feat: Timestaming with UTAG #107
Merged
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
jerzyjamroz
changed the title
* First implementation, simple set/get UTAG * Remove I/O Intr link that is not needed * Adding UTAG for each event * Add new getTimeStampUTag method to avoid mutex being locked twice in a row * Minor adjust in UTAG setpoint record name * Fix typo on nanosseconds assignment; convertTS is now template * Overload getTimeStamp; Use define guards to compile for older versions; Clean-up comments and defines * Additional comments and clean-up
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.
The timestamping can be used in two ways from now on:
evreventutag.dbinstead ofevrevent.db. UTAG value is applied by writing into:"$(EN)-SP"record, the timestamp+UTAG is provided by$(EN)Cnt-Irecord (EPICS Base 7 or higher).evrevent.dband ignoreevreventutag.db, the timestamp is provided by$(EN)Cnt-Irecord, so as it was before (legacy).The solution is based on the: