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  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024 
<== Date ==> <== Thread ==>

Subject: Re: How is EPICS used at your facility?
From: bob dalesio via Tech-talk <tech-talk at aps.anl.gov>
To: "Leblanc, Gregory" <leblanc at ohio.edu>, EPICS tech-talk <tech-talk at aps.anl.gov>
Date: Wed, 15 Mar 2023 08:08:42 -0400
How it is used can be inferred by the version and clients tools in use.

Version 3, channel access protocol, time series archiver, alarm manager, are SCADA tools and can produce DCS steady state co n trol.

SNL, scan records, scan tool in CSStudio, are state transition control.

The areaDector package adds DAQ for NDimensional data.

Model Based Control is done in different ways bit Matlab Middle Layer Toolkit is a good example for this type of control.

The most recent improvements are in beam related instruments that are FPGA based with GHz sampling rates and feedback or machine protection in the few microseconds to 100s of microseconds limited by the length of fiber and time through fpga nodes. For accelerators and science this Isa game changer.

Epics 7 and the pvAccess protocol support these new instruments with aggregated data sets, ND Array, table, image and statistics. This supports scientific data acquisition for experimental data and AI/ML.

It is difficult to get good information from this query on specific sites. The web site for EPICS does not attempt to list all facilities or users. 

Good luck in your endeavor,
Bob

On Tue, Mar 14, 2023, 5:11 PM Leblanc, Gregory via Tech-talk <tech-talk at aps.anl.gov> wrote:
How do you use EPICS at your facility?  We aren't using it yet and I am trying to make some design decisions before I get very far down the implementation road.  The thread last week about SCAN issues and the archiver appliance brought some of these to mind.

How many data points do you collect?
How fast do you collect data?
Do you archive every datapoint you collect? 
Do you archive data slower than you collect it?
What are you using to archive data (EPICS Archiver Appliance, CSS, Phoebus, other?)?
How many IOCs do you have, and how do you decide when you need a new IOC vs extending an existing IOC?
What do you use for visualization (CSS, Phoebus, custom solution (based on qtepics?), something else)?

I'm sure I could come up with a dozen more questions about how EPICS is implemented, but maybe another time.
    Greg

P.S. If there's interest in collecting any of this data I could put together a survey and make the data available (Ohio has some decent survey data collection tools).

--
Gregory Leblanc
Accelerator Engineer
Edwards Accelerator Lab - Ohio University
123 University Terrace
Athens, OH 45701 USA
leblanc at ohio.edu
M: (401) 52-OUAL1 or (401) 526-8251


References:
How is EPICS used at your facility? Leblanc, Gregory via Tech-talk

Navigate by Date:
Prev: RE: How is EPICS used at your facility? GAGET Alexis via Tech-talk
Next: areaDetector documentation changes Mark Rivers via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024 
Navigate by Thread:
Prev: RE: How is EPICS used at your facility? GAGET Alexis via Tech-talk
Next: Re: How is EPICS used at your facility? Kasemir, Kay via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024 
ANJ, 15 Mar 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·