1. Open new bottom is not very convenient, we need both the old and new day of reading the files
2. Conversion of the Gamma and Nu values is wrong (on individual frames it is done correctly)
3. For nb-geomtery do not print Chi and Phi values
*Created by: zaharko*
- [x] 1. Open new bottom is not very convenient, we need both the old and new day of reading the files
- [x] 2. Conversion of the Gamma and Nu values is wrong (on individual frames it is done correctly)
- [x] 3. For nb-geomtery do not print Chi and Phi values


Concerning 3. , since Chi and Phi values are subsequently used in spind panel, I assume that hiding Chi and Phi should be just a visual effect in that table (e.g. without removing them from data)?
*Created by: ivan-usov*
Concerning 3. , since Chi and Phi values are subsequently used in spind panel, I assume that hiding Chi and Phi should be just a visual effect in that table (e.g. without removing them from data)?
Yes, this is a visual effect in 'hdf viewer'.
Chi and Phi for the NB geometry are set to 0 within the crystallographic calculations of Pyzebra.
Our acquisition program writes some weird numbers (which we will fix hopefully this winter shutdown)
On 9 Nov 2021, at 11:53, Ivan Usov @.@.>> wrote:
Concerning 3. , since Chi and Phi values are subsequently used in spind panel, I assume that hiding Chi and Phi should be just a visual effect in that table (e.g. without removing them from data)?
*Created by: zaharko*
Yes, this is a visual effect in 'hdf viewer'.
Chi and Phi for the NB geometry are set to 0 within the crystallographic calculations of Pyzebra.
Our acquisition program writes some weird numbers (which we will fix hopefully this winter shutdown)
On 9 Nov 2021, at 11:53, Ivan Usov ***@***.******@***.***>> wrote:
Concerning 3. , since Chi and Phi values are subsequently used in spind panel, I assume that hiding Chi and Phi should be just a visual effect in that table (e.g. without removing them from data)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/paulscherrerinstitute/pyzebra/issues/44#issuecomment-964034632>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBMFVCQWZUQ2VSEJE3BNGTULD4RRANCNFSM5HSQI2DA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/44#issuecomment-964034632", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/44#issuecomment-964034632", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Created by: zaharko
Created by: ivan-usov
Concerning 3. , since Chi and Phi values are subsequently used in spind panel, I assume that hiding Chi and Phi should be just a visual effect in that table (e.g. without removing them from data)?
Created by: zaharko
Yes, this is a visual effect in 'hdf viewer'.
Chi and Phi for the NB geometry are set to 0 within the crystallographic calculations of Pyzebra.
Our acquisition program writes some weird numbers (which we will fix hopefully this winter shutdown)
On 9 Nov 2021, at 11:53, Ivan Usov @.@.>> wrote:
Concerning 3. , since Chi and Phi values are subsequently used in spind panel, I assume that hiding Chi and Phi should be just a visual effect in that table (e.g. without removing them from data)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/paulscherrerinstitute/pyzebra/issues/44#issuecomment-964034632, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMBMFVCQWZUQ2VSEJE3BNGTULD4RRANCNFSM5HSQI2DA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/44#issuecomment-964034632", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/44#issuecomment-964034632", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
Created by: ivan-usov
The does it make sense to set them to 0 for NB upon reading in h5.py? We can then still hide those zeros in the table.