Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

analysis step awarness #40

Open
dizak opened this issue May 11, 2018 · 1 comment
Open

analysis step awarness #40

dizak opened this issue May 11, 2018 · 1 comment
Labels
enhancement new feature

Comments

@dizak
Copy link
Owner

dizak commented May 11, 2018

f4d4887

Proposed feature

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.
@dizak dizak added the enhancement new feature label May 11, 2018
@dizak
Copy link
Owner Author

dizak commented May 22, 2018

The simplest way of re-running the analysis could be done in a similar way to calling mothulity for running the analysis phase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new feature
Projects
None yet
Development

No branches or pull requests

1 participant