-
Notifications
You must be signed in to change notification settings - Fork 118
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
Specify custom gtf but gene bed is not generated from that gtf? #109
Comments
Hi Lei! Please can you send me the full commands you used for each run please. |
Edited as a markdown code block 😉 run1: nextflow run nf-core/atacseq \
-c atacseq_custom.config \
-profile conda \
--input /hpc/grid/wip_drm_targetsciences/projects/p013_TE_Expression/GSE100750/nf_ATACSeq_pipeline/Design.txt \
--outdir /hpc/grid/wip_drm_targetsciences/projects/p013_TE_Expression/GSE100750/nf_ATACSeq_pipeline/Output/AllSampleOutput_GRCh38_defaultGeneModel/ \
--genome GRCh38 \
--skip_multiqc run2: nextflow run nf-core/atacseq \
-c atacseq_custom.config \
-profile conda \
--input /hpc/grid/wip_drm_targetsciences/projects/p013_TE_Expression/GSE100750/nf_ATACSeq_pipeline/Design.txt \
--outdir /hpc/grid/wip_drm_targetsciences/projects/p013_TE_Expression/GSE100750/nf_ATACSeq_pipeline/Output/AllSampleOutput_GRCh38_GENCODE26/ \
--genome GRCh38 \
--gtf /hpc/grid/wip_drm_targetsciences/users/shangl02/RefLib/Human/GENCODE/gencode.v26.basic.annotation.gtf \
--skip_multiqc |
Hi @mavershang This is a bug but there is a simple workaround. Please can you add the parameter |
Thank you @drpatelh. Will try |
Fixed here @mavershang. Thanks for reporting! |
Hi there, I ran the pipeline in two different settings:
run1. using the default ref genome GRCh38 without specify gtf and
run2. using the defualt ref genome GRCh38 and specified a custom gtf GENCODE.v26.basic.gtf
According to the document, the gene bed will be generated from the custom gtf, but in run2 the log says it seems the pipeline still go staging the genes.bed from S3 bucket.
The run2 get to the end successful. In the reference genome folder, the generated genes.tss.bed is exactly the same as run1.
So I am wandering is this a bug in the code or did I miss something?
Thanks,
Lei
The text was updated successfully, but these errors were encountered: