bug: SST1RSoXSDB scan hinting breaks if a scanned axis has negative value
#121
Assignees
Comments
pdudenas
added a commit
that referenced
this issue
Apr 4, 2024
…ng-breaks-if-a-scanned-axis-has-negative-value `SST1RSoXSDB`: fix bug described in #121
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SST1 RSoXS data doesn't include any hinting of what motor was scanned in an explicit way, so
SST1RSoXSDBdoes a rather convoluted inspection process to figure out what motors moved significantly (as judged by the reduced standard deviation of the scan) and make only those motors dimensions of the resulting xarray. If a motor had negative values, due to a simple math bug, the reduced standard deviation is negative and the dimension isn't automatically hinted.The text was updated successfully, but these errors were encountered: