Reads a list of MotionTracking '.csv'-export-files into Knime. This is done by searching for csv-files recursively within the specified directory or by selecting a list of files directly.
There are two modes of operation. Either you can choose a single directory in which
the nodes will search for MotionTracking files. The search is applied not only to the direct directory
contents but also to also its subfolders.
The second mode is to select a set of files (by keeping the apple/windows-key pressed while selecting files).
In the advanced tab of the configuration dialog one can define the pattern and associate the keywords to interpret the information of the file Paths contained in the first column. The default pattern is:
This pattern matches file paths from images acquired with the Opera (Perkin Elmer) and that are converted with motion tracking into mtf-files. Anything that is contained within () -> token, will be associated with the variable that is contained within. The rest of the syntax is normal regular expressions (see java-doc).
The mandatory variables are
The optional variables are:
timepoint: time point between scans
wellfield: field of view within one well
frame: can be a time-frame of a movie or a z-slice of a z-stack (usually not used in HCS).
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
A zipped version of the software site can be downloaded here.
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to firstname.lastname@example.org, follow @NodePit on Twitter, or chat on Gitter!
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.