-
Notifications
You must be signed in to change notification settings - Fork 10
Why is there a get_max_countc? #62
Copy link
Copy link
Open
Labels
V2required to move towards share XPCS/speckle analysis for CHX/CSXrequired to move towards share XPCS/speckle analysis for CHX/CSX_commonspecklepart of V2, but strictly related to a common repo (speckle + maybe scattering)part of V2, but strictly related to a common repo (speckle + maybe scattering)question
Metadata
Metadata
Labels
V2required to move towards share XPCS/speckle analysis for CHX/CSXrequired to move towards share XPCS/speckle analysis for CHX/CSX_commonspecklepart of V2, but strictly related to a common repo (speckle + maybe scattering)part of V2, but strictly related to a common repo (speckle + maybe scattering)question
Type
Fields
Give feedbackNo fields configured for issues without a type.
It seems like there is a function in skbeam.roi that handles compressed data in the lowest level function for visibility (
xsvsc_single())?https://github.com/NSLS-II/pyCHX/blob/6e991bb1eb06d8fe1bc8f684ebfcec581ee57aba/pyCHX/chx_specklecp.py#L254-L255
Is this skbeam function wrong? Or was this an effort to have more control for technical reason specific to the CHX detector?