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
mothulity know each step of analysis from each other. This might be achieved with few steps:
Enclosing particular mothur commands, instead of keeping them in a plaing text in the template. The question is: to what extent the logic from templates should be removed?
Once the command is passed to mothulity, it should know how the files would be named after each step. If it's done - resolving Checkpointing feature #9 is straightforward.
mothulity already creates the hidden logfile. It can be used as the cache.
The text was updated successfully, but these errors were encountered:
f4d4887
Proposed feature
mothulity
know each step of analysis from each other. This might be achieved with few steps:mothur
commands, instead of keeping them in a plaing text in the template. The question is: to what extent the logic from templates should be removed?mothulity
, it should know how the files would be named after each step. If it's done - resolving Checkpointing feature #9 is straightforward.mothulity
already creates the hidden logfile. It can be used as the cache.The text was updated successfully, but these errors were encountered: