-
Notifications
You must be signed in to change notification settings - Fork 90
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
Sketching paired-end read data #32
Comments
You have the right idea catting to stdin. I added this step to the tutorial to clarify, but this could certainly be more elegant, maybe with a flag that pools all inputs into one sketch (possibly a behavior of the read flag If you want to try avoiding |
I do seem to have this persistent core dump: zcat SRR1262647_1.fastq.gz | ../mash-Linux64-v1.1/mash sketch -k 21 -r - Same with cat: cat SRR1262647_1.fastq.gz | ../mash-Linux64-v1.1/mash sketch -k 21 -r - Works fine without piping: ../mash-Linux64-v1.1/mash sketch -k 21 -r SRR1262647_1.fastq.gz Any ideas? |
Looks look stdin input was broken in 1.1. A fix is now in the latest source and will be included in the next release. |
Should be fixed in v1.1.1. |
Hello,
output:
The ID is empty. We can do bellow:
so can avoid ID issue, but couldn't enjoy the pleasure of unix stream pipeline : ) Thanks for the author |
In latest source the |
Hi
I note no mention of paired-end data in the docs; sketching with multiple files creates a multi-file sketch, but if I want a single sketch per paired-end sample, how is this done?
I assume I should be able to use sub-shells and/or zcat and pipe to stdin; however when i did this on our cluster I got core dumps (admittedly I seem to be having some problems with zcat on our cluster....)
At the very least it may be a good idea to update your docs to reflect how to sketch paired-end read data
Cheers
Mick
The text was updated successfully, but these errors were encountered: