-
Notifications
You must be signed in to change notification settings - Fork 108
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
test with real data #33
Comments
I needed to specify Two warning massages appeared: WARN: Access to undefined parameter |
Warnings can be ignored, I will add an initialization step for readPaths, that should get rid of number 1. The second one is to be ignored in general :-) |
process make_SILVA_132_16S_classifier (which we dont test usually) raises an error: |
skipping that step for now using existing classifier with |
Process Command error: |
UNzip should be present now in the container, I updated the |
That might be a missing file issue. We'd need to login to binac then and check what happens when we try to access the path to your work directory from inside the singularity container. Might be also issue with mount paths etc.... which singularity version are we using there? |
mv /home/tu/bcgsd01/.nextflow/assets/nf-core/rrna-ampliseq/docs/output.md output.md works but module load devel/singularity/3.0.1 also module unload devel/singularity/3.0.1 is that what you wanted to know? |
Exactly!! |
This is on BinAC right? |
Yeah, I assume its a bit weird in terms of that we can't map these directories... |
Yeah. Try it on our Cluster @d4straub |
I started analysis on new cfc, dont really expect complete results before Monday. |
What does Monday say ? 🥇 |
ERROR ~ Error executing process > 'metadata_category_all (1)' Edit: this occured using module qbic/singularity_slurm/3.0.1, new trial using qbic/singularity_slurm/2.6 |
Why did this happen ?!?! |
Don't even know where this is coming from.... |
Could very well be a Singularity 3.0.1 issue unfortunately :-( |
same with Singularity 2.6, also fastqc is failing... weird |
Started it again with Singularity 2.5.2: Edit: terminal output attached Edit2: |
WTF, we tested locally using |
Should test on a workstation again, I fear binac has some module issues again... |
this is on our cfc... |
It sounds/looks a bit like a singularity error, copying in @mseybold for clarification |
It seems its missing
Looks to me as if running pretty well on a bigger test-dataset! |
Ran through on test system |
processes dada_single & make_SILVA_132_16S_classifier are queuing since yesterday, but processes that were failing before succeeded this time (output_documentation, metadata_category_all). |
I guess we could assume then this is resolved? |
I assume it is. ;) |
test with real data on binac
The text was updated successfully, but these errors were encountered: