-
Notifications
You must be signed in to change notification settings - Fork 67
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
Mapping error at .tmpMap//tmp.test2.*.SJ.out.tab' #378
Comments
Hi, That is indeed odd. Can you share the exact yaml file you use? Regarding the warning on the STAR version should be OK - STAR doesn't always write the precise version number into its index files. Best, |
Hiya, YAML is:
There is an unmapped.bam, but is seems incomplete? For
|
Hey, OK that looks actually quite good for the unmapped bam, and it did clearly set the PE flags correctly to the reads which is what STAR complained about. Anyways, my gut feeling is the commented out lines in the "reference" section may disturb things in the yaml! Please remove them completely and have a check
|
Thanks for the quick reply. I removed all comments from the yaml, but am getting the same issues. Unmapped bam output is still generated, fails during the mapping stage. I did a fully fresh run as well, but this is the error when starting with
Possibly relevant: during one trial one point I saw an error with |
Just updating for anyone else seeing the same issues - I never resolved this and instead switched to a kallisto-bustools pipeline, which now has a smart-seq3 option. See biostars post. Another option that worked for me was umi_tools > samtools > umi_tools dedup > feature counts. |
Trying to analyse some SMART-SEQ3 data and can't manage to get past the mapping step. Any suggestions would be much appreciated. I've remade my index multiple times (
STAR --version
is giving 2.7.3a, even though it's being flagged below as 2.7.1a?), and have also tried with using my own dependencies and STAR 2.7.11a, as well as a fresh zUMI pull (working with 2.9.7e).bash zUMIs/zUMIs.sh -c -y patch-seq/patchseq.yaml
Currently using the yaml provided from smart-seq3 example (https://github.com/sandberg-lab/Smart-seq3/blob/master/allele_level_expression/mouse_cross.yaml) with
num_threads:
andmem_limit:
adjusted, as well as nobarcode_file:
Output is as follows
I've tried re-running this from the mapping step using
which_Stage: Mapping
in the YAML and get a slightly different error with an eventualExecution halted
.As an aside: I'm trying to get this working on an HPC in parallel, but am still working through permission issues with the support team, any tips there would also be appreciated, error below.
The text was updated successfully, but these errors were encountered: