We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
I used the following command to compress a sam file and it completed without any error.
(/usr/bin/time --verbose \ /90daydata/maizegdb/sagnik/softwares/quip-1.1.8/src/quip \ --input=bam \ -r /90daydata/maizegdb/sagnik/data/ARATH/genome/Arabidopsis_thaliana.TAIR10.dna_sm.toplevel.fa.quip \ /90daydata/maizegdb/sagnik/ABRIDGE/rough/SRR13711353_SE.bam \ -c \ ) \ 1> /90daydata/maizegdb/sagnik/ABRIDGE/rough/SRR13711353_SE.quip \ 2> /90daydata/maizegdb/sagnik/ABRIDGE/rough/SRR13711353_SE.quip.compress.error
I keep getting an error when I attempt to decompress the same file. I think I am not correctly interpreting the command line arguments
(/usr/bin/time --verbose \ /90daydata/maizegdb/sagnik/softwares/quip-1.1.8/src/quip \ -d \ --input=quip \ -r /90daydata/maizegdb/sagnik/data/ARATH/genome/Arabidopsis_thaliana.TAIR10.dna_sm.toplevel.fa.quip \ /90daydata/maizegdb/sagnik/ABRIDGE/rough/SRR13711353_SE.quip \ -c \ ) \ 1> /90daydata/maizegdb/sagnik/ABRIDGE/rough/SRR13711353_SE.quip.decompressed.sam \ 2> /90daydata/maizegdb/sagnik/ABRIDGE/rough/SRR13711353_SE.quip.decompress.error
The error is
quip: /90daydata/maizegdb/sagnik/ABRIDGE/rough/SRR13711353_SE.quip: Unknown SAM field type:
Could you please look into it?
Thank you.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
I used the following command to compress a sam file and it completed without any error.
I keep getting an error when I attempt to decompress the same file. I think I am not correctly interpreting the command line arguments
The error is
Could you please look into it?
Thank you.
The text was updated successfully, but these errors were encountered: