ChristofferFlensburg / superFreq

Analysis pipeline for cancer sequencing data
MIT License
110 stars 33 forks source link

Successfully assigned alignments 0 error #99

Closed maheshworpaudel5001 closed 1 year ago

maheshworpaudel5001 commented 1 year ago

Hello Christoffer,

I have been trying to run superFreq with instructions in the manual. I have all the necessary input files and they are also setup in the necessary format. However, I have been running into a problem where the program itself does some alignment (I guess looking at the output) on already pre-aligned bam files and complains about 0 normal counts. A part of the output looks like the following:

Screenshot 2023-03-15 at 8 49 00 PM

Because of the counts being 0, my fCsExon.Rdata is empty which in turn does not generate the plots required. I am also not sure what are the all the output files the run should produce.

Anyway, the 0 count thing also happens for the normal samples I provide in the myreferencenormals directory.

I seriously need help on this.

ChristofferFlensburg commented 1 year ago

This is the read count step, using rsubread, and is intended and needed for copy number calling. The read counts of 0 are a problem, but not clear why that happened. Maybe you got some informative error messages?

In general, make sure everything is up to date (R, superFreq and dependencies), and check that your bam files, index and fasta are available, healthy and readable.

maheshworpaudel5001 commented 1 year ago

slurm-2876413.txt

Here is the full output of my run. I do not understand why the program writes the normal bam files of the reference normals directory twice in succession. I have checked all the input files, they look intact.

ChristofferFlensburg commented 1 year ago

SuperFreq doesn't write any bam files.

0 counts are almost always because the bam and or bam index files are not readable from your job submission. If you want to work on it from the R side, start by updating R and all the packages, but I don't think this is a superFreq error.

maheshworpaudel5001 commented 1 year ago

That was error on my part. I had messed up reference genome. I downloaded it using command: bwa.kit/run-gen-ref hs38DH which is recommended by the bwa.kit manual for GRCh38 mapping. However, this command does not download correct data but only downloads ALT CTGs.