Closed weiydcn closed 6 months ago
Hi,
Thanks for the detailed log, it seems that it crashed somehow when running aneufinder. (run_ANEUFINDER.R command ) The file /output_directory/call_CNVs/AneuFinder_run/gDNA/AneuFinder_output_best_parms.tab.generating.std
contains the STDOUT and STDERR of aneufinder. Could you check it and, if you can't solve it based on that file, attach its content here?
Best,
Miquel Àngel Schikora Barcelona Supercomputing Center
Good morning,
Could you solve this issue? If not, may you attach the file that I mentioned? Thanks.
Best,
Miquel Àngel Schikora Barcelona Supercomputing Center
Thank you for your kind assistance. I apologize for the delayed response. I have checked the file "AneuFinder_output_bestparms.tab.generating.std" as you mentioned, but I could only find an unfinished log in this file when comparing it with the mtDNA file. I will try to resolve this issue later, as we currently have a holiday for the Chinese New Year celebration. O(∩∩)O Now I can response instantly ,and i pasted bam file ,and two AneuFinder_output_best_parms.tab.generating.std. Hope to fix this error, thanks.
Best, Wei yidong FAAS, China
BAM file head:(reference genome:oryza sativa) @HD VN:1.6 SO:coordinate @SQ SN:Chr1 LN:44361539 @SQ SN:Chr2 LN:37764328 @SQ SN:Chr3 LN:39691490 @SQ SN:Chr4 LN:35849732 @SQ SN:Chr5 LN:31237231 @SQ SN:Chr6 LN:32465040 @SQ SN:Chr7 LN:30277827 @SQ SN:Chr8 LN:29952003 @SQ SN:Chr9 LN:24760661 @SQ SN:Chr10 LN:25582588 @SQ SN:Chr11 LN:31778392 @SQ SN:Chr12 LN:26601357 @SQ SN:chrM LN:527116 @SQ SN:chrC LN:134546 @RG ID:SAMPLE SM:SAMPLE @PG ID:bwa PN:bwa VN:0.7.17-r1188 CL:/opt/conda/envs/perSVade_env/bin/bwa mem -R @RG\tID:SAMPLE\tSM:SAMPLE -t 16 /output_directory/reference_genome_dir/reference_genome.fasta /reads/W07_1.fq.gz /reads/W07_2.fq.gz
gDNA:AneuFinder_output_best_parms.tab.generating.std
Attaching package: ‘BiocGenerics’ The following objects are masked from ‘package:parallel’: clusterApply, clusterApplyLB, clusterCall, clusterEvalQ, clusterExport, clusterMap, parApply, parCapply, parLapply, parLapplyLB, parRapply, parSapply, parSapplyLB The following objects are masked from ‘package:stats’: IQR, mad, sd, var, xtabs The following objects are masked from ‘package:base’: anyDuplicated, append, as.data.frame, basename, cbind, colnames, dirname, do.call, duplicated, eval, evalq, Filter, Find, get, grep, grepl, intersect, is.unsorted, lapply, Map, mapply, match, mget, order, paste, pmax, pmax.int, pmin, pmin.int, Position, rank, rbind, Reduce, rownames, sapply, setdiff, sort, table, tapply, union, unique, unsplit, which.max, which.min
Attaching package: ‘S4Vectors’ The following object is masked from ‘package:base’: expand.grid
Find CNVs for ID = AneuFinderID: Method = edivisive Running edivisive ... mtDNA:AneuFinder_output_best_parms.tab.generating.std
Attaching package: ‘BiocGenerics’ The following objects are masked from ‘package:parallel’: clusterApply, clusterApplyLB, clusterCall, clusterEvalQ, clusterExport, clusterMap, parApply, parCapply, parLapply, parLapplyLB, parRapply, parSapply, parSapplyLB The following objects are masked from ‘package:stats’: IQR, mad, sd, var, xtabs The following objects are masked from ‘package:base’: anyDuplicated, append, as.data.frame, basename, cbind, colnames, dirname, do.call, duplicated, eval, evalq, Filter, Find, get, grep, grepl, intersect, is.unsorted, lapply, Map, mapply, match, mget, order, paste, pmax, pmax.int, pmin, pmin.int, Position, rank, rbind, Reduce, rownames, sapply, setdiff, sort, table, tapply, union, unique, unsplit, which.max, which.min
Attaching package: ‘S4Vectors’ The following object is masked from ‘package:base’: expand.grid
Find CNVs for ID = AneuFinderID: Method = edivisive Running edivisive ... 25.99s Making segmentation ... 0.07s Time spent in findCNVs(): 26.72s
------------------ Original ------------------ From: "Gabaldonlab/perSVade" @.>; Date: Mon, Feb 12, 2024 06:06 PM @.>; @.**@.>; Subject: Re: [Gabaldonlab/perSVade] get an error in cnv calling (Issue #18)
Good morning,
Could you solve this issue? If not, may you attach the file that I mentioned? Thanks.
Best,
Miquel Àngel Schikora Barcelona Supercomputing Center
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Good afternoon,
Sure, no worries about the late response. I cannot see any error in the AneuFinder log, so I can't undertsand yet about the problem. Since aneufinder is run in both mtDNA and gDNA, can you verify that the attached file is /output_directory/call_CNVs/AneuFinder_run/gDNA/AneuFinder_output_best_parms.tab.generating.std
and not /output_directory/call_CNVs/AneuFinder_run/mtDNA/AneuFinder_output_best_parms.tab.generating.std
(which refers to the mtDNA, which was sucessful).
Do you have any performance issue (i.e. crash due to insufficient memory or similar)? I understand that the error is consistent (i.e. always the same when you run again) right?
Here is the puzzling thing. The end of the AneuFinder running script within perSVade is the following:
# run
cnv_calls = findCNVs(gr_coverage, most.frequent.state="2-somy", states=states, ID="AneuFinderID", strand="*", num.threads=threads, verbosity=4, method="edivisive", R=R, sig.lvl=sig_lvl)
# save
cnv_calls = data.frame(cnv_calls$segments)
write.table(cnv_calls, opt$outfile, sep="\t", col.names=TRUE, quote=FALSE, row.names=FALSE)
# remove all R objects
rm(list = ls())
According to the log, it seems like findCNVs finshed (see text "Time spent in findCNVs(): 26.72s") right? So it is crashing at the writing step. Perhaps a disk issue?
Thanks,
Miquel Àngel
Good morning,
Did you have a chance to look at this error? Could you solve it?
Thanks,
Miquel Àngel
Sorry, i reply using email with some picture, but they didnt show in github
we find the Unexpected exit in "AneuFinder_output_best_parms.tab.generating.std" from AneuFinder_run/gDNA
Find CNVs for ID = AneuFinderID: Method = edivisive Running edivisive ...
And AneuFinder_output_best_parms.tab.generating.std from AneuFinder_run/mtDNA is normal:
Find CNVs for ID = AneuFinderID: Method = edivisive Running edivisive ... 25.99s Making segmentation ... 0.07s Time spent in findCNVs(): 26.72s
------------------ Original ------------------ From: "Gabaldonlab/perSVade" @.>; Date: Mon, Feb 19, 2024 04:57 PM @.>; @.**@.>; Subject: Re: [Gabaldonlab/perSVade] get an error in cnv calling (Issue #18)
Good morning,
Did you have a chance to look at this error? Could you solve it?
Thanks,
Miquel Àngel
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Hi,
Alright, so I understand that /output_directory/call_CNVs/AneuFinder_run/gDNA/AneuFinder_output_best_parms.tab.generating.std
only contains the text " Unexpected exit in ", which I cannot interpret. I looks at some system failure. If you run again (with --replace to repeat all steps), does it happen the same (sometimes something fails in the computer and its worth re-reunning)? Do you have any disk / RAM issues while running?
Best,
Miquel Àngel
actually , I run three samples in an script, and I got same error for each samples。 and I check the coverage_file.tab in gDNA,find it incomplete(rice has 12 chromosom,but the data stop in chr9)
Chr9 24754001 24754500 0 Chr9 24754501 24755000 0 Chr9 24755001 24755500 0 Chr9 24755501 24756000 0 Chr9 24756001 24756500 0 Chr9 24756501 24757000 0 Chr9 24757001 24757500 0 Chr9 24757501 24758000 0 Chr9 24758001 24758500 0 Chr9 24758501 24759000 0 Chr9 24759001 24759500 0 Chr9 24759501 24760000 0 Chr9 24760001 24760500 0 Chr9 24760501 24760661 0 chrC 1 500 3919 chrC 501 1000 5416 chrC 1001 1500 11726 chrC 1501 2000 10860 chrC 2001 2500 11100 chrC 2501 3000 8109 chrC 3001 3500 6019 chrC 3501 4000 6413 chrC 4001 4500 8826 chrC 4501 5000 7429 chrC 5001 5500 5033 chrC 5501 6000 6743 chrC 6001 6500 2686 chrC 6501 7000 6203 chrC 7001 7500 6259 chrC 7501 8000 6743 chrC 8001 8500 * 1303
Hi,
Alright, perhaps the issue lies in the previous coverage generation then. The file coverage_file.tab
contains the inferred counts of reads mapping to each region. When you say "(rice has 12 chromosom,but the data stop in chr9)" what do you mean? In the file you send (I assume its the content of coverage_file.tab
) you have data for chr9 (only the end) and chrC (only the beginning). So you only have these in the file? This would seem an issue.
Also, it seems that Chr9 has coverage=0 all along right? Is this expected? This would suggest that something odd is happening with the coverage generation. In your bam file, do you see coverage in chrom 9 (and others)? I'd really recommend you to i) check that your bam has evely distributed coverage across all chromosomes and ii) run again from scratch (remove all files generated by call_CNVs, and run again, so that everything is re-run).
Hope this helps,
Miquel Àngel
Thanks for
Hi,
Alright, perhaps the issue lies in the previous coverage generation then. The file
coverage_file.tab
contains the inferred counts of reads mapping to each region. When you say "(rice has 12 chromosom,but the data stop in chr9)" what do you mean? In the file you send (I assume its the content ofcoverage_file.tab
) you have data for chr9 (only the end) and chrC (only the beginning). So you only have these in the file? This would seem an issue.Also, it seems that Chr9 has coverage=0 all along right? Is this expected? This would suggest that something odd is happening with the coverage generation. In your bam file, do you see coverage in chrom 9 (and others)? I'd really recommend you to i) check that your bam has evely distributed coverage across all chromosomes and ii) run again from scratch (remove all files generated by call_CNVs, and run again, so that everything is re-run).
Hope this helps,
Miquel Àngel
Thanks for your reply. The files "coverage_file.tab" seem normal, the region of chr9 with coverage =0 is the termini of chromosome. The record of Chr10-12 are right and localizated after Chr1. I would call CNV using other servers to exclude server running environment issues。
Hi,
Alright, so then you do have the chromosomes 10-12 right? Does it mean that the problem is solved? Regardless, what you are saying " I would call CNV using other servers to exclude server running environment issues" is interesting, and also validate that there are no RAM / disk issues (may be the case since we are not getting a clear error message).
Best,
Miquel Àngel
Yes,the coverage file is normal. The problem is solved, and i would report when i meet problem, thanks!
------------------ Original ------------------ From: "Gabaldonlab/perSVade" @.>; Date: Tue, Feb 20, 2024 11:55 PM @.>; @.**@.>; Subject: Re: [Gabaldonlab/perSVade] get an error in cnv calling (Issue #18)
Hi,
Alright, so then you do have the chromosomes 10-12 right? Does it mean that the problem is solved? Regardless, what you are saying " I would call CNV using other servers to exclude server running environment issues" is interesting, and also validate that there are no RAM / disk issues (may be the case since we are not getting a clear error message).
Best,
Miquel Àngel
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Alright, great, happy to see that it worked out. Tell me if you have further issues.
Best,
Miquel Àngel
use docker to call CNVs,this is the command
error log
the output file