RE: NDPluginFile attribute saving

[Mark Rivers <rivers@cars.uchicago.edu>]

Hi Steve,

What version of ADCore are you using?  The way capture mode is handled was changed in R3-2.  See the release notes:

https://github.com/areaDetector/ADCore/blob/master/RELEASE.md

In R3-2 I think it will do what you want, but previously it probably did not handle attributes correctly.

Is there a reason you are using capture mode rather than stream mode?  I recommend using stream mode.  Prior to R2-5 there was a reason to use Capture mode because the QueueSize for a plugin was fixed at iocInit and could not be changed a run-time.  Since R2-5 the QueueSize for all plugins can be changed at run-time.  It is generally better to set a large QueueSize and use stream mode rather than capture mode because:
- It always handles the attributes correctly, even prior to R3-2.
- File writing is overlapped with data collection so it reduces the total time for the experiment
- The memory overhead is less because it only needs to buffer the frames it cannot keep up with writing to disk, rather than buffering all frames in memory.

Capture mode may be deprecated in a future release of ADCore because it complicates the code and offers no real advantages any more.

Mark


-----Original Message-----
From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Steve Kinder - UKRI STFC
Sent: Tuesday, May 1, 2018 12:08 PM
To: tech-talk@aps.anl.gov
Subject: NDPluginFile attribute saving

I have an areaDetector file plugin saving a specific HDF5 structure with multiple images in one file. I set attributes to be saved per image via NDAttributesFile. I'm currently using capture mode. At the moment each image seems to have the same parameter values; as at the point the file is written. Is there a way for the attribute values to be as they were at the point each image is collected? Maybe I missed something in creating the plugin, some other setting or the attributes XML file?


Thanks


Steve