bec/debye_bec
0
0
Fork 0
Code Issues 9 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Handling of Async Signals for NIDAQ #18

New Issue
Open
opened 2025-05-07 13:03:41 +02:00 by appel_c · 0 comments
appel_c commented 2025-05-07 13:03:41 +02:00 (Migrated from gitlab.psi.ch)
Copy Link

This should be picked up again once we worked on PSIComponent, once we have a proper way to deal with signals from async devices that should be monitored. Currently, the NIDAQ either send data directly to BEC (xas scans), or to EPICS channels for all other types of scan. We would like data to appear in both cases for the same signal.

This should be picked up again once we worked on `PSIComponent`, once we have a proper way to deal with signals from async devices that should be monitored. Currently, the NIDAQ either send data directly to BEC (xas scans), or to EPICS channels for all other types of scan. We would like data to appear in both cases for the same signal.
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 issue::reproducible priority::nice to have scope::backend type::improvement
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 clark_a debenjak_l divall_e hitz_s lombosi_c nachtegaal perl_d tiefenbacher_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/debye_bec#18
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?