-
Notifications
You must be signed in to change notification settings - Fork 11
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
sc_long_pipeline.py--> ValueError: invalid contig chr1
#37
Comments
Oh I think it is a pysam error which happens when reading the bam file. It is likely that your bam file is generated with a different reference without chr1 or there is no chr1 reads in your bam files so it give this error. you can check your bam file header using |
Here's my output. There seem to be @hd VN:1.6 SO:coordinate |
The genomefa should be the fasta file of genome instead of transcript. For human the most recent primary assembly should be: https://ftp.ebi.ac.uk/pub/databases/gencode/Gencode_human/release_42/GRCh38.primary_assembly.genome.fa.gz. other versions have similar naming convention. The FLAMES software will generate the transcript fasta file, which contains the known transcript and the new transcript called from the bam file. |
I see, thanks. With the updated input, I get a new error:
Our barcode is the first 16nt and the umi is the next 10nt that follows. The fastq I provided for |
Yes, it is expecting fastq files outputted by match_cell_barcode, where the identifier field has the format of |
But this fastq file couldn't be viewed by
Here is the output statistic for
|
@dontwantcode there seem to be an extra
|
Hi Luyi,
|
Should be a gzipped fastq, could you check with zcat? Or maybe post the first line of |
Hi, both my
genome.fa
andgff3
files use contigchr1
. Is there support for this format or parameters I can set to solve this error?The text was updated successfully, but these errors were encountered: