...
Phase 1: Put Mad model run results in the Oracle database.
| Anchor |
|---|
| PRJ-MADTWISSINDBMODELARCH |
|---|
| PRJ-MADTWISSINDBMODELARCH |
|---|
|
PRJ-MADTWISSTODBMODELARCH: In this phase we will architect the model hierarchy - how one or more model sections comprise a beamline, and the beamline modelled in one or more energy profiles (aka "Twiss modes"). 4 combinations of teh two input types should be supported: - design lattice + extant values
- design lattice + design settings
- test lattice + test settings
- test lattice + extant values
Simultaneously we will create a Mad model server, that runs those models.
| Anchor |
|---|
| PRJ-MADTWISSINDB |
|---|
| PRJ-MADTWISSINDB |
|---|
|
PRJ-MADTWISSTODB: : Both "design" and "extant" machine should be supported. Modelling the extant machine will be done by running the mad input through a filter, which will find the epics PV or slc db name associated with each device (via the "symbols" Oracle schema), and create an output file which can be run by Mad. The resulting Twiss and R-mat will then be loaded into Oracle.
In this phase we will architect the model hierarchy - how one or more model sections comprise a beamline, and the beamline modelled in one or more energy profiles (aka "Twiss modes").| Anchor |
|---|
| PRJ-BDESTOKMOD |
|---|
| PRJ-BDESTOKMOD |
|---|
|
PRJ-BDESTOKMOD: We will need a "bdes-to-kmod" as part of this. If after analysis that seems hard, we should consider jumping straight to phase 2, since XAL's tracking will acquire klystron readings and make the conversion directly, at the time of tracking, so in this respect it would be easier than implementing an online model system for Mad.
...
PRJ-XALMODEL: Functionally as phase 1, but for XAL. Phase 1 precedes phase 2 since we already have a Mad model. Phase 2 will additionally involve adapting XAL for the LCLS beamline requirements (acceleration, solenoid), and creating a model server for XAL. The model server runs (in XAL language it hall "probe") the input file on demand (
design lattice + extant values, design lattice + design settings, test lattice + test settings, or test lattice + extant values). The model inputs for this phase will be a hand written XAL input files. That is to say, this is not a continuous accelerator simulator.
...
