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

meta.id confusion #79

Open
muffato opened this issue Aug 22, 2023 · 0 comments
Open

meta.id confusion #79

muffato opened this issue Aug 22, 2023 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@muffato
Copy link
Member

muffato commented Aug 22, 2023

Description of the bug

On the public_dev branch, the input fasta is called GCA_946965045.1.fasta.gz and the Hi-C CRAM file GCA_946965045.1.unmasked.hic.uoEpiScrs1.subsampled.cram, but the assembly parameter is set to GCA_946965045.2. After a run of the test profile, 1) I get these two files in the genome_note/ directory:

  • GCA_946965045.1.csv
  • GCA_946965045.2.docx

2), GCA_946965045.1.csv contains:

Accession,GCA_946965045.1

3), and many more intermediate files are also named GCA_946965045.1.*, indicating that the pipeline is confused about what is meta.id.

The input file names can be different from the accession number etc, but I'd expect the outputs of the pipeline to be consistently named.

Command used and terminal output

nextflow run sanger-tol/genomenote/ -profile test,singularity -r public_dev

Relevant files

No response

System information

Nextflow 23.04.1-5866 from our central installation

@muffato muffato added the bug Something isn't working label Aug 22, 2023
@muffato muffato mentioned this issue Aug 22, 2023
9 tasks
@muffato muffato added this to the 2.0.0 milestone Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: In Progress
Development

No branches or pull requests

2 participants