metafile *.cami

[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:

• I suggest to give path in 'rootpath' and in 'filelist' only the filenames

  #begin rootpath
  /afs/psi.ch/project/sinqdata/2021/zebra/20211324/
  #end rootpath
  #begin filelist
  zebra2021n002539.hdf
  zebra2021n002540.hdf
  #end

• dist1 is located in /entry1/ZEBRA/SINQ/area_detector/distance

  #begin detector parameters
  dist1=538
  #end

• zebra_mode=nb or bi is located in /entry1/zebra_mode 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

  #begin zebra_mode
  nb
  #end

• name, UB, cell h,k,l, is 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

  #begin crystal
  name=CePdIn
  UB=-0.148595,-0.0572272,0.013334,-0.0205403,-0.138141,-0.0292135,0.0055983,-0.0132632,0.246737
  cell=  7.073600 7.073600 4.019000 90. 90. 90.
  lambda=1.178
  #end

[ivan-usov]

Changed from

#zebra_mode
nb
#zebra_mode

to

#begin zebra_mode
nb
#end

which is consistent with the rest of .cami specs

[ivan-usov]

I would suggest to keep rootpath and filelist as they were before, otherwise one would need to modify all old .cami files

[ivan-usov]

Is it dist1 or dist2? And I believe the path in hdf is /entry1/ZEBRA/area_detector2/distance, is it correct?

[ivan-usov]

I would suggest to either separate cell values with commas, or separate UB values with spaces, so that both are consistent

[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" } } ]

[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" } } ]

[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.