You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to run a python program inside a simple nextflow pipeline. This script (apple.py) has an option that calls another script (banana.py) as a sub-process.
Running python apple.py (banana option) on the terminal works fine, however, inside my workflow this has the task ending successfully despite seemingly not running the banana.py sub-process. I'm not sure I understand why this is happening - is the task being considered done even though apples.py has a running python sub-process (bananas.py)? If so, any tips on how I can work around this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello!
I'm trying to run a python program inside a simple nextflow pipeline. This script (
apple.py
) has an option that calls another script (banana.py
) as a sub-process.Running
python apple.py (banana option)
on the terminal works fine, however, inside my workflow this has the task ending successfully despite seemingly not running thebanana.py
sub-process. I'm not sure I understand why this is happening - is the task being considered done even thoughapples.py
has a running python sub-process(bananas.py)
? If so, any tips on how I can work around this?Beta Was this translation helpful? Give feedback.
All reactions