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

basic descriptions of what's being done and why #23

Open
roblanf opened this issue Feb 20, 2017 · 3 comments
Open

basic descriptions of what's being done and why #23

roblanf opened this issue Feb 20, 2017 · 3 comments

Comments

@roblanf
Copy link
Collaborator

roblanf commented Feb 20, 2017

We are making progress! But one thing I've noticed is that we spend a decent amount of time trying to decipher what should be happening if everything works.

So, can I ask you to add two sections to the readme at the end of each of the scripts, titled something like:

What it does

and

Expected output

E.g. for the clean_reads.sh in the first section we'd want stuff about RCorrector, khmer, and the rationale for combining them here. In the section section we'd want to know what files we'd expect to see in the output directories (as well as subdirectories that should be empty, etc), and a sentence on what each file should contain.

Thanks!

R

@adamjorr
Copy link
Owner

I will work on this. Thanks for the feedback, it helps to know what is confusing so I can make the documentation as helpful as possible.

Specifically for clean_reads, the khmer and rcorrector steps are combined merely for ease of use. Do you think they should be separated? Maybe I could spin them into two separate scripts and keep clean_reads as a wrapper for them both. Since we're considering ditching khmer anyway, that may be easier for maintainability. It may also be easier to turn the pipeline into a make file, which is something @reedacartwright wants me to do.

adamjorr added a commit that referenced this issue Feb 20, 2017
@roblanf
Copy link
Collaborator Author

roblanf commented Feb 20, 2017 via email

@adamjorr
Copy link
Owner

I updated the docs, let me know if it helps

adamjorr added a commit that referenced this issue Feb 21, 2017
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