...

/reg/neh/home/cpo/git/lcls2/psana/psana/dgramPort/jungfrau.xtc2
lcls2/xtcdata/xtcdata/app/jungfrau.cc - cpo
lcls2/psalg/psalg/tests/test_hsd.cc  - cpo + chuck
lcls2/psalg/psalg/tests/test_xtc_data.cc - my

XTC2 production

2019-07-24 two xtc2 files were generated in similar conditions for cspad and jungfrau, using examples

in lcls1 environmant:

~/LCLS/con-lcls2/ex-conv-xtc-00-parse_lcls1_data.py

similar to: https://github.com/slac-lcls/lcls2/blob/master/psana/psana/dgramPort/parse_lcls1_data.py

in lcls2 environmant:

~/LCLS/con-lcls2/ex-conv-xtc-01-translate_xtc_json.py

similar to: https://github.com/slac-lcls/lcls2/blob/master/psana/psana/dgramPort/translate_xtc_json.py

converted *.xtc2 files are moved to /reg/g/psdm/detector/data2_test/xtc/

XTC2 processing issue

2019-07-24 Now command like

• xtcreader -f /reg/g/psdm/detector/data2_test/xtc/data-xpptut15-r0430-e000010-jungfrau.xtc2 - works,
• xtcreader -f /reg/g/psdm/detector/data2_test/xtc/data-cxid9114-r0089-e000010-cspad.xtc2 - does not work for presumably corrupted data.

The same issue is seen in

psalg/tests/test_xtc_data.c, running as

test_xtc_data 11

Q to cpo: how to treat any problem with xtc corrupted data within current definition of all xtc objects? 

References

• 2019-01-29 cpo: Detector Interface Proposalxtcreader -f /reg/g/psdm/detector/data2_test/xtc/data-cxid9114-r0089-e000010-cspad.xtc2xtcreader -f /reg/g/psdm/detector/data2_test/xtc/data-xpptut15-r0430-e000010-jungfrau.xtc2in lcls1 environmant:n lcls1 environmant:ex-conv-xtc-01-translate_xtc_json.py