Re: Autosave -- debug output when field is updated

["Mooney, Tim M." <mooney@aps.anl.gov>]

Hi Evan

You can invoke this function at the ioc console:

save_restoreSet_Debug(int debug_level)

debug_level==10 will give you a lot of output, but it won't tell you which PV is the problem.  

One easy way to narrow the list of possible culprits is to specify that a sequence file be written, and specify a short period:

# Number of sequenced backup files to write

save_restoreSet_NumSeqFiles(1)

# Time interval between sequenced backups

save_restoreSet_SeqPeriodInSeconds(10)

Then you can diff, for example, auto_settings.sav and auto_settings.sav0

Tim Mooney (mooney@aps.anl.gov) (630)252-5417
Beamline Controls Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab

---

From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> on behalf of Daykin, Evan <daykin@frib.msu.edu>
Sent: Tuesday, February 13, 2018 12:50:03 PM
To: tech-talk@aps.anl.gov
Subject: Autosave -- debug output when field is updated

 

Hello,

 

Apologies in advance if this is in the documentation somewhere, I was unable to find it.

We have an IOC which uses quite a lot of CPU when autosave is turned on. This is most likely the result of some inadvertently autosaved fields being updated at 100Hz. Is there a straightforward way, such as an IOC shell command, to print some debug output whenever an autosaved field is written?

 

Best,

Evan