-
Notifications
You must be signed in to change notification settings - Fork 25
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 ~ No such variable: Exception evaluating property 'out' for nextflow.script.ChannelOut #70
Comments
Please could you provide the custom config used in the command, along with the sample and contrast sheets? |
Hi, sure. This is the sample sheet:
This is the contrast sheet:
And this is the custom.config. I only use it here to enforce running on HTCondor. Everything else in there so far is relevant to
|
Thanks @amizeranschi, will get back to you after reviewing |
Hi! Is there any update on this issue? It would be great to have this pipeline working from BAM files produced with nf-core/rnaseq, in order to avoid having to map reads a second time to the reference genome. |
Hi @amizeranschi , We've just pushed a bunch of changes to dev, and this should have fixed your issue. Remember to force nextflow download the latest changes, rather than a cache of the one you currently have on your computer. Let us know how you get on. |
Thanks @jma1991 for letting me know. I tried testing again and now I'm running into the issue described here: #72 Could you guys also implement the fixes proposed there by @dkoppstein and @valentinoruggieri? |
Good that your issue has been solved. I will implement the fixes in #72 right now. |
Description of the bug
Hello,
I'm getting the error from the title when testing the pipeline, starting from BAM files produced by nf-core/rnaseq. Tested with the latest dev version and Nextflow
23.04.0
. This the the output:The last printed message seems to refer to this part of the code: https://github.com/nf-core/rnasplice/blob/dev/workflows/rnasplice.nf#L175-L179
I am attaching the full log below.
Command used and terminal output
No response
Relevant files
nextflow.log
System information
No response
The text was updated successfully, but these errors were encountered: