Fixing imprecise TPR_TICK_NS constant #1306
Merged
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.
Description
Changing TPR_TICK_NS from 5.384 to 70/13. 5.384 is imprecise enough to cause large errors in _get_delay used by TprMotor.readback.get() and TprTrigger.ns_delay.get().
Motivation and Context
#1302
How Has This Been Tested?
Interactively (The error was due to a misspelling)
Where Has This Been Documented?
Pre-release notes
Pre-merge checklist