-
Notifications
You must be signed in to change notification settings - Fork 24
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
re-occuring "not a valid Project Location" error #17
Comments
Hey Nir, SIRIUS ties to write to A known problem is that when SIRIUS "fails" because of a wrong command (e.g. non existing parameter) it has already created the output folder, but in a non valid state. The folder is non empty but does also not contain a single compound. In that case you need to delete the folder manually. Could that be the reason for you problem? This behavior shall be improved in one of the upcoming updates. In case of an permission problem a "permission denied" error message should be reported in the console. Best |
Hi Markus, Thanks for your swift reply! The software behaviour is much clearer now. I don't want to open another thread - but to briefly ask about the following case: So, is there an option to set Canopus to annotate all the identified molecular formulas, or - in case of Have a good week and thanks once more, |
Hi Sirius team,
Running the latest version from the command line (and as "system" call from within R) on Linux64bit, I keep getting a non indicative error message related to the output directory: "not a valid Project Location".
By re-iterating with different parameters I conclude that this error message occurs in the following conditions:
I did set full permissions at my designated output folder and additionally I noticed the Sirius is independently writing to "/tmp" which is owned by "root" (!) - so I really I do not know what can cause this error.
Thanks,
Nir
Matrix products: default
BLAS: /usr/lib/libblas/libblas.so.3.6.0
LAPACK: /usr/lib/lapack/liblapack.so.3.6.0
locale:
[1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C
[3] LC_TIME=he_IL.UTF-8 LC_COLLATE=en_US.UTF-8
[5] LC_MONETARY=he_IL.UTF-8 LC_MESSAGES=en_US.UTF-8
[7] LC_PAPER=he_IL.UTF-8 LC_NAME=C
[9] LC_ADDRESS=C LC_TELEPHONE=C
[11] LC_MEASUREMENT=he_IL.UTF-8 LC_IDENTIFICATION=C
The text was updated successfully, but these errors were encountered: