-
Notifications
You must be signed in to change notification settings - Fork 11
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
Added an optional frameswritten setter #67
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #67 +/- ##
==========================================
- Coverage 96.35% 96.29% -0.07%
==========================================
Files 12 12
Lines 1180 1187 +7
==========================================
+ Hits 1137 1143 +6
- Misses 43 44 +1 ☔ View full report in Codecov by Sentry. |
e3ad641
to
715bd5f
Compare
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.
Couple of minor comments, can we write a test that the file number comes out of the end of the pipeline?
418ab45
to
70feb3f
Compare
1465540
to
8fbe219
Compare
@coretl completely forgot about adding the test till now. dmgav approved the ioc side add_ringbuffer PR so after this is released I'll merge and release that if CI is all good? |
Added a new thread that sets the NumCaptured PV Added a new EndReason
Added a test to verify that the number of frames written is passed downstream in the pipeline
28ee7da
to
14dcc00
Compare
Added an optional setter in the HDF5 writer to set a record detailing the number of frames written.
We require merging and release of this PR before the ioc side: PandABlocks/PandABlocks-ioc#83
According to DiamondLightSource/pythonSoftIOC#142, the set of a record should be thread safe, but we should do some testing before we release.