Skip to content
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

Specifying enforced elements in .ms file #31

Closed
pleeferguson opened this issue Mar 22, 2021 · 3 comments
Closed

Specifying enforced elements in .ms file #31

pleeferguson opened this issue Mar 22, 2021 · 3 comments

Comments

@pleeferguson
Copy link

Hi, I would like to run the Sirius CLI in batch mode so that I can avoid having to call a new JVM for every formula calculation I am doing, but I need to be able to set different enforced elements for each individual spectrum input. I cannot seem to make this work within the .ms file format. I can of course use the -E flag within the CLI arguments, but then the same elemental alphabet will be applied across all calculations. However, when I specify >elements within the .ms files, the elemental alphabet seems to be treated analogous to the CLI argument -e (elements considered).

Perhaps I'm missing a feature? Please let me know if this is possible or if it could be implemented.

@kaibioinfo
Copy link
Contributor

Hi Lee,

you can specify the enforced elements with
>FormulaSettings.enforced C,H,N,O,P,S,Cl,Br,I

In fact, you can set all kind of config options this way. A list of all available config options can be found in /.sirius-4.7/custom.config

@pleeferguson
Copy link
Author

This works perfectly. Thanks for the quick reply, Kai!

@mfleisch
Copy link
Contributor

Just for completion:

sirius config -h

should give you the list of possible parameters from the command line.

mfleisch pushed a commit that referenced this issue Aug 2, 2024
…nnotation' into 'master'

Resolve "Make spectral scoring function customizable via an annotation"

Closes #31

See merge request bright-giant/sirius/sirius-libs!10
mfleisch pushed a commit that referenced this issue Aug 2, 2024
…mono-repo' into 'master'

Resolve "Merge sirius-libs into sirius-frontend to create a mono repo."

Closes #300, #132, #126, #123, #128, #125, #127, #124, #122, #121, #120, #109, #115, #106, #99, #112, #111, #61, #110, #103, #108, #107, #104, #221, #102, #98, #198, #92, #94, #93, #85, #84, #87, #76, #56, #73, #32, #70, #65, #43, #63, #33, #53, #58, #59, #57, #54, #52, #41, #47, #50, #49, #48, #39, #46, #37, #38, #27, #34, #22, #31, #28, #18, #23, #21, #19, #9, #240, #280, #254, #242, #246, #238, #156, #25, #155, #189, #172, #154, #11, #6, #16, and #4

See merge request bright-giant/sirius/sirius-frontend!106
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants