-
Notifications
You must be signed in to change notification settings - Fork 29
[Question] Output of CLI command different from documentation? (v6.1.1) #251
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
Comments
Hi, You might be looking at outdated documentation, this is the correct link for SIRIUS 6: https://v6.docs.sirius-ms.io. It contains information on most of your questions. Could you please let me know where you got the link for the old documentation from, so that we can replace it there as well? For questions not answered in the docs, our gitter community at https://matrix.to/#/#sirius-ms:gitter.im would be a better suited place |
Hi Martin, thank you for the reply! It seems somehow, even though I was aware of the deprecated v5 documentation, I had ended up reading some of that one for the Quick Start CLI guide. That's where my confusion about How many compounds can be expected in I have joined the gitter community and will forward my questions there from now on. Thank you again! Joe |
The summary files for the project should contain only one answer per compound (cause it is a "summary"). You can access the original ranking via the REST api. |
Thank you Kai! |
Hello! I have a few questions regarding the SIRIUS CLI, specifically the output when running commands. I am using SIRIUS version 6.1.1 on Ubuntu inside a Docker container based off the eclipse-temurin:21 java image.
So far, my commands have followed the following format (based off the quick-start CLI documentation):
sirius --input tests/test.mgf --output query-results/sirius-output formula -p orbitrap fingerprint compound-classes write-summaries --output query-results/sirius-summary
Based on the documentation, I would expect this command to create a
formula_candidates.tsv
file under the summary directory with the ten most likely compounds (along with other files). When I run this command, I get asirius-output.sirius
file and asirius-summary
folder underquery-results/
which is expected, but inside thesirius-summary
folder, I get 6 files:canopus_formula_summary.tsv
,canopus_structure_summary.tsv
,denovo_structure_identifications.tsv
,spectral_matches.tsv
,structure_identifications.tsv
, andformula_identifications.tsv
. The formula_identifications file is the only file that has any content (aside from headers). And the content is a single compound identified by SIRIUS given the MGF file. Why is there only one compound listed? Is it because SIRIUS is ultra-confident in that one being correct? Or should I be seeing a list of 10 compounds ordered by rank? And is thisformula_identifications.tsv
file the same as theformula_candidates.tsv
file mentioned in the documentation? If not, where is that file / why is it not being produced?Also, I am struggling to find information on the structure command. What does adding
structure --database pubchem
to my command do? What kind of database does the command use if no database is supplied? Is it always better to use pubchem over no specified db? I read pubchem has over 111 million formulas?Another question I had was regarding the indexing of the commands. I noticed some commands do not work when you switch up the order, is there a documentation page where we can see which commands are expected at which index / order? I couldn't find any information on it.
Sirius --help
gave me a little more insight but I am still unsure. Thank you!Here is the testing MGF file I have been using:
And the output inside formula_identifications has been: (how come some entries are empty, like overallFeatureQuality?)
1 C21H42O5 [M + K]+ C21H42KO5+ 0.677 14.089 14.089 0.000 1 0.882 1.862 1.862 -0.638 413.266 700493078913457792 700493074744319612 700493074744319612_UNKNOWN_FEATURE_1
Thank you so much for your time!
Joe
The text was updated successfully, but these errors were encountered: