-
Notifications
You must be signed in to change notification settings - Fork 5
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
DECTRIS support; use PipelinedExecutor for live processing #51
Conversation
d3256d6
to
6b4e2e8
Compare
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Codecov Report
@@ Coverage Diff @@
## master #51 +/- ##
==========================================
- Coverage 81.93% 73.56% -8.38%
==========================================
Files 17 23 +6
Lines 1467 2474 +1007
Branches 218 388 +170
==========================================
+ Hits 1202 1820 +618
- Misses 216 551 +335
- Partials 49 103 +54
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
@matbryan52 pushed an example notebook into the prototypes folder in 407032d |
Thanks! Finally had a moment to look at this and can confirm I got it running on a MIB dataset acquired here. Just had to increase the maximum open files limit as it's a one-file-per-frame type of dataset. I admit it also took me a while to figure out I needed to use the |
Thank you for testing - yeah, in the other example notebooks, we had docs on this directly in the notebook, which I forgot to add to this one. Sorry about that, hope it didn't waste too much time. There is a question if we should change the defaults to something sensible - @uellue what do you think? I'm mostly starting the simulator with FYI: the example notebook needs updates again, as I changed the |
Yep, I just updated (I had to force update the branch bizarrely ?) and am letting the executor decide its own spec. Still working. Am going to try to look more into the code this afternoon, around the meetings. Is there anything in particular that I should focus on at this point? I haven't tried |
Yes, sounds good to change the trigger default. Since we have the "experimental" disclaimer in the docs, we can probably just change it with a changelog notice. I usually don't cache and didn't notice much of a difference. Also, memfd is only supported on Linux. Maybe we can leave the default cache behavior as "no cache", or did you notice any misbehavior? Regarding trigger, what about still accepting |
I don't really use the non-cached case, so 🤷 I mostly built the Directly comparing, without
Sounds good - means we don't have to update our notebooks, probably... Let's do this in a separate PR. |
Sorry about that, that was me rebasing to current
👍
For testing, mostly running different UDFs would be valuable - to sniff out any issues around serialization or scattering for example. Anything that is a bit more involved than the UDFs included with LiberTEM itself would be useful. Also, trying "edge cases" around error handling or startup/shutdown sequences. One current limitation in the As for code review, I think the most important parts are the new interfaces in |
Understood, just for now I've started writing / implementing some test cases without looking too deeply at the code. In fact I already found one issue where a UDF raising a bare |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
It seems we can tackle running the tests in CI as soon as LiberTEM 0.10 is |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
A very simple file format: int64 length field followed by bytes of that length per message.
Azure Pipelines successfully started running 1 pipeline(s). |
This comment was marked as duplicate.
This comment was marked as duplicate.
Azure Pipelines successfully started running 1 pipeline(s). |
* Switch to RTD theme * Run the dectris sim in docs-check to check the example code * Separate sections for API reference and user documentation * Add verbosity switch in dectris sim to make sphinx doctest happy (it's not yet possible to ignore output of testsetup / testcleanup directives) * dectris sim: catch StopException
for more information, see https://pre-commit.ci
Azure Pipelines successfully started running 1 pipeline(s). |
This comment was marked as outdated.
This comment was marked as outdated.
Azure Pipelines successfully started running 1 pipeline(s). |
for more information, see https://pre-commit.ci
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
From my perspective, this is the major item still blocking the PR - we could also handle this as a separate issue, but at least before the release the copyright header should be fixed. Notes on the code coverage:
Further efficiency improvements are definitely possible, but IMHO can and should be done once this is merged (also important to unblock #56) |
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.
Looks good to me! 🏆
Thx @sk1p!
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Merging! |
Support for DECTRIS detectors supporting the SIMPLON API, including support for the new
PipelinedExecutor
.This also updates the Merlin support to use the new
PipelinedExecutor
.TODO
DEigerClient
copyright noticeContributor Checklist:
Reviewer Checklist:
/azp run libertem.libertem-live-data
passed