...
| Wiki Markup |
|---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e38f92478990a343-f5c5b6f6-48c4458c-b0cda3db-d91f687786713c1ce94b8768"><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 "database"
- design lattice + design settings - aka "design"
- test lattice + extant settings (PV values)
- test lattice + test settings
| Anchor |
|---|
| PRJ-MADSERVERRUNMODEL |
|---|
| PRJ-MADSERVERRUNMODEL |
|---|
|
Simultaneously we will create a Mad model server, that runs those models.
...
