Merge feature branch of Debye back to main #51
Reference in New Issue
Block a user
Delete Branch "resolve_mr_conflict"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
MR with various online changes and developments in the weeks preparing for the first commissioning with beam. Before merging to main, the code should be tested at the beamline.
closes #11 #9 #8 #5
TODO
Note:
Extra tests should be added later on to ensure functionality of integrations and scans.
assigned to @appel_c
changed the description
requested review from @wakonig_k and @clark_a
added 1 commit
6ab1a294- fix: fix typo in device config mo1_braggCompare with previous version
added 1 commit
03e3b1c6- fix: fix imports in basler_camCompare with previous version
added 1 commit
32e24cd9- fix: fix occasional crash of mo1_bragg for scan; closes #11Compare with previous version
added 4 commits
24d81bb1- build: update black dependency to ~=25.0002a3323- fix(ion-chambers): fix ion chamber code at beamline31ff2823- fix: update config, remove cameras for the moment7b7a24b6- refactor: formattingCompare with previous version
marked the checklist item Fix occasional error upon calling stage after restarting the server. #10 as completed
marked the checklist item Investigate whether complete method logic is now properly implemented #3 as completed
marked the checklist item Test codes at the beamline, scheduled for Wednesday 7th. as completed
marked this merge request as ready
changed title from {-Draft: Resolve mr conflict-} to {+Merge feature branch of Debye back to main+}
changed the description
added 1 commit
74e0b01b- fix: temporary comment, issue created #16Compare with previous version
In addition, this closes #17 .
this will never be the case, no?
I think you want
same for all the following checks
I'd suggest to use the same kind of checks for all ranges, just for consistency
we should probably add all the boilerplate code for PSIDeviceBase. But this can also be done in another MR
Looks good at first glance!
Yeah, agreed. This should be in the template! I fix the things above!
changed this line in version 7 of the diff
added 1 commit
Compare with previous version
resolved all threads
added 1 commit
Compare with previous version
changed this line in version 9 of the diff
added 1 commit
b03b90a8- fix: fix range checks in Mo1Bragg and IonizationChamberCompare with previous version
approved this merge request
mentioned in issue #17
mentioned in issue #10