Skip to content
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

Cannot write to --joblog parallel_1_call_var_bam_pileup.log #5

Closed
MeHelmy opened this issue May 17, 2021 · 7 comments · Fixed by #8
Closed

Cannot write to --joblog parallel_1_call_var_bam_pileup.log #5

MeHelmy opened this issue May 17, 2021 · 7 comments · Fixed by #8
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@MeHelmy
Copy link

MeHelmy commented May 17, 2021

Hi,

I'm using Clair3 as the following:
${HOME}/Clair3/run_clair3.sh --bam_fn ~/projects/tests/clair3/HG002.ONT.bam --ref_fn ~/hs37d5_mainchr.fa --threads 10 --platform ont --model_path ~{HOME}/Clair3/modules/ont --output SNVs

I have this error:

+ Clair3/scripts/clair3.sh --bam_fn ~/projects/tests/clair3/HG002.ONT.bam --ref_fn ~/hs37d5_mainchr.fa --threads 10 --model_path ${HOME}/Clair3/modules/ont --platform ont --output SNVs --bed_fn=EMPTY --vcf_fn=EMPTY --ctg_name=EMPTY --sample_name=EMPTY --chunk_num=0 --chunk_size=5000000 --samtools=samtools --python=python3 --pypy=pypy3 --parallel=parallel --whatshap=whatshap --qual=0 --var_pct_full=0.3 --ref_pct_full=0.3 --snp_min_af=0.0 --indel_min_af=0.0 --pileup_only=False --gvcf=False --fast_mode=False --print_ref_calls=False --haploid_precise=False --haploid_sensitive=False --include_all_ctgs=False --no_phasing_for_fa=False [INFO] Check envrionment variables [INFO] --include_all_ctgs not enabled, use chr{1..22,X,Y} and {1..22,X,Y} by default [INFO] Call variant in contigs: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 X Y [INFO] Chunk number for each contig: 50 49 40 39 37 35 32 30 29 28 28 27 24 22 21 19 17 16 12 13 10 11 32 12 [INFO] 1/7 Calling variants using pileup model tee: SNVs/log/1_call_var_bam_pileup.log: No such file or directory parallel: Error: Cannot write to --joblog SNVs/log/parallel_1_call_var_bam_pileup.log.

Thanks,
Medhat

@zhengzhenxian
Copy link
Collaborator

zhengzhenxian commented May 18, 2021

Hi Medhat,
Could you try changing --output SNVs to --output ${HOME}/SNVs. Let us know if that works, and we will improve the code accordingly.

@aquaskyline aquaskyline added bug Something isn't working enhancement New feature or request labels May 18, 2021
@huangnengCSU
Copy link

huangnengCSU commented May 18, 2021

Hi,
I had the same error. And when all the inputs use the absolute path, the error does not appear any more.

@MeHelmy
Copy link
Author

MeHelmy commented May 18, 2021

As mentioned by @huangnengCSU it works.
Thanks,
Medhat

@aquaskyline
Copy link
Member

aquaskyline commented May 18, 2021

Relative path supported in v0.1-r1 if you use Singularity or create a Conda environment. Relative path is still not supported when using docker. The best practice is still to use absolute path everywhere.

@MeHelmy
Copy link
Author

MeHelmy commented May 18, 2021

Relative path supported in v0.1-r1.

For both bam and output directory?
Thank you

@aquaskyline
Copy link
Member

aquaskyline commented May 18, 2021

Yes. Are you using docker? Absolute paths are still necessary for docker, It's a problem with docker, and I have updated my previous reply to show when would absolute path still be necessary. We are also adding a checkpoint that will stop the program early if a docker environment and non-absolute paths are detected.

@MeHelmy
Copy link
Author

MeHelmy commented May 18, 2021

I'm using conda env installation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants