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

ROI cutting (Threshold) #105

Open
linzuzeng opened this issue Dec 20, 2019 · 3 comments
Open

ROI cutting (Threshold) #105

linzuzeng opened this issue Dec 20, 2019 · 3 comments
Assignees
Labels
feature A certain type of analysis that ETA can not do yet. GUI Features related to the GUI recipe issue related to a built-in recipe

Comments

@linzuzeng
Copy link
Member

linzuzeng commented Dec 20, 2019

We can maintain an old copy of the "result['h3']", and calculate the difference result_diff between current "result['h3']" and the old "result['h3']". We also need "result['countrate'][0]" which comes from the Virtual Instrument copied from the "countrate" recipe.
In the meantime, we consider if "result['countrate'][0]>threslold", then we add that result_diff to the final histogram variable, for live display or file saving. Otherwise we discard result_diff of this section.

I don't understand what i said

@linzuzeng linzuzeng added recipe issue related to a built-in recipe feature A certain type of analysis that ETA can not do yet. labels Dec 20, 2019
@linzuzeng linzuzeng changed the title Threshold ROI cutting (Threshold) Mar 12, 2020
@linzuzeng linzuzeng added the GUI Features related to the GUI label Mar 12, 2020
@linzuzeng
Copy link
Member Author

Samuel:
https://docs.bokeh.org/en/dev/docs/gallery/range_tool.html
bokeh/bokeh#7795
I think we could use that for defining the regions.

@linzuzeng linzuzeng pinned this issue Mar 12, 2020
@linzuzeng linzuzeng unpinned this issue Mar 15, 2020
@linzuzeng
Copy link
Member Author

linzuzeng commented Sep 27, 2021

Lucas:
fnAHgZrYVkoLdIzfxrofCgma

@linzuzeng
Copy link
Member Author

linzuzeng commented Sep 27, 2021

you can simply write a FORMAT_QT_RAW to disk and use it with Lucas' solution as if shutter events are recorded physically

Maybe we can make a generic toolkit to add markers to a histogram and save the markers into memory with FORMAT_QT_RAW. I think the tricky part would be how to get the GUI work.

user_marker = Clip() 
user_marker.buffer=np.asbytes(....)
user_marker.RecordType=eta.FORMAT_QT_RAW
user_marker.BytesofRecords=10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A certain type of analysis that ETA can not do yet. GUI Features related to the GUI recipe issue related to a built-in recipe
Projects
None yet
Development

No branches or pull requests

3 participants