IPKM/python3-damaris
Public Access
3
0
Fork 0
Code Issues 7 Pull Requests Actions 2 Releases Activity

ADC_result should have a flag for clipped data #16

New Issue
Closed
opened 2026-03-26 14:10:51 +00:00 by markusro · 1 comment
markusro commented 2026-03-26 14:10:51 +00:00
Owner
Copy Link
Copy Source

ADC_Result should have a flag for clipped data. Ideally this should be already set from the backend upon recording and stored in the result file. The backend knows the bit depth of th ADC and could do that reliably. The front end could then have small warning or report shown.

ADC_Result should have a flag for clipped data. Ideally this should be already set from the backend upon recording and stored in the result file. The backend knows the bit depth of th ADC and could do that reliably. The front end could then have small warning or report shown.
markusro self-assigned this 2026-03-26 14:10:51 +00:00
markusro commented 2026-07-05 11:58:15 +00:00
Author
Owner
Copy Link
Copy Source

Fixed with commit d3b1a9e3fd

Entirely done in the front-end. Configurable with "adc_bit_depth" , defaults to 14bit.

Fixed with commit d3b1a9e3fd559b18ac0bb06916e956060441699b Entirely done in the front-end. Configurable with "adc_bit_depth" , defaults to 14bit.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
ckolb (Christian Kolb) mandal (Suvendu Mandal) markusro (Markus Rosenstihl)
No Assignees markusro
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: IPKM/python3-damaris#16
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?