-
Notifications
You must be signed in to change notification settings - Fork 178
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
feat(shared-data): correct existing labware defs engageHeight #5261
Conversation
@@ -55,9 +55,6 @@ export const MODULE_MODELS: Array<ModuleModel> = [ | |||
...THERMOCYCLER_MODULE_MODELS, | |||
] | |||
|
|||
// offset added to parameters.agneticModuleEngageHeight for displaying reccomended height in PD | |||
export const ENGAGE_HEIGHT_OFFSET = -4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed this from constants b/c nobody aside from getLabwareDefaultEngageHeight
should use it, as far as I can figure. I think wanting the -4 would be a sign you're not going through the getter and probably you should use the getter...?
Codecov Report
@@ Coverage Diff @@
## edge #5261 +/- ##
==========================================
+ Coverage 61.44% 62.16% +0.72%
==========================================
Files 1043 1043
Lines 29623 30363 +740
==========================================
+ Hits 18201 18876 +675
- Misses 11422 11487 +65
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❄️
- previous default value: 16
- new GEN1 value: 18
- new GEN2 value: 36
Approving assuming these are the new ranges/numbers!
shared-data/js/getLabware.js
Outdated
labwareDef.namespace === OPENTRONS_LABWARE_NAMESPACE && | ||
_SHORT_MM_LABWARE_DEF_LOADNAMES.includes(labwareDef.parameters.loadName) | ||
) { | ||
const rawEngageHeight: ?number = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this part be moved out of the if block since it's repeated on line 83?
Dismissing my approval since i think there is some confusion of real and short mm numbers here and in ranges and what the UI should accept. i think we talked about getting rid of the units all together? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐅
makes sense now!
overview
Closes #5226
changelog
review requests
((original_number_in_def * 2) - 4) / 2
. For GEN2 magnetic module, the final/ 2
shouldn't happen, for GEN1, it should.For the 1 recommended magnetic module labware,
for nest_96_wellplate_100ul_pcr_full_skirt
, both default value and "Recommended: __" caption should be:FYI, the math is:
risk assessment
Shouldn't interfere with anything outside on engageHeight use in PD. But it WILL mess up creating engage magnet steps in PD with default values until we do #5230, because the min/max values we have aren't right; default values won't be valid until we fix the range. However this issue is blocking #5230 too.