docs(api): explain order of operations for RTP value updates triggering reanalysis #15195
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
ecormany
changed the title
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.
Overview
Testing revealed that labware offsets aren't applied to labware that are only loaded as the result of custom RTP values. This is somewhat expected, due to the order of operations: analyze -> apply offsets -> choose RTP values -> reanalyze.
This docs addition goes into much greater detail than the very short summary we could fit into the release notes (see #15194).
Test Plan
Sandbox
Review requests
Is this too much? Will it all be rendered moot by a hotfix?
Risk assessment
none