failed: 256 at ./run-trust4 line 55.
liu9756 opened this issue · comments
Here is my code and the bug:
$ ./run-trust4 -b all_contig.bam -f all_contig.fasta -o TRUST_all_contig_toassemble --ref mm39.fa --barcode CB -t 4
[Tue Mar 12 11:32:23 2024] TRUST4 begins.
[Tue Mar 12 11:32:23 2024] SYSTEM CALL: /home/user/trust4/TRUST4/bam-extractor -b all_contig.bam -t 4 -f all_contig.fasta -o TRUST_all_contig_toassemble_toassemble --barcode CB
[Tue Mar 12 11:32:23 2024] Start to extract candidate reads from bam file.
Unknown genome name: GGGGTAATTGAAGTCAAGACTCAGCCTGGACATGATGTCCTCTGCTCAGTTCCTTGGTCTCCTGTTGCTCTGTTTTCAAGGTACCAGATGTGATATCCAGATGACACAGACTACATCCTCCCTGTCTGCCTCTCTGGGAGACAGAGTCACCATCAGTTGCAGGGCAAGTCAGGACATTAGCAATTATTTAAACTGGTATCAGCAGAAACCAGATGGAACTGTTAAACTCCTGATCTACTACACATCAAGATTACACTCAGGAGTCCCATCAAGGTTCAGTGGCAGTGGGTCTGGAACAGATTATTCTCTCACCATTAGCAACCTGGAGCAAGAAGATATTGCCACTTACTTTTGCCAACAGGGTAATACGCTTCCGTACACGTTCGGAGGGGGGACCAAGCTGGAAATAAAACGGGCTGATGCTGCACCAACTGTATCCATCTTCCCACCATCCAGTGAGCAGTTAACATCTGGAGGTGCCTCAGTCGTGTGCTTC
system /home/user/trust4/TRUST4/bam-extractor -b all_contig.bam -t 4 -f all_contig.fasta -o TRUST_all_contig_toassemble_toassemble --barcode CB failed: 256 at ./run-trust4 line 55.
I checked my data and the data should not have problems
The -f file hold the VDJ sequences from a reference genome along with their genomic coordinates at the header. The reference files for mouse can be found at: https://github.com/liulab-dfci/TRUST4/tree/master/mouse , where GRCm38_bcrtcr.fa is for -f, and the IMGT one is for --ref. Or do you need to use your own VDJ reference sequences?
Thanks for your reply. Actually I tried the GRCm38_bcrtcr.fa and IMGT , however it seems not work:
$ ./run-trust4 -b all_contig.bam -f GRCm38_bcrtcr.fa --ref mouse_IMGT+C.fa -o TRUST_all_contig_toassemble --barcode CB
[Wed Mar 13 10:00:32 2024] TRUST4 begins.
[Wed Mar 13 10:00:32 2024] SYSTEM CALL: /home/user/trust4/TRUST4/bam-extractor -b all_contig.bam -t 1 -f GRCm38_bcrtcr.fa -o TRUST_all_contig_toassemble_toassemble --barcode CB
[Wed Mar 13 10:00:32 2024] Start to extract candidate reads from bam file.
Unknown genome name: 6
system /home/user/trust4/TRUST4/bam-extractor -b all_contig.bam -t 1 -f GRCm38_bcrtcr.fa -o TRUST_all_contig_toassemble_toassemble --barcode CB failed: 256 at ./run-trust4 line 55.
Could you please show me the chromosome names of your bam file by "samtools view -H all_contig.bam"?
@hd VN:1.6 SO:coordinate
@sq SN:AAACCTGAGACGCACA-1_contig_1 LN:496
@sq SN:AAACCTGAGATAGTCA-1_contig_1 LN:488
@sq SN:AAACCTGAGCGTTCCG-1_contig_1 LN:510
@sq SN:AAACCTGAGGACAGCT-1_contig_1 LN:464
@sq SN:AAACCTGAGGACAGCT-1_contig_2 LN:521
@sq SN:AAACCTGCAAGCGCTC-1_contig_1 LN:499
@sq SN:AAACCTGCAAGCGCTC-1_contig_2 LN:656
@sq SN:AAACCTGCAAGCGCTC-1_contig_3 LN:503
@sq SN:AAACCTGCACAACGCC-1_contig_1 LN:551
@sq SN:AAACCTGCACGCCAGT-1_contig_1 LN:508
@sq SN:AAACCTGCACGGCGTT-1_contig_1 LN:492
@sq SN:AAACCTGCAGCGTCCA-1_contig_1 LN:503
@sq SN:AAACCTGCATTACGAC-1_contig_1 LN:517
@sq SN:AAACCTGCATTGCGGC-1_contig_1 LN:551
@sq SN:AAACCTGGTACCATCA-1_contig_1 LN:303
@sq SN:AAACCTGGTACCATCA-1_contig_2 LN:460
@sq SN:AAACCTGGTATAGTAG-1_contig_1 LN:496
@sq SN:AAACCTGTCAGTGTTG-1_contig_1 LN:503
@sq SN:AAACCTGTCCGTCAAA-1_contig_1 LN:496
@sq SN:AAACCTGTCCTAAGTG-1_contig_1 LN:559
@sq SN:AAACCTGTCCTAAGTG-1_contig_2 LN:498
@sq SN:AAACCTGTCGGCGCTA-1_contig_1 LN:538
@sq SN:AAACCTGTCGGCGCTA-1_contig_2 LN:498
@sq SN:AAACCTGTCTCCCTGA-1_contig_1 LN:496
@sq SN:AAACCTGTCTCCCTGA-1_contig_2 LN:373
@sq SN:AAACCTGTCTCTAGGA-1_contig_1 LN:497
@sq SN:AAACCTGTCTGCTTGC-1_contig_1 LN:495
@sq SN:AAACGGGAGCTGCAAG-1_contig_1 LN:389
@sq SN:AAACGGGAGTGTTGAA-1_contig_1 LN:590
@sq SN:AAACGGGAGTGTTGAA-1_contig_2 LN:506
@sq SN:AAACGGGCAAACCCAT-1_contig_1 LN:551
@sq SN:AAACGGGCAGCTGCAC-1_contig_1 LN:538
@sq SN:AAACGGGCAGGTGGAT-1_contig_1 LN:495
@sq SN:AAACGGGCATTATCTC-1_contig_1 LN:512
@sq SN:AAACGGGTCAACCAAC-1_contig_1 LN:497
@sq SN:AAACGGGTCACAACGT-1_contig_1 LN:342
@sq SN:AAACGGGTCAGAGCTT-1_contig_1 LN:493
@sq SN:AAACGGGTCCACGTTC-1_contig_1 LN:527
@sq SN:AAACGGGTCGTGGACC-1_contig_1 LN:309
@sq SN:AAACGGGTCTAACTCT-1_contig_1 LN:428
@sq SN:AAACGGGTCTTGTATC-1_contig_1 LN:565
@sq SN:AAAGATGAGTTCGATC-1_contig_1 LN:538
@sq SN:AAAGATGCAAGAGTCG-1_contig_1 LN:467
@sq SN:AAAGATGCAAGGTTTC-1_contig_1 LN:551
@sq SN:AAAGATGCAGATGAGC-1_contig_1 LN:684
@sq SN:AAAGATGCAGATGAGC-1_contig_2 LN:512
@sq SN:AAAGATGCATGAACCT-1_contig_1 LN:512
@sq SN:AAAGATGGTAAATGAC-1_contig_1 LN:501
@sq SN:AAAGATGGTATCTGCA-1_contig_1 LN:620
@sq SN:AAAGATGGTCACACGC-1_contig_1 LN:512
@sq SN:AAAGATGTCAAACGGG-1_contig_1 LN:503
@sq SN:AAAGATGTCCCACTTG-1_contig_1 LN:559
@sq SN:AAAGATGTCCCACTTG-1_contig_2 LN:410
@sq SN:AAAGATGTCGGGAGTA-1_contig_1 LN:481
@sq SN:AAAGATGTCTTGTCAT-1_contig_1 LN:493
@sq SN:AAAGCAAAGAAGATTC-1_contig_1 LN:495
@sq SN:AAAGCAAAGCCACGTC-1_contig_1 LN:495
@sq SN:AAAGCAAAGGAGTACC-1_contig_1 LN:521
@sq SN:AAAGCAAAGTGCCAGA-1_contig_1 LN:512
@sq SN:AAAGCAACAGCCTATA-1_contig_1 LN:521
@sq SN:AAAGCAAGTAAGTTCC-1_contig_1 LN:505
@sq SN:AAAGCAAGTTGTGGCC-1_contig_1 LN:627
@sq SN:AAAGCAATCACATGCA-1_contig_1 LN:501
@sq SN:AAAGCAATCAGGCCCA-1_contig_1 LN:504
@sq SN:AAAGCAATCCCTAATT-1_contig_1 LN:532
@sq SN:AAAGCAATCCTGTACC-1_contig_1 LN:512
@sq SN:AAAGCAATCGCCTGTT-1_contig_1 LN:494
@sq SN:AAAGCAATCTGAGTGT-1_contig_1 LN:503
@sq SN:AAAGTAGAGACTACAA-1_contig_1 LN:559
@sq SN:AAAGTAGAGACTAGGC-1_contig_1 LN:510
@sq SN:AAAGTAGAGAGTGAGA-1_contig_1 LN:494
@sq SN:AAAGTAGAGATCACGG-1_contig_1 LN:500
@sq SN:AAAGTAGAGCGTGAAC-1_contig_1 LN:407
@sq SN:AAAGTAGAGGCATGGT-1_contig_1 LN:684
@sq SN:AAAGTAGAGGCATGGT-1_contig_2 LN:512
@sq SN:AAAGTAGCAATAACGA-1_contig_1 LN:512
@sq SN:AAAGTAGCACCAGGCT-1_contig_1 LN:567
@sq SN:AAAGTAGCACGTCAGC-1_contig_1 LN:561
......
@pg ID:samtools PN:samtools VN:1.16.1 CL:samtools sort -l 8G -m 600M -o /home/user/referenceData/run_vdj_S5/SC_VDJ_ASSEMBLER_CS/SC_MULTI_CORE/MULTI_GEM_WELL_PROCESSOR/VDJ_B_GEM_WELL_PROCESSOR/SC_VDJ_CONTIG_ASSEMBLER/ASSEMBLE_VDJ/fork0/chnk00-uf0fee24a37/files/contig_bam_sorted.bam /home/user/referenceData/run_vdj_S5/SC_VDJ_ASSEMBLER_CS/SC_MULTI_CORE/MULTI_GEM_WELL_PROCESSOR/VDJ_B_GEM_WELL_PROCESSOR/SC_VDJ_CONTIG_ASSEMBLER/ASSEMBLE_VDJ/fork0/chnk00-uf0fee24a37/files/contig_bam.bam
@pg ID:samtools.1 PN:samtools PP:samtools VN:1.16.1 CL:samtools merge -@ 3 -c -p -s 0 -b /home/user/referenceData/run_vdj_S5/SC_VDJ_ASSEMBLER_CS/SC_MULTI_CORE/MULTI_GEM_WELL_PROCESSOR/VDJ_B_GEM_WELL_PROCESSOR/SC_VDJ_CONTIG_ASSEMBLER/ASSEMBLE_VDJ/fork0/join-uf0fee24a37/files/contig_bam.fofn /home/user/referenceData/run_vdj_S5/SC_VDJ_ASSEMBLER_CS/SC_MULTI_CORE/MULTI_GEM_WELL_PROCESSOR/VDJ_B_GEM_WELL_PROCESSOR/SC_VDJ_CONTIG_ASSEMBLER/ASSEMBLE_VDJ/fork0/join-uf0fee24a37/files/contig_bam.0.bam
@pg ID:samtools.2 PN:samtools PP:samtools.1 VN:1.13 CL:samtools view -H all_contig.bam
I think the BAM file is from the alignment of the read to each BCR contig. The bam file for TRUST4 should be the alignment to the reference genome. Just curious, since your data already has cellranger vdj results, why you need to run TRUST4 on the data? Thank you.
I am trying to get some SHM analysis by TRUST4
The cellranger vdj probably already contains enough information for SHM analysis in the AIRR file. If you need to use TRUST4 from the beginning, I think using the VDJ fastq file is more convenient.