...
Phase 1: Put Mad model run results in the Oracle database.
| Wiki Markup |
|---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="87c9074d-0be8-4280-bedb-2c0fe797f7c0"><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]\]. 4 combinations of the two input types should be supported: |
| Anchor |
|---|
PRJ-MODELARCH | PRJ-MODELARCH | 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. 4 combinations of the two input types should be supported: - design lattice + extant settings (PV values) - aka "design"
- design lattice + design settings - aka "database"
- test lattice + extant settings (PV values)
- test lattice + test settings
...
REF-SLCBMLS. SLC/PEPII Beamline Definitions,
http://www-mcc.slac.stanford.edu/%7Egreg/MODEL_SKEL.HTML
[anchor: REF-MBITS
} . Steph's old email about how SLC DB MBITS define which "twiss modes" a device is modelled in,
http://www-mcc.slac.stanford.edu/%7Egreg/MODEL_PROG_GUIDE_MBITS.TXT
