-
Notifications
You must be signed in to change notification settings - Fork 5
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
Sample IDs based on filenames causing errors in computation #20
Comments
Thank you for the report. This will be solved in our next release. |
Thank you for the feedback. The issue is solved in version 1.1 |
Hi @aysegokce ! I also have an issue related to file names in Severus v1.1. All my BAM files are generated with the same name, and I use the storage directory as their ID. However, Severus appears to only consider the file name, and if they share the same name (even in different directories), the execution is canceled, warning that I'm using the control as the target too: [2024-07-24 01:30:32] root: INFO: Starting Severus 1.1
[2024-07-24 01:30:32] root: DEBUG: Cmd: /storage/scratch01/groups/bu/simSVs/visor-simulations/.snakemake/conda/2a5c70c705b132ee6ccd896c702286f5_/bin/severus --target-bam results/v1_30x_B_LASeR/sim.srt.bam --control-bam results/normal_LASeR/sim.srt.bam --out-dir results/v1_30x_B_severus -t 24
[2024-07-24 01:30:32] root: DEBUG: Python version: 3.12.4 | packaged by conda-forge | (main, Jun 17 2024, 10:23:07) [GCC 12.3.0]
[2024-07-24 01:30:32] root: ERROR: Error: Control bam also inputted as target bam For now, I am avoiding the problem by creating symbolic links for the tumor files: ln -sf $(basename {input.tumor_bam}) $(dirname {input.tumor_bam})/tumor.bam
ln -sf $(basename {input.tumor_bam}).bai $(dirname {input.tumor_bam})/tumor.bam.bai
severus \
--target-bam $(dirname {input.tumor_bam})/tumor.bam \
--control-bam {input.normal_bam} \
--out-dir {output.dir} \
-t {threads} \
> {log} 2>&1 |
I have a pipeline that uses clair3 for haplotyping and severus afterward. I noticed that even though I have control samples, the output only included all_SVs. I suspected the cause to be that the input bams have the same name (as clair3 generates them). So I ran some tests, and that seems to be the case.
This is the log for the run with files named the same:
And this is the available output:
And this is the log for the run where I created symlinks for the same bams, to have different filenames:
And the corresponding output tree:
The text was updated successfully, but these errors were encountered: