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

Read minimum lengths: Include read names in rest file? #47

Closed
marcelm opened this issue Mar 13, 2015 · 2 comments
Closed

Read minimum lengths: Include read names in rest file? #47

marcelm opened this issue Mar 13, 2015 · 2 comments
Labels

Comments

@marcelm
Copy link
Owner

marcelm commented Mar 13, 2015

From cas...@gmail.com on March 07, 2012 11:29:15

If I use trim and apply a minimum length, then the rest file contains the trimmed part for sequences not in the output file. So I cannot tell which line in the rest file corresponds to a line in the output.

I would suggest adding the sequence name to the rest file: jamescasbon@8ace754

Original issue: http://code.google.com/p/cutadapt/issues/detail?id=37

@marcelm
Copy link
Owner Author

marcelm commented Mar 13, 2015

From marcel.m...@tu-dortmund.de on March 09, 2012 03:04:01

I think this is really useful, but I’m reluctant to change the file format (as bad as it is) because it wouldn’t be backwards compatible. Perhaps some scripts are already out there that rely on this. My idea for a while has been to add a new --info-file option that would also contain the "rests", but also the read name, no. of mismatches, length of the overlap etc.

But perhaps no one is really using the rest file in an automated way, I don’t know.

@marcelm
Copy link
Owner Author

marcelm commented Mar 13, 2015

From marcel.m...@tu-dortmund.de on June 17, 2012 10:28:53

I've merged your changes, let's see who complains. By the way, to make collaboration easier, I've now moved the source code to github: https://github.com/marcelm/cutadapt . Thanks for the patch!

Status: Fixed

@marcelm marcelm closed this as completed Mar 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant