23
FEL PERFORMANCE PROGRAM IN 2016 January 2016

Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

FEL PERFORMANCE PROGRAM IN 2016

January 2016

Page 2: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

BACKGROUND

Non-user time 2/7 of total

Development e-,

x-ray,

~50%

Setup prepare configs

instrument checkout

~25%

Maintenance PAMM, urgent problems, BBA

~25%

User Beams. . . . . User Beams

Goal: “Make the best use of non-user time to improve the performance and capability of the machine.”

The FEL Performance Program started in the January 2014

Page 3: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

FUNCTIONAL ORGANIZATION

CapabilityZ. Huang

QualityH. Loos,

ReproducibilityR. Iverson/W.

Colocho

StabilityT. Maxwell/F.J Decker

PhotonM. Minitti

Performance Program Management

H. Loos, J. Welch, W. White

Scheduling and Coordination

J. Turner

• 5 Program functions are chosen to cover all aspects of the beam the users receive

• Scheduling deals with the real-world complications

• Management keeps system going and helps provide transparency

• Good cross-over between photon and electron work.

Page 4: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

HOW IT WORKS• Each Program has a clear Objective and Scope defined in a synopsis.

• User Run Schedule is made by LCLS and sets the user and non-user time.

• Overall % allocation of development time for each program is assigned by Performance Program Managers at beginning of user run.

• Program Leads decide priorities within their program, plan and organize studies, and make sure analysis is done and reported.

• Individual studies are scheduled each week using the % allocations.

Page 5: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

SCHEDULING AND COORDINATION

Run Schedule Set

Program time is allocated

Program leaders prioritize studies

Studies are scheduled

Results analyzed and discussed

Final schedule set Monday afternoon

Thursday MD meeting and FEL R&D meeting

Resolves conflictsPAMM/POMM, instrument setup, undulator swaps, laser work, maintenance work, user configs, remedial tuning needs

Once per run

Once per run

ContinuouslyMany more studies are proposed than there is time for.

To match LCLS needs as best as possible.

Includes coordination with Linac & FEL Division

Input from broad community including users, instrument scientists and operators

Page 6: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

PROGRAM PERFORMANCE• Pulse energy is somewhat higher

• New capabilities introduced

• Quicker energy changes / tune ups? Don’t have data to support claim

• Still need extensive tune-up on saved configurations

• Still have too much jitter

• Poor reproducibility and long start-up times after downs

• Photon operations seems smoother?

Page 7: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

Hard

Soft

Quality

Page 8: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

Fall 2015

Fall 2013

Reproducibility

0 0.5 1 1.50

5

10

15

20Soft X−Ray Reproducibility: 79.0 ± 33.9 (%)

Cou

nts

(#)

0 0.5 1 1.50

10

20

30Hard X−Ray Reproducibility: 70.6 ± 35.7 (%)

Cou

nts

(#)

Pulse Energy / SCORE expected value measured within 60 minutes of load

0 0.2 0.4 0.6 0.8 1 1.2 1.40

1

2

3

4Soft X−Ray Reproducibility: 66.2 ± 40.6 (%)

Cou

nts

(#)

0.4 0.5 0.6 0.7 0.8 0.9 1 1.1 1.2 1.30

1

2

3

4Hard X−Ray Reproducibility: 79.8 ± 16.8 (%)

Cou

nts

(#)

Pulse Energy / SCORE expected value measured within 60 minutes of load

Page 9: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

ACTUAL ALLOCATION

Overallsince 11/12/13

Run 12AS OF 1/5/16

Page 10: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

OLD ISSUES

• Maintenance time is too large

• Need feedback on program balance. Rebalance from 40% Capability, 20% Quality, 10% Reproducibility, 10% Stability, 20% Photon?

• Program goals are out of date

Page 11: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

NEW ISSUES• Efficiency improvement needed

• Management and priority decisions are needed for

• Transfer to operations of new capabilities

• Special setups

• LCLS-II studies.

• No Henrik

Page 12: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

LOOKING FORWARD

• I will take over Henrik’s role as program leader Beam Quality

• Try to re-establish target 25/50/25 split for Maintenance/Development/Setup

• Deal with the new issues

Page 13: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

RUN 10 PROGRAM GOALS EXAMPLE

“Restoring machine setup following stopper disaster. Implementing different new operation modes: self seeding, two-color split bunch.”Quality

Recover from L1S modulator changes. Attain rho/2 energy stability.Stability

Concentrate on reproducibility of the source: laser and cathode.Reproducibility

• Commission Delta• Commission multi-bunch• Evaluation of harmonic lasing and associated studies (slice energy spread).• Further development of SXRSS capabilities• Evaluation of taper performance in SXRSS, HXRSS, SASE, iSASE.• Reach selenium edge 12.6 keV•

Capability

Expectations for progress in calendar year 2014 include:▪ Characterization of beam sharing operating conditions in self-seeded mode (single and double lines)▪ Commissioning of the FEE variable energy spectrometer▪ Commissioning of the new standardized LCLS time tools▪ Testing and characterization of the DESY polarization analyzer

Photon

Page 14: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

NEXT WEEK

• Bring in and discuss updated goals for run12 and run 13

• Be prepared to discuss how to manage Transfer to Operation work.

Page 15: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

EFFICIENCY IMPROVEMENT• There are about 24 months of delivering beam before

we start commissioning LCLS-II.

• Accelerator operations budget will go down ~30% during that time and then go back up with LCLS-II is running.

• We will need to become more efficient, particularly in the next six months to one year time frame.

Page 16: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

EFFICIENCY IDEAS FROM OPSManagement

1. operators doing work outside of daily operation - need to add management (working on that) mainly using project driven priorities, who are the customers?

Hardware: priority is very roughly in order of list

1. motion control is really painful except undulator 2. laser cathode profile reproducibility 3. laser motion control system is unreliable: steering and feedbacks, hysteresis, home is lost, resolution is poor for needs 4. ability to recover from klystron cycles: feedback go wild, 6x6 is dumb 5. klystron reliability / trip rate 6. modulator upgrade fallout 7. weak steering software: LTU feedback and steering, jitter, dispersion correction is lost 8. LLRF is not too bad according to Stanek - failure modes are difficult to detect 9. timing system is ok: laser timing / phase timing; some new improvement is well liked: frisch and justin 10. dispersion correction is poor. routines don’t converge and don’t cover many areas of the beamline 11. Lutman setups are too hard 12. need more one button push stuff 13. flow charts for special setups would be helpful 14. changing matrices when changing energies should be automatic: no hooks for model 15. MPS just trips instead of rate recovery, some project is going but it taking years 16. phase error masked by feedback corrections

Page 17: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

EFFICIENCY IDEAS

• flat-topping

• auto-tuning

• mission readiness programs

• reproducible source: laser spot: beam shaping, single mode

• laser temporal profile? what is reproducible?

Page 18: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

TRANSFER TO OPERATIONS

• New capabilities are proven within the Capabilities program, but commissioning them and making them routinely available for users has become an increasingly large fraction of the non-user time.

• Process and responsibilities are not well defined.

• AOS needs to say when they have sufficient tools and training.

• L&FEL and new capabilities experts should provide the tools and training.

Page 19: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

New Capability Proven

Commissioning

Transfer to Operations

Delivery to Users

LFEL staff and experts, using MD time, demonstrate the new

capability

LFEL staff and experts work with AOS staff to develop tools and

provide operator training

AOS records it is ready to provide the new capability without requiring

LFEL staff and experts

AOS delivers the beam to users

Page 20: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

SPECIAL SETUPS• Some users are getting special setups that take 12 hrs of “non-user

time” where normal users get 2. For example

• 2-bunch Delta on1/11/16,

• 2-bunch 2-color on 1/20/16

• Is it fair to other users?

• Is it given the right priority for this time?

• Is the priority process transparent?

Page 21: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

LCLS-II STUDIES

1. Radiation hardness of coated and uncoated CVD diamond

2. Argon fluorescence

3. Plasma effects on gas detectors and attenuators

4. CVD diamond attenuator speckle measurement

5. Diamond fluorescence tests

Do we want to track them separately?What priority should they be given?

Examples

Page 22: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

WHAT’S GOING ON• Tim Maxwell is working on the jitter problem!• Various people are doing machine studies for new capabilities.• Yuantao and others are understanding the details of the final phase space that generate good performance• Rick is making hardware improvements to the LTU• Juhao and others are working on find a magic taper• Feng Zhou is constantly retuning the injector• Daniel Ratner is trying to improve the initial phase space with cathode shaping R&D• FJ Decker is solving the latest crises• J. Turner is solving the latest crises• J. Welch is pontificating• A. Lutman is making GUIs for hard to use software• Chao is getting his feet wet• HD Nuhn is keeping the undulators going• W. Colocho is collating information• Henrik is leaving

• Dorian Bohler is GUI-ing• Alan Fisher is playing with detectors• P. Krejcik is …• Jacek Kryzwinski is …• Tonee is…

• John Sheppard is …• Mike Sullivan is keeping up with the users• Axel Brachmann is managing up and managing down to 26 regular employees. only 26 reporting. Everything else is functional.

Page 23: Performance Program 2016 - Stanford University · • Reach selenium edge 12.6 keV • Capability Expectations for progress in calendar year 2014 include: Characterization of beam

WEBSITES

• https://portal.slac.stanford.edu/sites/lclscore_public/Pages/FEL-Performance-Programs.aspx