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

Wrong reference genome indicated in the juicer.log #364

Open
Audald opened this issue Dec 28, 2024 · 0 comments
Open

Wrong reference genome indicated in the juicer.log #364

Audald opened this issue Dec 28, 2024 · 0 comments
Labels

Comments

@Audald
Copy link

Audald commented Dec 28, 2024

Hi there,

I am running Juicer as follows (as reported by the aligned/header file):

Experiment description: Juicer version 1.6; BWA 0.7.17-r1188; 20 threads; openjdk version "11.0.19" 2023-04-18; /opt/scripts/juicer.sh -d /path/to/folder -D /opt/ -p /path/to/folder/ref/clean.chrom.sizes -y /path/to/folder/ref/sites.txt -z /path/to/folder/ref/genome.fasta -t 20

However, the juicer.log indicates that I am aligning my reads against the hg19 genome.

(-: Looking for fastq files...fastq files exist
(-: Aligning files matching /path/to/folder/fastq/*_R*.fastq* to genome hg19 with site file /path/to/folder/ref/sites.txt
(-: Created /path/to/folder/splits and /path/to/folder/aligned.

I suspect this is a bug/error (confirmed by the Arima Technical Support Team) because when I try to force the mapping to hg19 (instead of my -z genome.fasta) with -g hg19:

Reference sequence /opt//references/homo_sapiens_assembly19.fasta does not exist (as expected)

Just raising this bug in case you want to correct the way the log files are being reported. Best!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant