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

IGV cannot open the session file #278

Closed
ktrns opened this issue May 22, 2023 · 2 comments
Closed

IGV cannot open the session file #278

ktrns opened this issue May 22, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request WIP Work in progress
Milestone

Comments

@ktrns
Copy link

ktrns commented May 22, 2023

Description of the bug

Hi there,

The pipeline produces an IGV session file. IGV can no longer open this file, as the "genome" folder is missing in the results folder, and the genome file cannot be found. This has been briefly discussed in the slack channel, and I wanted to copy-paste it into the issue section over here so it doesn't get lost.

The genome folder has been there before, so I suppose that this bug came with one of the recent updates.

By manually copying the genome.fa to the correct location, and generating an index, I can again open the IGV session file.

Best wishes & thanks
Katrin

Command used and terminal output

nextflow run $base/nf-core/atacseq/workflow --input $base/samples.csv \
--outdir $base/results \
--genome GRCm39 \
--read_length 100 \
-c $base/nf-core/atacseq/dcgc.config \
-c $base/nf-core/atacseq/genomes.config

Relevant files

No response

System information

No response

@ktrns ktrns added the bug Something isn't working label May 22, 2023
@JoseEspinosa
Copy link
Member

The reason for this behavior is that the save_reference parameter needs to be set to make the fasta file available in the genome folder, see here. But it is true that this is not documented and probably, makes little sense. So I think we should revert this behavior.

@JoseEspinosa JoseEspinosa added enhancement New feature or request WIP Work in progress and removed bug Something isn't working labels Jun 9, 2023
@JoseEspinosa JoseEspinosa self-assigned this Jun 9, 2023
@JoseEspinosa JoseEspinosa added this to the 2.1 milestone Jun 9, 2023
@JoseEspinosa
Copy link
Member

This should be fixed now in dev, if you find any further issue do not hesitate to reopen the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request WIP Work in progress
Projects
None yet
Development

No branches or pull requests

2 participants