New Scripting Nodes

A couple new scripting nodes can be found here.

  • Adding an m/z column to the Compounds table
  • Adding m/z and Delta Mass [ppm] columns to the Expected Compounds table
  • Calculate O/C and H/C ratios in the Compounds table
  •  Show KEGG IDs (top mzCloud hit) in the Compounds table 

Your feedback and requests for additional scripting nodes are welcome!

About Ralf Tautenhahn

Platform Manager Metabolomics Software

Posted on April 7, 2020, in Uncategorized. Bookmark the permalink. 4 Comments.

  1. Hi Ralf, that’s very nice, I remember asking for the mz column and the theoretical logP vs RT plot.
    My CD3.1 will not allow me to have more than one scripting node in my workflow… Is there a plan to allow several? Or am I missing something?

    Like

  2. Hi Julie, great question. I’m happy you like the Scripting nodes. You are right, you can only use one Scripting node in the workflow. The Scripting node offers a convenient user interface that helps with the initial development and testing of a script. However once you are happy with your script, you can then “install” your Scripting node as a standalone node which looks just like all the other nodes. That way you can install and use as many Scripting nodes as you want and you can also use additional options like having menu options in the node parameters to pass these additional parameters to the node etc. The installation process is described in section “Registering Standalone Scripting Nodes” in the Custom Script Integration manual and you can find an example for the JSON file that is required in SimpleTest.zip (Example 1). I was thinking about creating the JSON files also for the other examples but the file paths within those JSON files would still need to be adjusted for your R version and location of the script. Please let me know if you need help with the JSON files or the installation process!

    Like

    • Thank you for the quick reply.
      Anas suggested that maybe I could put the code of several desired scripting nodes into a single longer code then used in the single scripting node in the workflow. Would that work? I’m just wondering if the variable description part would be easy enough and would not create conflicts. I haven’t tried yet anyway.

      Like

  3. Ralf Tautenhahn

    Anas is right. That would work too. However it would require a significant rewriting of the code, whereas the other solution (install as standalone scripting nodes) only requires the JSON file for the installation to be created. I can help with that if needed, just send me a email.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: