EPICS Home

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  <20162017  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  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: asyn: drvInfo string vs. EPICS record name
From: Phil Atkin <[email protected]>
To: [email protected]
Date: Fri, 5 Feb 2016 15:07:07 +0000
areaDetector drivers and plug-ins seem to (mainly) use different names for these: for example

    drvInfo string: QUEUE_SIZE
    EPICS record name: $(P)$(R)QueueSize

Is there any reason for this?  Any reason they should not be QueueSize and $(P)$(R)QueueSize, or even QUEUE_SIZE and $(P)$(R)QUEUE_SIZE?  As far as I can see, the drvInfo string is not visible to any client.

Thanks,

Phil
--
Pixel Analytics is a limited company registered in England. Company number: 7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP

Replies:
RE: asyn: drvInfo string vs. EPICS record name Mark Rivers

Navigate by Date:
Prev: Re: CSS Boy scripting, clear XY-Graph automatically Kasemir, Kay
Next: Re: BOY Linking Container doesn't support OPI Search Path? Kasemir, Kay
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Omega iR2 Temperature controller Mazanec Tomáš
Next: RE: asyn: drvInfo string vs. EPICS record name Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024