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

Report kevlar version when running a script #61

Open
standage opened this issue Mar 31, 2017 · 3 comments
Open

Report kevlar version when running a script #61

standage opened this issue Mar 31, 2017 · 3 comments

Comments

@standage
Copy link
Collaborator

...for reproducibility's sake, yo.

@ctb
Copy link
Collaborator

ctb commented Apr 3, 2017 via email

@standage
Copy link
Collaborator Author

Minimal reporting added in #65. Leaving this thread open to entertain considerations raised by @ctb.

@standage
Copy link
Collaborator Author

standage commented Dec 3, 2018

The introduction of Snakemake workflows in #305 and #306 raises the possibility of recommending Snakemake as the primary interface for most users, with the kevlar command documented for users that are curious or need to tweak results. In any case, I think with a small amount of effort we can improve and capture the existing logging outputs and save them to standardized locations in the Snakemake working directory, creating a nice record of provenance. Capturing logs when running kevlar directly will be left as an exercise for the user. :-)

I don't have much interest in going down the rabbit hole we started exploring in dib-lab/khmer#676.

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

No branches or pull requests

2 participants