@qzhang234 - Please confirm this is what you described to me.
The XPCS index number should increase with each collection. For a plan with nframes=1_000, number_of_collection_points=20, the HDF5 plugin should create 20 separate HDF5 files, each containing 1,000 frames. Each of these files was measured at a different sample (x,y), according to the plan's arguments.
Each image file's base name should be constructed like this example: D001_144_BlueskyTest-01000
D001 - user-supplied XPCS header
144 - the XPCS index (increments with each collection, initialized by user during setup plan)
BlueskyTest - user-supplied title
01000 - user-supplied number of frames nframes
Instead of a single image file (such as collected by the xpcs_bdp_demo_plan() plan), this plan will collect many files. We'll need to keep track of them in the plan and inform the workflow.
prjemian
commented
2 hours ago
@qzhang234 - Please confirm this is what you described to me.
The XPCS index number should increase with each collection. For a plan with
nframes=1_000, number_of_collection_points=20, the HDF5 plugin should create 20 separate HDF5 files, each containing 1,000 frames. Each of these files was measured at a different sample (x,y), according to the plan's arguments.Each image file's base name should be constructed like this example:
D001_144_BlueskyTest-01000D001- user-supplied XPCS header144- the XPCS index (increments with each collection, initialized by user during setup plan)BlueskyTest- user-supplied title01000- user-supplied number of framesnframesInstead of a single image file (such as collected by the
xpcs_bdp_demo_plan()plan), this plan will collect many files. We'll need to keep track of them in the plan and inform the workflow.Originally posted by @prjemian in https://github.com/aps-8id-dys/bluesky/issues/87#issuecomment-2423040354