Skip to content
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

'filter data' makes trigger reconstruction difficult/impossible #23

Open
153957 opened this issue Nov 12, 2013 · 1 comment
Open

'filter data' makes trigger reconstruction difficult/impossible #23

153957 opened this issue Nov 12, 2013 · 1 comment
Labels

Comments

@153957
Copy link
Member

153957 commented Nov 12, 2013

The filter data filter can cause all values in a trace to be below the thresholds, making it had to find the trigger moment. Moreover, sometimes there are multiple solutions for reconstructing the original from the filtered data.

Interface - Show filtered data in the interface, use this to determine the pulse height and pulse integral, but keep a switch to toggle the filter on/off only for the interface.
Datastore - Send the unfiltered data to the datastore, so we can properly reconstruct information like the trigger time.

@153957
Copy link
Member Author

153957 commented Jul 13, 2016

Should be fixed in v4, the filter is not used for data sent to the datastore.
Verify with @vaneijk .

@153957 153957 removed the bug label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants