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 2023 2024 | 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 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Listing channels |
From: | Ned Arnold <[email protected]> |
To: | David Dudley <[email protected]> |
Cc: | [email protected] |
Date: | Wed, 7 May 2008 07:55:42 -0500 |
David, Reply to #1) At the end of every one of our [280+] st.cmd files we have the following commands: cd "/iocinfo/pvdata" dbl(0,iocname) This gives us a file for each IOC which contains the names of the PVs it has. A simple "grep" then identifies which IOC a PV resides in. It seems that a simple GenSub record could use dbl to but the list in a waveform record, but I'm not sure how many tools out there are capable of handling an array of strings. Also, there is also an EPICS tool around called IRMIS (http://www.aps.anl.gov/epics/irmis/index.php) that includes scripts that "crawl" the st.cmd file of every IOC and recreates the PV definitions in a relational database so even the definitions of the PVs can be perused via the web. This captures the data from the .dbd and .db files, so it doesn't matter what tool the application developer used to define them (vi, vdct, Capfast, etc). Other crawlers create another database which records which PVs are used by which CA clients (medm, alh, sdds, sequencer, other db files, etc). Reply to #2) APS has a very extensive set of data archive/viewer tools based on SDDS. Contact Bob Soliday for further info. Ned On May 6, 2008, at 9:26 PM, David Dudley wrote: Got 3 little questions: |