Tools: mcrun: optimization allows to specify criteria expression #1743
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR provides the ability to specify an expression with
--optimize-eval="EXPR"such as:This enables to optimize on existing monitors, and still use some predefined statistics within:
d.intensityThe detector intensity;d.errorThe detector intensity uncertainty;d.valuesAn array with [intensity, error, counts];d.X0 d.Y0Center of signal (1st moment);d.dX d.dYWidth of signal (2nd moment).Default is
d.intensity. Examples are:d.intensity/d.dXfor 1D;d.intensity/d.dX/d.dYfor 2DThis PR avoids to create specific monitors for optimization, as long as the 1st/2nd moments are satisfactory.