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

ERROR ~ A process input channel evaluates to null -- Invalid declaration val mito_name #306

Closed
JiahuaQu opened this issue Jul 13, 2023 · 3 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@JiahuaQu
Copy link

Description of the bug

Hi, I had problems in downloading the complete and correct pipelines. I tried many versions but always failed with the similar errors:
ERROR Cannot parse container string in
'nf-core-atacseq-2.0/workflow/modules/nf-core/bowtie2/align/main.
nf':

         ${ workflow.containerEngine ==                               
                                                                      
     ⚠ Skipping this singularity image.. 

downloading with singularity images.txt

Then I determied to download without singularity images.
However, when running the program in my institute's HPC, the same error always showed:
ERROR ~ A process input channel evaluates to null -- Invalid declaration val mito_name
my.log
test.sh.o9702320.txt

Hope get your help. Thank you.

Command used and terminal output

No response

Relevant files

No response

System information

nextflow # version: 22.10.6

HPC
GSE
With or without singularity
CentOS

I tried various versions:

nf-core-atacseq-dev

nf-core-atacseq-2.0

nf-core-atacseq-master

nf-core-atacseq-1.2.2

nf-core-atacseq-modules-update

@JiahuaQu JiahuaQu added the bug Something isn't working label Jul 13, 2023
@JoseEspinosa
Copy link
Member

Yes, these are two known bugs of the current released version that are fixed in the dev version of the pipeline see #270 and #286. Anyway, if you want to use the release version you can:
1- Just can use the nf-core download and do not care about the error. The reason is that the the bwa image will be downloaded anyways since bwa/mem uses the same image and there it is correctly tagged. More info about the download command here.
2- Just provide an empty or a fake mito_name adding this to your command --mito_name '' or --mito_name dummy

@JoseEspinosa JoseEspinosa added the duplicate This issue or pull request already exists label Jul 14, 2023
@JiahuaQu
Copy link
Author

Yes, these are two known bugs of the current released version that are fixed in the dev version of the pipeline see #270 and #286. Anyway, if you want to use the release version you can: 1- Just can use the nf-core download and do not care about the error. The reason is that the the bwa image will be downloaded anyways since bwa/mem uses the same image and there it is correctly tagged. More info about the download command here. 2- Just provide an empty or a fake mito_name adding this to your command --mito_name '' or --mito_name dummy

Thank you for your answer.
Now I used the version 2.0 and added the command --mito_name ''.
Although the program could be ran further than before, there was a new error with the BWA-MEM. Details in the attachment.
Hope get further help. Thank you again.
new_error.txt

@JoseEspinosa
Copy link
Member

JoseEspinosa commented Jul 25, 2023

Since this is being discussed already in nf-core/chipseq#356. I close this issue now in favor of the former.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants