Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

LCLS Online Physics Applications.

from From 20000ft

This document describes a possible architecture for physics applications for the LCLS. It outlines the existing support for accelerator optics modeling in XAL, and in the exiting online SLC control system, and includes recommendations for a technology track, the process for XAL modeling, how SLC and XAL modeling can be brought together to meet the commissioning schedule, and highlights issues that will require attention. It is assumed that both the SLC modeling environment and SCP applications will be replaced by XAL based equivalents over some period.

...

Our target desktop processors will be x86 CPUs running RedHat linux, with the GTK window system (see Details). The executables may be housed on either AFS or NFS filesystems (see Filesystem). Each user (including control room heads) additionally requires their own configuration file area - the precise configuration seen by each head may be unique therefore. This is a feature of XAL and the other desktop technologies we'll use. That configuration file area will be NFS because a long-lived executable (>25hrs - the AFS token lifetime) must be able to write to it at any time.

...

XAL (that is JFC/Swing) and SWT/Jface applications may be used on any X11 equipped workstation (Windows PC, Solaris) with some performance degradation since JFC/Swing performs poorly over X11. These apps could be run "natively" on Windows (Swing is pure Java, which is platform independent, and any SWT components could be delivered for Windows too, but the added complexity of synchronizing filesystem resources between the Unix filesystem and the Windows filesystem probably makes this option undesirable - see questions) and redflags Redflags.

Overall User Interface

Use Case: A user (physicst or operator) types the name of the main application, say "lips" (or iscp or any other name we like"LCLS integrated physics environment" so we can use a word in this doc) at a Linux console - a . A GUI based application launches. This application can launch any EPICS display (DM, dm2k etc), any XAL application, the SCP (on MCC), or any EPICS extension application like archive browser, alarm handler watchdog, stripchart, cmlog browser etc. These are launched on the correct host for that application or display. The "local" messages generated by each application appear in a console window dedicated to that application - "global" messages appear in the jcmlog browser window. (This functionality has already been developed - see figure 1.

Starting Applications

)

Systematics of the User Interface

Figure 1 shows See figure 1, a screenshot of representative user applications for LCLS. This shows The main application shown is a minimally modified Eclipse Rich Client (that is, basically Eclipse out of the box) in the Resource Perspective, where the Eclipse Workspace has been configured to launch various kinds of program. A number of execution modes are represented (in-process, out-of-process, using Swing and SWT GUI frameworks, plus EPICS display technologies): #Eclipse

  1. Eclipse external launching (epics displays, archive viewer, scp etc).

...

  1. Eclipse launching external java SWT/Jface application (jcmlog)

...

  1. Eclipse launching internal java SWT/Jface (same VM) application (aida probe)

...

  1. Eclipse launching external java JFC/Swing (XAL) application (NOT SHOWN YET)

Graphical User Interface (GUI)

...

  1. Err - a platform and language independent (java & c++) error handling framework for creating and logging error messages.
    #global message: error or warning text message typically going to some log like cmlog, and viewed by a user through a browser like cmlog browser. A global message is on generated by a front-end computer or an application that thinks it's worth telling the world about. compare to local message
    #local message: a message generated by an application that is intended only for viewing by the application's user at that time. Eg "0 is not a permitted number of iterations to average bpm readings".

REFERENCES1

  1. XAL http://www.sns.gov/APGroup/appProg/xal/xal.htm

...

...

  1. XML

...

  1. entry in Wikipedia http://en.wikipedia.org/wiki/XML

...

...

  1. LCLS lattice files

...

...

  1. JAMA

...

  1. http://math.nist.gov/javanumerics/jama/

...

To do
Add gold lattice to optics flowchart diagram

Anchor
td_GW
td_GW
add to diagram