-----Original Message-----
From: [email protected] <[email protected]> On
Behalf Of Jeong Han Lee via Tech-talk
Sent: Wednesday, August 21, 2019 6:55 PM
To: Johnson, Andrew N. <[email protected]>; EPICS tech-talk <tech-
[email protected]>
Subject: Re: Is anyone building AreaDetector with Sumo?
Hi Andrew,
On 8/21/19 8:14 PM, Johnson, Andrew N. via Tech-talk wrote:
I realise there probably aren't many sites out there using the HZB
Sumo package
<https://urldefense.proofpoint.com/v2/url?u=https-3A__goetzpf.bitbucke
t.io_sumo_&d=DwIDaQ&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9CpZ-
pCOw&r=x06s-qkiWY_RW6xat452vA&m=5vG3w0_2-
8knIdSfwVVSm2gDEe4AoiYEOu29dDnEHrQ&s=TJNyOGW4Nb6xD-N1PAEM-
vEkldFy8M6hcdcIVNAuYe8&e= >, but has anyone who does use it worked
out how to configure and build AreaDetector with it, either as a series of
separate modules or as one big module?
Unlike most EPICS modules AreaDetector has multiple kinds of RELEASE
files that need to be populated, and a non-trivial configuration
process (which is well-documented
<https://urldefense.proofpoint.com/v2/url?u=https-
3A__areadetector.github.io_master_install-
5Fguide.html&d=DwIDaQ&c=aTOVZmpUfPKZuaG9NO7J7Mh6imZbfhL47t9Cp
Z-pCOw&r=x06s-qkiWY_RW6xat452vA&m=5vG3w0_2-
8knIdSfwVVSm2gDEe4AoiYEOu29dDnEHrQ&s=_O2G_8bHNjJhozoYHWIZ9ZD
4zbLNsGkLL3Q0beFus3I&e= >).
The Sumo tool automates the configuration and building of sets of
EPICS modules on demand, but I'm not sure if it can cope with
configuring AreaDetector. If someone has succeeded in doing so I would
be grateful to hear details or ideas how best to approach it — I
haven't tried yet and I will need to do that soon.
If the Sumo tool does its job well with the most EPICS modules, I think,
the tool does the same job on the AreaDetector also. But we may not use
the current global configuration files of areadetector with the Sumo tool,
because here we (ESS) can build them as individual modules, and combine
"necessary components" to build "an Application" and run an IOC without
any issues.
For example, in order to see images from a PointGrey (FLIR) camera,
Here (ESS), we define system libraries and ADSupport clearly in terms of
OS. And we compile ADSupport as a module, And we compile ADCore which
has the maximum configuration options with both dependent libraries
(system and ADSupport) together. And we compile ADPointGrey according
to ADCore, ADSupport, and system libraries. (Note that the vendor libraries
also we have to consider.)
The full dependent chain for my example (ignore system libraries and
vendor lib) is
EPICS Base < Asyn < ADsupport < ADCore < ADPointGrey < FLIR Camera IOC
application
In addition, you also have to consider how you would like to handle all
template files and configuration files in the different manners.
BTW, how Debian-based facilities does handle the areadetector?
HTH,
Han
- Andrew
--
Complexity comes for free, Simplicity you have to work for.
