Re: DETRIS Eiger triggering

[John Dobbins via Tech-talk <tech-talk at aps.anl.gov>]

Bruno,

Thanks. That would explain it. I was taking a single series with FileWriter generating a single file.

John

---

From: Bruno Martins <brunoseivam at gmail.com>
Sent: Tuesday, November 17, 2020 11:40 AM
To: Matt Newville <newville at cars.uchicago.edu>
Cc: John Dobbins <john.dobbins at cornell.edu>; tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: DETRIS Eiger triggering

 

Of note, when using the "FileWriter" source, the driver waits (polls) until there are new files available on the detector's disk, then downloads the HDF5 files, then opens them and puts the contents in the areaDetector pipeline. If you are acquiring a small number of frames, or if you have set a large amount of frames per file, then you will only see the frame number increasing at the end of the acquisition, since probably all frames will fall into a single HDF5 file.

One way to test this is to lower your frames per file setting to be a fraction of the total number of frames expected. Then you will see the number of frames increasing in bursts (one burst every time a new data file is available).

Bruno

On Tue, Nov 17, 2020 at 11:15 AM Matt Newville via Tech-talk <tech-talk at aps.anl.gov> wrote:

Does  `cam1:NumImagesCounter_RBV` not report the number of images during collection for you?   

We use External Enable for triggered collection, set the number of Triggers to the expected value (maybe expected+1), and then that `cam1:NumImagesCounter_RBV` does report the current number of images.  FWIW, we use the "Stream" data source, not using the Dectris file-writing and stream to HDF5. With that, the HDF plugin `HDF1:NumCaptured_RBV` also shows the number of images captured to the file.

That's with an Eiger v1 500K detector with firmware 1.6.6, Eiger Driver 2.8, and ADCore 3.10.  

On Tue, Nov 17, 2020 at 9:46 AM John Dobbins via Tech-talk <tech-talk at aps.anl.gov> wrote:

All,

One odd thing about the Eiger detector (using areaDetector 3-10, latest ADEiger) is that once I 'Start' acquisition, whether Internal Series or External Series, there seems to be no live indicator of how many images have been acquired.

With Internal Series selected,  acquisition ends on its own when the requested number of images has been acquired and then ArrayCounter_RBV updates.

With External Series acquisition ends only when I send 'Stop', (I believe this has been reported) and then ArrayCounter_RBV updates.

Is there a way to get live updates of the number of acquired images?

Regards and thanks,

John Dobbins

Research Support Specialist

Cornell High Energy Synchrotron Source

Cornell University

www.chess.cornell.edu

--Matt