The Scripting Node is a customizable node that allows you to run an executable file as the final node in a workflow and to incorporate the result data into the application’s result file.
The data exchange between the Proteome Discoverer application and the executable relies on a few mechanisms that do not need .NET code because the executable does not use the application API to read and write data. Instead, the user declares the columns for the tables from the result file to be exported into one or more tab-separated text files along with a JSON file describing the structure and location of those files. The user-defined script or executable should subsequently read these files, perform the user-defined type of analysis, and then optionally write out tab-separated text files containing information with another JSON file describing the structure of new tables and/or columns to be imported into the Proteome Discoverer results.
To create a script for the Scripting Node, programmers can use any programming language that supports running code from the command line, for example, Python, R, C#, C++, and so on.
- Use as a Post Processing Node (Default)
- For an example, see Use the Scripting Node in a workflow.
- Register a standalone Processing or Consensus node that can be given to another Proteome Discoverer user.
For information about how to register a custom workflow node, see Managing the application licenses.
The Scripting Node cannot access MS/MS spectra. In general, the Scripting Node can only act upon viewable columns from a result file.
To integrate a search engine, a statistic algorithm, or a workflow that requires deeper access to the application code, you must program in C#. Contact pd.support@thermofisher.com for more information.