RE: ADPilatus writing cbf strangeness

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

You should also enable ASYN_TRACEIO_DRIVER on the asyn port that is communicating with camserver and see what is happening there.

 

Mark

 

 

 

From: John Dobbins <john.dobbins at cornell.edu>
Sent: Friday, December 10, 2021 10:29 AM
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: Jacob Ruff <jpr243 at cornell.edu>; tech-talk at aps.anl.gov
Subject: Re: ADPilatus writing cbf strangeness

 

Mark,

 

Yes, the filepath for the IOC is PPU ramdisk. I will investigate per your suggestion.

 

John

---

From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Friday, December 10, 2021 11:22 AM
To: John Dobbins <john.dobbins at cornell.edu>
Cc: Jacob Ruff <jpr243 at cornell.edu>; tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: RE: ADPilatus writing cbf strangeness

 

Hi John,

 

What is the FilePath you are using for ADPilatus?  Is it reading from the PPU ramdisk? 

 

I suggest you run camonitor on one of the PVs that updates each time ADPilatus reads a CBF file and does NDArray callbacks.  Is it gradually falling behind the detector so that after N images the allowed timeout has been reached?  Have you looked at “top” to see if the ADPilatus task is CPU bound, perhaps because the time to read the CBF files is longer than the time between when they are created?

 

Mark

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of John Dobbins via Tech-talk
Sent: Friday, December 10, 2021 10:15 AM
To: tech-talk at aps.anl.gov
Cc: Jacob Ruff <jpr243 at cornell.edu>
Subject: ADPilatus writing cbf strangeness

 

All,

 

I am hoping you can help me understand what is happening when I try to write cbf files from a PILATUS 6M.

 

ADCore 3.9 ADPilatus Driver 2.9 

 

If I write tiff files everything seems fine.

 

When I write cbf files it works for slow acquisition rate, say 1 Hz.

 

At ~ AcquirePeriod = 0.35, ExposureTime =0.09, NumImages =20

internal trigger

 

PIL10:cam1:StatusMessage_RBV reports a series of messages like

 

"Reading Image File ....."

 

But after ~ 13 or 14 images I get a message

 

"Timeout waiting for file to be created"

 

All 20 images appear to be written normally to disk. 

 

I tried changing PIL10:cam1:ImageFileTmot from 5 to 10 to 20 but this doesn't seem to have any effect other than delaying the appearance of the error message.

 

 

Note our set-up is:

 

DCU runs camserver, collects images from detector which it writes to local ramdisk

 

PPU hosts IOC which communicates with camserver

 

Furka copies images from DCU ramdisk to PPU rammdisk, Grimsel copies images from PPU ramdisk to final destination (a network location)

 

Any guidance would be appreciated.

 

John Dobbins

 

Research Support Specialist

Cornell High Energy Synchrotron Source

Cornell University

 

www.chess.cornell.edu