metafile *.cami #32
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Created by: zaharko
I write here entries from cami file which could be sometimes rewritten to perform correct calculations in pyzebra or any other new software working with zebra hdf files:
if the mode is nb the angles chi and phi should be nullified chi=0, phi=0
chi and phi are located in /entry1/sample
cell (6 entries) are located in hdf file or rewritten from here should be used in spind (now spind uses a dummy default)
lambda is located in /entry1/ZEBRA/monochromator/wavelength
Created by: ivan-usov
Changed from
to
which is consistent with the rest of .cami specs
Created by: ivan-usov
I would suggest to keep
rootpath
andfilelist
as they were before, otherwise one would need to modify all old .cami filesCreated by: ivan-usov
Is it
dist1
ordist2
? And I believe the path in hdf is/entry1/ZEBRA/area_detector2/distance
, is it correct?Created by: ivan-usov
I would suggest to either separate
cell
values with commas, or separateUB
values with spaces, so that both are consistentCreated by: zaharko
Ivan,
I am personally for no commas,
But the old software uses UB input with commas
Therefore I suggest to have presently commas in cell parameters and UB.
Oksana
On 29 Jun 2021, at 11:44, Ivan Usov @.@.>> wrote:
I would suggest to either separate cell values with commas, or separate UB values with spaces, so that both are consistent
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/paulscherrerinstitute/pyzebra/issues/32#issuecomment-870445331, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMBMFVDFOFRZPMIYSXW7V2LTVGIZJANCNFSM47ODBKJA.
[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/32#issuecomment-870445331", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/32#issuecomment-870445331", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
Created by: zaharko
I do not know should it be dist1 or dist2
How should we number them?
Dist1 for 1d detector
Dist2 for 2D detector?
You are right, the distance for the area detector is saved in
entry1/ZEBRA/area_detector2/distance
On 29 Jun 2021, at 11:36, Ivan Usov @.@.>> wrote:
Is it dist1 or dist2? And I believe the path in hdf is /entry1/ZEBRA/area_detector2/distance, is it correct?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/paulscherrerinstitute/pyzebra/issues/32#issuecomment-870439866, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMBMFVBMTSYQMER3BTA3PTLTVGHZPANCNFSM47ODBKJA.
[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/32#issuecomment-870439866", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/32#issuecomment-870439866", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
Created by: ivan-usov
OK, i'll go with
dist1
for now, and I don't have any strong opinion about the naming for the actual devices.