Software Summary

1
Software Summary

• Chris Rogers, MICE CM
• 28 June 05

2
Summary - Analysis/BT/Optics (Rogers)

• Some updates to Analysis
• Algorithmic improvements
• A new Optics module
• Calculate optical function
• Optimise for current selection etc
• Plans for an upgrade to the Field modelling
  packages
• Modular design
• Still skeletal on some details

3
Analysis Updates

• New file io routine
• File io takes 90 of processing time
• Now time taken goes as n_events
• Formerly n2
• Function to calculate single particle emittance
  using optical functions instead of bunch
  covariance matrix
• Code cleanup/comments
• Still behind on testing
• Plans for a new bunch sampling/Gaussian weighting
  algorithm

4
Optics Example Optimisation
current
Number of Cycles

• Current evolution over time
• Currents converge pretty quickly
• Processing time minute (on a single Imperial
  cpu)
• But fairly simple problem

5
Beta function

• Beta started as blue
• Finished as red
• Pretty simple problem

6
New Field Model Structure
FieldGroup StageV
FieldGroup AFC1
FieldGroup AFC0
FieldGroup Tracker0
FieldGroup Tracker1
FieldGroup RFCC
Solenoid CouplingCoil
Solenoid CouplingCoil
FieldGroup Linac
RfCavity RF1
RfCavity RF0
RfCavity RF2
RfCavity RF3
7
Future Plans - Longitudinal Cooling

• Aim to write proposal for longitudinal cooling in
  MICE
• Single wedge - MICE IV.wedge
• Wedges and RF - MICE V.wedge
• Wedges, RF and Tilted solenoids (ambitious) MICE
  VII.wedge!
• Prove feasibility, get order of magnitude of cost
• Plastic wedges (cheap), LiH wedges, LH2 wedges
  (ambitious)?
• Optics and simulation study

8
Simulation More on DAQ (Ellis)

• Much progress has been made on the online code
  for the tracker.
• Still plan to use G4MICE for monitoring and
  analysis of test-beam activities at KEK.

9
New Domains

• Additions to G4MICE to add functionality needed
  for analysis of test-beam data
• Calibration and Alignment information
• Decoding information (to go from electronic
  channel space to physical space on the detector)
• Visualisation (event display)
• More flexible ability to produce applications
  (executables)

10
Plans

• G4MICE activities will take a second priority to
  test-beam readout until it is finished.
• Aim to study optimum station spacing if time
  allows.

11
AFE II code

• Code currently exists to perform most needed
  functions
• Initialisation of the board (including
  programming FPGAs, TRIP chips, etc).
• Control of the SASEQ (to select Idle, Acquire or
  Trigger modes).
• Readout of the AFE II board over the LVDS link
• Code currently only reads out one board (not a
  big deal to make it read out N).
• Code currently cannot correctly load FPGA
  firmware correctly. There is some byte/word order
  problem which needs to be addressed.

12
Screen shots of GUI
13
Plans

• Work at D0 is continuing, aim to have a complete
  system test including calibration and cosmic-ray
  data taking by the end of July.
• DAQ code will be extended to read out several AFE
  boards and fix checksum problem.
• Once hardware/software system has been validated,
  hardware will be shipped to KEK, software will
  then be ready to be integrated with UniDaq system.

14
G4MICE status

• Design
• Implementation
• A lot done, a lot to do
• Cooling channel geometry and fields
• Detector geometry
• More engineering detail
• Digitization (raw data)
• More electronics detail (spill, etc.)
• Reconstruction
• Global matching and PID
• Analysis tools (emittance, etc.)
• Flexible user-defined analysis
• Large scale production tools
• Persistency (data storage, access)
• Use
• Detector optimization
• Optics design
• Data analysis (KEK beam test)
• Physics analysis