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

[Feature request] Add option to write all candidates in the summaries #50

Closed
Adafede opened this issue Dec 9, 2021 · 4 comments
Closed
Labels
fixed v5.4 indicates that a bug or feature request has been fixed in v5.4

Comments

@Adafede
Copy link

Adafede commented Dec 9, 2021

Hi again,

Would be nice to have such an option directly for downstream uses of the candidates' list.
I think many people out there have custom bash scripts to cat their own summaries from the folders just because the "default" candidates are too restricted.

Best,

Edit: Having the ability to filter the N top candidates according to a given score, for example, the confidence score, would be even better! 😄

@mfleisch mfleisch added the fixed v5.4 indicates that a bug or feature request has been fixed in v5.4 label Mar 16, 2022
@mfleisch
Copy link
Contributor

I had a discussion with @lfnothias on this. Since the information is already available in the compound level summaries we agreed that it might be enough if these files can be written to a location outside of the project-space so that they can be easily processed (without the huge raw results).

This feature will be available in SIRIUS 5.

Please reopen the issue if this does not tackle the problem.

@Adafede
Copy link
Author

Adafede commented Mar 17, 2022

@mfleisch Thank you very much!

Do you have an estimate of when it will be (pre-)released?

@Adafede
Copy link
Author

Adafede commented Mar 18, 2022

Looks like I need to subscribe to the web service to get the new features ;P

@mfleisch
Copy link
Contributor

mfleisch commented Mar 18, 2022

Yes an account is needed, but you will not have to subscribe when using an email address from your (academic/non-profit) institution ;-) Documentation will follow ;-)

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

Resolve "new persistence model classes need more annotations"

Closes #50

See merge request bright-giant/sirius/sirius-libs!23
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
fixed v5.4 indicates that a bug or feature request has been fixed in v5.4
Projects
None yet
Development

No branches or pull requests

2 participants