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

Confusing Info Printout about GFF and GTF #307

Closed
subwaystation opened this issue Oct 11, 2019 · 7 comments
Closed

Confusing Info Printout about GFF and GTF #307

subwaystation opened this issue Oct 11, 2019 · 7 comments
Milestone

Comments

@subwaystation
Copy link

When I run the pipeline using an iGenomes genome, the pipelines informs me, that GTF is favoured over GFF and that the GFF will be ignored, although I never specified a GFF. Furthermore, iGenomes provides a GTF for EB1 as can be seen in https://github.com/nf-core/rnaseq/blob/master/conf/igenomes.config.
Nextflow start:

nextflow run nf-core/rnaseq -r dev --reads '*.fastq.gz' --genome EB1 -profile cfc --singleEnd

Confusing message:

...
Prefer GTF over GFF, so ignoring provided GFF in favor of GTF
...

I think one should either not print this message or at least I would like to know what is going on :)

@apeltzer apeltzer added this to the 1.5 milestone Oct 11, 2019
@apeltzer
Copy link
Member

I think that means to say whatever you provide as GTF is overruling any specified GFF file (as GFF -> GTF conversion loses some info in most cases..).

@apeltzer
Copy link
Member

Was adjusted in V1.4 which was just now released 👍

@drpatelh drpatelh reopened this Oct 17, 2019
@drpatelh
Copy link
Member

This hasnt been updated in the latest release. I agree, it is a bit confusing.

@apeltzer
Copy link
Member

The text was, but the message logic not ;-)

@apeltzer apeltzer modified the milestones: 1.5, 1.4.1 Oct 17, 2019
@drpatelh
Copy link
Member

Ok. This whole block is confusing and will need a proper look. Indenting doesnt help either 😅

rnaseq/main.nf

Lines 259 to 288 in 55eee0c

if( params.gtf ){
if ( params.gff ){
// Prefer gtf over gff
log.info "nf-core/rnaseq prefers a GTF over GFF, so ignoring a provided GFF in favor of GTF"
}
if (hasExtension(params.gtf, 'gz')){
gtf_gz = Channel
.fromPath(params.gtf, checkIfExists: true)
.ifEmpty { exit 1, "GTF annotation file not found: ${params.gtf}" }
} else {
Channel
.fromPath(params.gtf, checkIfExists: true)
.ifEmpty { exit 1, "GTF annotation file not found: ${params.gtf}" }
.into { gtf_makeSTARindex; gtf_makeHisatSplicesites; gtf_makeHISATindex; gtf_makeSalmonIndex; gtf_makeBED12;
gtf_star; gtf_dupradar; gtf_qualimap; gtf_featureCounts; gtf_stringtieFPKM; gtf_salmon; gtf_salmon_merge }
}
} else if ( params.gff ){
if (hasExtension(params.gff, 'gz')){
gff_gz = Channel.fromPath(params.gff, checkIfExists: true)
.ifEmpty { exit 1, "GFF annotation file not found: ${params.gff}" }
} else {
gffFile = Channel.fromPath(params.gff, checkIfExists: true)
.ifEmpty { exit 1, "GFF annotation file not found: ${params.gff}" }
}
} else {
exit 1, "No GTF or GFF3 annotation specified!"
}

Im going to remove this message here because the gff and gtf validation is done earlier anyway:

rnaseq/main.nf

Lines 655 to 657 in 55eee0c

} else {
log.info "Prefer GTF over GFF, so ignoring provided GFF in favor of GTF"
}

@apeltzer
Copy link
Member

Yeah, this isn't optimal

@drpatelh drpatelh mentioned this issue Oct 17, 2019
9 tasks
@drpatelh
Copy link
Member

Fixed in #319

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

No branches or pull requests

3 participants