Deployment of CSS-BOY at APS Beam Lines · 2017-02-17 · – APS accelerator screens are a project...
17
Deployment of CSS-BOY at APS Beam Lines Pete R. Jemian Advanced Photon Source, Argonne National Laboratory 2012 EPICS Collaboration Meeting SLAC, Menlo Park, CA 2012-04-25 thanks to: CSS developers, BOY developers, John Hammonds, Tim Mooney, Peter Beaucage, David Ilavsky, Jan Ilavsky
Transcript of Deployment of CSS-BOY at APS Beam Lines · 2017-02-17 · – APS accelerator screens are a project...
Deployment of CSS-BOY
at APS Beam Lines
Pete R. Jemian
Advanced Photon Source, Argonne National Laboratory
2012 EPICS Collaboration Meeting
SLAC, Menlo Park, CA
2012-04-25
thanks to: CSS developers, BOY developers, John Hammonds, Tim Mooney, Peter Beaucage, David Ilavsky, Jan Ilavsky
Abstract
It is planned to deploy CSS-BOY at APS beam lines using standard screens from the APS as well as locally-produced screens. This talk will describe our initial test deployment and the procedure for deployment at other facility beam lines.
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
2
Outline
APS beam lines today
Describe our test deployment
Hands-on examples
Migration Punchlist
Plans for regular deployment of CSS-BOY
– provided as APS_CSS, http://css.aps.anl.gov/
Most of all, suggestions are welcome and encouraged!
Note: author is not a CSS developer, just a reporter
APS
today
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
3
APS/XSD: 17 sectors +1 coming +4 labs Partner: 2 sectors Independent: 13 sectors
Facility provides MEDM screens today from a DSERV
(network file server +)
DSERV: Distributed SERVer (computer)
– One master, rsync to sector DSERVs each day
– VLAN into each beam line’s local subnet
– Hardware in main server room
– NTP, facility DNS, some other servers
– NFS file shares:
• /APSshare (ro) for all beam lines
• VME boot and user space (rw) for APS/XSD beam lines
/APSshare provides common files and software
– EPICS base, some EPICS extensions, APS local software, others (SPEC, Python, IDL, …)
– Existing suite of MEDM screens
• synApps: ~900 .adl files (most are unique)
• Accelerator: ~4000 .adl files (not all are unique)
– Beam lines probably use ~100 of these
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
4
The APS USAXS instrument at station 15ID-D:
our guinea pig for testing software
15ID beam line (EPICS used throughout the beam line):
– Front-end controls provided by APS (as all APS beam lines)
– Upstream optics provided by CARS (manages the rest of 15ID)
– 15ID-D station managed by APS/XSD (as partner with CARS)
15ID-D station
– 2 VxWorks IOCs
– 1 Vector Linux IOC
– 1 Pilatus detector (Linux) IOC
– 1 RHEL5 combined soft IOC and OPI workstation
– 2 (or more) Windows user OPI workstations
USAXS Instrument has several working configurations
– Bonse-Hart USAXS with 1-D or 2-D collimation
– USAXS Imaging
– USAXS XPCS
– Hybrid USAXS collimating optics and 2m pinhole SAXS
Been using APS_CSS for more than one year. They like it!
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
5
Test deployment
CSS workspace
– Single project: “/CSS”
– Working directory of instrument-specific SVN
– Some facility screens in components subdirectory
– Most instrument screens were converted from MEDM predecessors (adl->opi)
– then hand-tweaked by talented and motivated undergraduates
– Remember: put .project file into SVN!
• Makes it easy to import as a CSS project! Provides a default project name!
– Separate workspace and SVN working directory on each instrument workstation
MEDM still used when no OPI is available
– Spawns MEDM process on local workstation from CSS
– Legacy support (only) for unconverted facility screens
• Need for this ends when all facility screens are available
• Works well now (lesson learned: do NOT spawn MEDM screens through X11 session!)
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
6
CSS-BOY button can launch MEDM
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
7
Note: motor control widget re-used
Note: this was started from a CSS-BOY button
Tabbed display shows different configurations
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
8
Detached display
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
9
CSS-BOY Migration Punchlist
Each beam line wants …
– … its local network to be wholly autonomous
– … to be able to fall back to MEDM during transition period
– … to use CSS-BOY the same way they used MEDM (!)
– … to share same screens at beam line workstations, allow for local modifications
Convert existing suite of MEDM screens to CSS-BOY and provide locally by DSERV
– synApps provides ~900 .adl files
• All are converted to OPI screens and tested at ~90% level (thanks to Tim Mooney)
• Needs functional testing (waiting on easy deployment)
– Accelerator provides ~4000 .adl files
• Beam lines probably use ~100 of these, especially storage ring stripchart of current
• Accelerator not ready to use CSS-BOY yet
Provide developers easy access to beam line screens
The Challenge
– Simultaneous eclipse sessions cannot share same workspace directory
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
10
Deployment plans
Workspace layout in terms of projects
– Instrument screens are a project
– Upstream optics might (or not) be separate project
– synApps screens are a project
– APS accelerator screens are a project
– /CSS project is left empty
– Scales to multiple instruments and beam lines in one CSS workspace
• Support staff can have all beam line projects in their workspace or select individually
• Partnered beam lines can share screens
– Version control can apply to each project separately
– This design fits the typical eclipse model
Project locations
– Local storage (for early or uncontrolled development)
– Shared file server (preferred)
– Subversion working directory (alternative)
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
11
Still Needed:
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
12
Display Screens
– Instrument screens
• adl->opi converter works well, need graph widgets to convert
• provide (proposed) tool to adjust paths to facility screens (?suggestions?)
– synApps screens need to be tested
• Developers will need to provide both .adl and .opi screens until we can let go of MEDM
– APS accelerator screens need to be converted and tested
Setup of user workspaces
– Documentation to be provided
– Support staff training
– Lectures and demonstrations
– In some cases, installations guided by facility support staff
Socialization (CSS-BOY needs to be easy to adopt)
– How to deal with multiple workstation workspaces (not eclipse workspace)?
– Multidisplay workstations
– Preconfigured view locations across several monitors
More user experience
Suggestions to improve CSS-BOY from our test
Auto-sizing of detached views
Provide a search path for OPI screens
– allows user to override facility screens
– Example: Facility provides /synApps/motor/motorx.opi
– User wants to temporarily override this with local /CSS/motorx.opi
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
13
Thank you for your attention!
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
15
Standard MEDM screen in BOY
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
16
EPICS 2012 @ SLAC: Jemian: Deployment of CSS-BOY at APS Beam Lines
17
