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

Take into account radius for calibration params #745

Merged
merged 3 commits into from
Jan 12, 2025

Conversation

psavery
Copy link
Collaborator

@psavery psavery commented Jan 10, 2025

For cylindrical detectors, we need to take into account the radius for calibration flags and parameters.

This uses the old, non-lmfit style for defining calibration flags and parameters. We will be able to eliminate all of this when we upgrade the HEDM calibration to use the new lmfit calibration style...

But for now, we need to maintain this.

For cylindrical detectors, we need to take into account the radius
for calibration flags and parameters.

This uses the old, non-lmfit style for defining calibration flags and
parameters. We will be able to eliminate all of this when we upgrade
the HEDM calibration to use the new lmfit calibration style...

But for now, we need to maintain this.

Signed-off-by: Patrick Avery <patrick.avery@kitware.com>
@psavery psavery marked this pull request as ready for review January 10, 2025 20:10
Copy link

codecov bot commented Jan 10, 2025

Codecov Report

Attention: Patch coverage is 60.00000% with 4 lines in your changes missing coverage. Please review.

Project coverage is 39.69%. Comparing base (c1fbb97) to head (4890d34).
Report is 7 commits behind head on master.

Files with missing lines Patch % Lines
hexrd/instrument/cylindrical_detector.py 50.00% 2 Missing ⚠️
hexrd/instrument/hedm_instrument.py 66.66% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #745      +/-   ##
==========================================
- Coverage   39.70%   39.69%   -0.01%     
==========================================
  Files         135      135              
  Lines       22392    22397       +5     
==========================================
+ Hits         8890     8891       +1     
- Misses      13502    13506       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

The expression indicates that the parameter is computed, and thus should
not be allowed to vary.

This prevents an issue where, if the Y value of 'IMAGE-PLATE-4' for
TARDIS was allowed to vary using the old parameter flags, and TARDIS
engineering constraints are used such that the Y value of 'IMAGE-PLATE-4'
is computed, that we won't accidentally set that parameter to vary.

Signed-off-by: Patrick Avery <patrick.avery@kitware.com>
Due to a bug where we were accidentally setting IP4-Y to vary, even
though it is supposed to be computed, we were actually not applying
engineering constraints in this test.

Since we weren't actually applying engineering constraints in the
testing before, just disable them for now. We can look into adding
them later.

Signed-off-by: Patrick Avery <patrick.avery@kitware.com>
Copy link
Member

@saransh13 saransh13 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@saransh13 saransh13 merged commit 8bd2a7d into master Jan 12, 2025
7 checks passed
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

Successfully merging this pull request may close these issues.

2 participants