bec/csaxs_bec
0
0
Fork 1
Code Issues 13 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

MCS Card readouts #132

New Issue
Open
opened 2026-01-23 13:32:42 +01:00 by appel_c · 0 comments
appel_c commented 2026-01-23 13:32:42 +01:00
Owner
Copy Link

It should be tested if the readout cycles from the MCS card can be moved from passive to a timed reading and whether this improves the performance. There should be a test that checks the amount of time spent in complete of the MCS CARD, and whether the performance decreases if ~1e6 points are buffered before data is sent out. This could be improved by using an alternative triggering of the readout. Currently it is set to passive (mcs.read_mode).

It should be tested if the readout cycles from the MCS card can be moved from passive to a timed reading and whether this improves the performance. There should be a test that checks the amount of time spent in `complete` of the MCS CARD, and whether the performance decreases if ~1e6 points are buffered before data is sent out. This could be improved by using an alternative triggering of the readout. Currently it is set to passive (mcs.read_mode).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
issue::not confirmed
Used if an issue has not yet been confirmed by a developer
 issue::not reproducible
Used if an issue is not reproducible
 issue::reproducible
Used if a developer was able to reproduce the issue
 priority::critical
Should be done as soon as possible
 priority::needed
An important update to the code base
 priority::nice to have
Not really needed but a good improvement
 scope::backend
An issue regarding the backend services
 scope::frontend
An issue regarding the user-facing services
 stage::in development
This issue is currently being worked on
 stage::on hold
Something is blocking the development
 stage::pre_release
For issues that have been merged into a pre-release branch and are waiting for their release.
stage::ready for review
For issues that have been resolved and are ready for review
 stage::selected for development
This issue has been selected for development but has not been scheduled yet
 stage::weekly backlog
This issue has been selected for development for the next development cycle
 type::bug
It's a bug!
 type::discussion
A discussion is wanted/needed
 type::doc
Improvements to the documentation
 type::feature
A new feature
 type::improvement
Neither a feature nor a bug but an improvement to the code base
 type::test
Missing tests or improvements to the test suite
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
acerbo_a appel_c bec_bl_push-gitea bec-gitea celcer_t debenjak_l diaz divall_e guizar_m holler lombosi_c menzel perl_d stubbs_s usov_i wakonig_k wang_x1 wyzula_j zamofing_t
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bec/csaxs_bec#132
Delete Branch "%!s()"

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?