EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: autosave: makeAutosaveFiles()
From: Wesley Moore <[email protected]>
To: Michael Stanley Zelazny <[email protected]>
Cc: EPICS tech-talk <[email protected]>
Date: Thu, 02 Aug 2012 11:36:09 -0400 (EDT)
I looked at doing that, must have goofed up something.  I see you like your epics threads well rested... ;)

----- Original Message -----
> From: "Michael Stanley Zelazny" <[email protected]>
> To: "EPICS tech-talk" <[email protected]>
> Sent: Thursday, August 2, 2012 11:27:03 AM
> Subject: RE: autosave: makeAutosaveFiles()
> 
> I cd to the directory before making the files:
> 
> [snip]
> ## Start saving datasets
> cd("${IOC_DATA}/${IOC}/autosave-req")
> epicsThreadSleep(1)
> makeAutosaveFiles()
> epicsThreadSleep(1)
> create_monitor_set("info_settings.req",60,"")
> epicsThreadSleep(1)
> create_monitor_set("info_positions.req",60,"")
> epicsThreadSleep(1)
> [snip]
> 
> IIRC the sleeps make a difference, but I forget why at the moment.
>  Maybe lore from long ago.
> 
> ________________________________________
> From: [email protected] [[email protected]]
> On Behalf Of Wesley Moore [[email protected]]
> Sent: Thursday, August 02, 2012 8:18 AM
> To: EPICS tech-talk
> Subject: autosave: makeAutosaveFiles()
> 
> Techies,
>     makeAutosaveFiles() dumps everything into the IOC's directory by
>     default and I'd rather not clutter it up.  So I call
>     makeAutosaveFileFromDbInfo() directly as a work-around.  Is this
>     how others handle this or am I missing another trick?  Could
>     this be a nice thing to easily add to autosave?  Something like
>     makeAutosaveFiles("newdir/path")...
> 
> Here's what I've come up with as my work-around:
> 
> #
> # from st.cmd...
> #
> #makeAutosaveFiles()
> makeAutosaveFileFromDbInfo("autosave/req/info_settings.req",
> "autosaveFields");
> makeAutosaveFileFromDbInfo("autosave/req/info_positions.req",
> "autosaveFields_pass0");
> create_monitor_set("info_positions.req",30)
> create_monitor_set("info_settings.req",30)
> 
> It works fine.  Just more curious about what you guys do.
> 
> Wesley
> 
> 

References:
RE: autosave: makeAutosaveFiles() Zelazny, Michael Stanley

Navigate by Date:
Prev: RE: autosave: makeAutosaveFiles() Zelazny, Michael Stanley
Next: EPICS Support for Kashiyama Mu100/Mu300 Vacuum Pump? Boyes, Matthew
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: autosave: makeAutosaveFiles() Zelazny, Michael Stanley
Next: EPICS Support for Kashiyama Mu100/Mu300 Vacuum Pump? Boyes, Matthew
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·