FCCee availability model review:

• objective of review
  • avoiding bugs before anything else
• logistics
  • merge request
    • master points to empty branch
    • we comment there and hannah and jack keep working there
• demo
  • code tour
    • most in fcc_core
    • place to start should be manysims.py
      • copies local folder inputs to afs
      • creates sensitivity analyssi object
      • creates simulation object
      • select system to anlayse
      • iterates over for loops
        • creates output folders
        • has parameters class
          • also saved
        • defines system
          • includes targets (or inputs for them to meet the targets)
        • update changes system (by fetching input parameters from input files)
          • can be single system or multiple
      • sends all off to htcondor in 100 seed batches
      • if 98 of 100 seeds are done --> postprocessing is done
        • unfinished ones are sent again
    • template files
      • target
        • mttr as in LHC + drive time
        • mtbf calculated to make the target as defined by complexity study
      • system test
        • naming coding to identify which see which system & failure modes to replace in targets file
      • similar strategy for infinite physics & no polarization & which repair strategy
    • top level init.py has global constants
    • fcc_core
      • inputs
        • simulation and sensitivity - don't get changed much
        • system
          • big
          • sub-fucntions
            • add sub-systems
            • not generic but depends on system
            • update_failuremodes: bypasses excel
        • set op cycle, repair (all manipulations in spreadsheet)
      • simulation
        • handles simulations on htcondor
      • general --> utilities
      • results
        • processes results
        • doesn't always work for all system configurations
        • meant to be generic - do specific plots on top of that
        • testing - not finished and can be ignored
      • system modeling (parametrizing models)
        • defines drivetimes, cooldown times, locations of systems, mapping to AFT names,
        • returns times between failures
        • splits repairs
        • fits functions
          • mainly do exponential these days
        • class FCC_system
          • takes fault data - parametrizes system model failure & repair
    • system processing
      • specifics for modeling of each system
        • based on input from each system expert
        • mainly used AFT data
          • data from petra 3 is used, power converters, slac sent data, kek electron positron source
          • not processed in the code
            • there might be for power converters, code for petra III coming
        • all following system modeling functions template
  • foreseen usage scenarios
    • get graphs for all systems
    • discuss with experts
    • updating will be done in system_processing scripts
    • most foreseen changes seem manageable
• timeline
  • final results by end of year
  • have review done before (by 5th Dec)

@jheron @hdostman @mblaszki @dwesterm