...
| Wiki Markup |
|---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="9570aa8de8558c99-26aae8e0-4a5943dc-8eb88223-d27ef52d7e3ec194dd33f769"><ac:parameter ac:name="">PRJ-MODELARCH</ac:parameter></ac:structured-macro> *PRJ-MODELARCH*: In this phase we will architect the model hierarchy - how one or more model sections comprise a beamline \[[#REF-SLCBMLS]\], and the beamline modelled in one or more energy profiles (aka "Twiss modes") \[[#REF-MBITS]\]. A *requirement* clear from SLC/PEPII experience is that > 1 model and its consequent set of twiss/R params should be storeable in the DB for each beamline (in each twiss mode); that is, not just the design model run with extant values, but a test lattice with test and extant settings too. Hence, 4 combinations of the two input types should be supported: |
- design lattice + extant settings (PV values) - aka "designdatabase"
- design lattice + design settings - aka "databasedesign"
- test lattice + extant settings (PV values)
- test lattice + test settings
| Anchor |
|---|
| PRJ-MADSERVER |
|---|
| PRJ-MADSERVER |
|---|
|
Simultaneously we will create a Mad model server, that runs those models.
| Anchor |
|---|
| PRJ-MADTWISSINDB |
|---|
| PRJ-MADTWISSINDB |
|---|
|
PRJ-MADTWISSTODB: 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
. A requirement clear from SLC/PEPII experience is that > 1 set of twiss/R params should be storeable in the DB for each beamline (in each twiss mode), not just the design model run with design and extant values, but a test lattice with test and extant settings too. That is, all 4 combinations above.
| 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.
...
