Closed CloXD closed 4 months ago
Have you tried the instructions in the Troubleshooting section of the README?
Didn't see it, sorry! However, do you think it's a good idea to have --writable-tmpfs enabled? In this case, NUMBA default cache directory is in the code source directory of the library ( if I'm not misinterpreting here ) and in a containerized environment, it might be cleaner to set this NUMBA_CACHE_DIR and other cache/temporary env variable to /tmp Sorry again for the disturb and thanks for the really nice pipeline
Operating System
Linux
Other Linux
RedHat
Workflow Version
latest
Workflow Execution
Command line (Cluster)
Other workflow execution
lsf with singularity profile
EPI2ME Version
No response
CLI command run
No response
Workflow Execution - CLI Execution Profile
None
What happened?
Runtime error:
Don't know why, but apparently NUMBA cachedir is either not set or the location is not accessible ( tested on lsf using singularity). I solved in process matrix ( subworkflows/process_bams.nf )
Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
no
Other demo data information
No response