Closed FedericaBrando closed 1 year ago
Hi Frederica,
From the Linx log it appears that one or more of the Purple files have produced an INF in the data, and this is causing the R plotting script and Linx to fail.
Are you able to share the Purple input files from this run? Then I can run Purple in debug to see how it is failing in that R script.
Email me directly if preferable: c.shale@hartwigmedicalfoundation.nl
thanks,
Charles
Hi @charlesshale, thanks for the answer. I am using COLO829T and COLO829T bam files as input (the one that are in the github repo for running the demo).
I'm running the pipeline in panel mode and it fails on purple step. This is the command that I am using:
scripts/run_pipeline scripts test_data ref_data_dir/37/PANEL tools_dir "COLO829T,COLO829R" V37 PANEL 8 64
I ran our demo pipeline just now with our current pipeline (v5.32) on the COLO829 mini BAMs and it produced valid results for all components, including Purple and Purple plots.
Could you try this again if still applicable, and ensure that it includes Cobalt v1.14 which better handles regions with low coverage.
I think any issue here is with the COLO mini BAMs, and not the components or the pipeline itself. We have run many panel samples (TSO500 and HMF OncoPanel) through this pipeline now, and compared the results to WGS output and it is as expected.
Me, again. I am running the panel demo pipeline with the test data provided in the repo with the following command:
but I get the following error at the Purple step:
by inspecting the
tmp/copyNumberPlots.R15471386380511817827.error
I get this:Then, the next step in the pipeline is Linx and I am not sure if it's related to the previous error or not, but I get this
Exception
: