You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if the pipeline had the ability to take a file containing the paths to all the sequences that need to be run instead of a python list of sequences.
Some users need to subset reads from multiple different locations and are unable to use wildcards to do this, so are forced to make giant lists in the config file giving the path to each individual isolate. A possible solution to this is instead giving pipeline a text file that has the path to one read set per line, to prevent users having to copy and paste large lists into the config file.
The text was updated successfully, but these errors were encountered:
Possible to do, but a fair bit of work for rare case - and 'cut and paste' from a text file isn't that hard...
To make it easier to read, isolates can be added like this:
It would be nice if the pipeline had the ability to take a file containing the paths to all the sequences that need to be run instead of a python list of sequences.
Some users need to subset reads from multiple different locations and are unable to use wildcards to do this, so are forced to make giant lists in the config file giving the path to each individual isolate. A possible solution to this is instead giving pipeline a text file that has the path to one read set per line, to prevent users having to copy and paste large lists into the config file.
The text was updated successfully, but these errors were encountered: