-
Notifications
You must be signed in to change notification settings - Fork 6
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
Illegal option -- #23
Comments
Dear @seveein, |
Hi Josué,
The gene_ages.tsv file is empty afterwards. Do you have an idea how we could resolve this issue? |
Dear @seveein, Could you try something akin to this command?
Please let me know if this works for you so I can update the wiki for singularity users. Best, |
``Dear Josué,
All user-provided paths are available to singularity. There should be also enough computational resources available. Best, edit: current singularity call:
|
Dear @seveein, Could you please send me the complete STDOUT log from the Best, |
Dear @josuebarrera. ncbi_lineages_2024-09-02.csv:
4084_Diamond_results.bout
Stdout:
gene_age_summary.tsv
Let me know whether you need anything else! Best, s. |
Dear @seveein, It seems that step 1 ran without any issues, so you can keep using the file The first thing I noticed is that the file The other possible source of error I see could be in the script FASTSTEP3R. This is an R script that makes step 3 run much faster than in the initial versions of GenEra, but it also consumes a considerable amount of memory and may be the cause of your errors. To verify this, could you please run GenEra again by adding the following argument: I'm still puzzled about the error Please let me know if these two things solve your issues. Cheers, |
Hi Jossué, Step 3 finished within minutes and returned the same error prompt again:
The issue seems to be related to Step 3. Adjusting to |
Quick update: I've been experimenting with the Singularity settings because it seemed that Singularity was mishandling environment variables. Using the
messages are no longer appearing in the STDOUT. Additionally, Step 3 appears to be running more stably now and isn't skipping the analysis. However, it’s still in progress, so please proceed with caution. STDOUT:
troubleshooting command:
cheers, |
Dear @seveein, It seems that Cheers, |
Dear @josuebarrera, |
Hi everyone,
thank you very much for this nice contribution to the community!
I tested GenEra on our cluster.
here, I observed the following on stdout:
After this, it seems like GenEra continues with the analysis:
To Reproduce
I use the Docker-Container via singularity:
Is this a known bug, and can I trust that GenEra will continue without further issues?
Thank you very much.
cheers
s
The text was updated successfully, but these errors were encountered: