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: Links between bob files in different support modules
From: Andrew Johnson via Tech-talk <tech-talk at aps.anl.gov>
To: "Cobb, Tom (DLSLtd,RAL,LSCI)" <tom.cobb at diamond.ac.uk>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Tue, 28 Mar 2023 11:03:47 -0500
Hi Tom,

An approach that I've introduced for APS-U is that at IOC build-time I'm having all our IOC applications copy the screens from their support modules into a $(TOP)/opi/<tool> directory. That ensures (a) the screens for a specific IOC area are all loaded from the same directory, and (b) the screens will always be appropriate for the version of the support modules the IOCs are loading. The IOC area also installs its own screens there, providing higher-level screens to call up the support screens with appropriate macros.

In our case these are adl files for MEDM which does have a search path, but MEDM searches the directory that the parent screen was loaded from before it tries the path (unless the screen is specified with an absolute filename). The IOC area has a Makefile with a 1-line wildcard to find the screen files for each support module.

If your operators won't have direct file-system access to the IOC build area you can always package up the IOC's opi/<tool> directory to install or rsync it elsewhere.

We still have some unresolved issues in this design on how to get to the inner screens of an IOC from higher-level system screens; the idea of using macros that Paul mentioned might help there, but I haven't really thought about that much yet.

HTH,

- Andrew


On 3/28/23 5:02 AM, Cobb, Tom (DLSLtd,RAL,LSCI) via Tech-talk wrote:
Hi all,

We are looking at how to structure bob files within our support modules, especially how to link between support modules. For example, imagine we have a bob file ASupport/ASupportApp/op/bob/A_details.bob​ and we want to link to BSupport/BSupportApp/op/bob/B_details.bob​. As phoebus doesn't support a search path (for good reasons) we would need to supply an absolute or relative path to B_details.bob​ in A_details.bob​. My instinct is to use relative paths, so the directory tree can be served over http at runtime, but this means a link to ../../../BSupport/BSupportApp/op/bob/B_details.bob​ in A_details.bob​ which mandates that the two support modules be checked out next to each other.

Has anyone else had to link between bob files in two different support modules? If so, how have you done it?

Thanks,
Tom

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 


-- 
Complexity comes for free, Simplicity you have to work for.

References:
Links between bob files in different support modules Cobb, Tom (DLSLtd,RAL,LSCI) via Tech-talk

Navigate by Date:
Prev: MEDM font alias woes on Ubuntu 22 (Jammy) Stein, Samuel Joshua via Tech-talk
Next: Re: MEDM font alias woes on Ubuntu 22 (Jammy) Pete Jemian 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: Links between bob files in different support modules Mark Rivers via Tech-talk
Next: MEDM font alias woes on Ubuntu 22 (Jammy) Stein, Samuel Joshua 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, 28 Mar 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·