LCLS Lattice Description

This was the home page of the lattice descriptions of the Linac Coherent Light Source (LCLS) facility. These materials are now DEPRECATED . Please now (as of April 24, 2019) refer to the new LCLS lattice home page, where you will find the lattice files for both normal conducting (NC) and the new superconducting (SC) beampaths of the combined LCLS accelerator complex.

Lattice Description Files

Main command file

LCLS_main.mad8

Matching command file

Master definitions

Linac 1 definitions

Linac 1 for Elegant

Linac 2 definitions

Linac 2 for Elegant

Linac 3 definitions

Linac 3 for Elegant

A-line definitions

Lattice Output Files

Databases

Modelled element and device data are available in SLAC's Oracle Database. See the Elements and Symbols tabs (they contain largely the same information).

Optics Plots

These are the Twiss parameter plots resulting from the latest deck, for each beampath. Click on an image for the set of plots of that beampath.

Beampaths

The following are descriptions of each electron beam traversal through the "LCLS" accelerator complex. In the context of the LCLS-II project now under construction, these represent the CU related beampaths of the future. The paths described here, are as they are now.

**Beampath Table:** Primary RF refers to the technology used for radio frequency structures of the primary acceleration of the beamline; "cu" = warm copper. Status refers to the administrative standing of the beampath. MAD filename prefix refers to the filenames of the MAD output relating to the beampath. The Beampath ID is the unique tag of the beampath understood by the MEME directory service. The maps are zoomable PDF. Middle-click to download, open with for instance Adobe Reader (zoom in with for instance View ↳Zoom ↳ Pan and Zoom). The maps show the all modelled elements of the mad deck, including devices (where the element has one), markers etc, with their suml and Z positions, arranged left to right by Z and hierarchically by modelled line. Arrows link the elements to show the path of the beam from element to element through the machine.
Primary RF	Description	Status	MAD output filename prefix	Beampath ID	Lines file file
cu	Gun to HXR dump	In Operation	LCLS	CU_HXR	LCLS_lines.dat
cu	Gun to 135MeV Spectrometer	In Operation	SPEC	CU_SPEC	SPEC_lines.dat
cu	Gun to Gun Spectrometer	In Operation	GSPEC	CU_GSPEC	GSPEC_lines.dat
cu	Gun to A-line	In Operation	LCLSA	CU_ALINE	LCLSA_lines.dat

Beampath Table: Primary RF refers to the technology used for radio frequency structures of the primary acceleration of the beamline; "cu" = warm copper. Status refers to the administrative standing of the beampath. MAD filename prefix refers to the filenames of the MAD output relating to the beampath. The Beampath ID is the unique tag of the beampath understood by the MEME directory service. The maps are zoomable PDF. Middle-click to download, open with for instance Adobe Reader (zoom in with for instance View ↳Zoom ↳ Pan and Zoom). The maps show the all modelled elements of the mad deck, including devices (where the element has one), markers etc, with their suml and Z positions, arranged left to right by Z and hierarchically by modelled line. Arrows link the elements to show the path of the beam from element to element through the machine.

Primary RF

Description

Status

MAD output filename prefix

Beampath ID

Lines file file

Map Link

Gun to HXR dump

In Operation

LCLS

CU_HXR

LCLS_lines.dat

Gun to 135MeV Spectrometer

In Operation

SPEC

CU_SPEC

SPEC_lines.dat

Gun to Gun Spectrometer

In Operation

GSPEC

CU_GSPEC

GSPEC_lines.dat

Gun to A-line

In Operation

LCLSA

CU_ALINE

LCLSA_lines.dat

The mapping from elements to EPICS PV names (or at least the device name part of PV names) is defined by the file elementdevices.dat. These lines files and maps were created using an awk script mad2dot.awk. mad2dot takes as input the print and survey files as output from Mad (see header of mad2dot), plus one or more element/devices files - the main one being elementdevices.dat. mad2dot creates the lines file (for consumption by the directory service, so on-line apps know the device-line hierarchy), and a dot file, for instance LCLS.dot, for each beampath. We then use the unix command dot, or Graphviz, to create a PDF from the dot file.

Publication Guide

For those people who need to change the lattice files, there is a README in CVS, in the same directory as the lattice files. That README describes how to do the CVS, and use a makefile to publish the output files to /afs/slac/www/grp/ad/model/output/.