work organization and plans n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Work organization and plans PowerPoint Presentation
Download Presentation
Work organization and plans

Loading in 2 Seconds...

play fullscreen
1 / 5

Work organization and plans - PowerPoint PPT Presentation


  • 108 Views
  • Uploaded on

Work organization and plans. Road map. Integration run (February 2012) Main goals : Assessment of CPU power Hardware to control LKr (~ 600 channels) Simulation of STRAW tracker ELMB system (1 module ~ 500 channels) Part of RICH HV system with a few loaded channels (500 channels)

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Work organization and plans' - carter


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
road map
Road map
  • Integration run (February 2012)
    • Main goals: Assessment of CPU power
    • Hardware to control
      • LKr (~ 600 channels)
      • Simulation of STRAW tracker ELMB system (1 module ~ 500 channels)
      • Part of RICH HV system with a few loaded channels (500 channels)
      • About 1600 channels in total – ¼ of full system
    • DCS hardware – the same as in the LKr vertical slice

VF

dcs road map 2
DCS road map - 2
  • Dry DCS test run (June 2012 )
    • Main goal: Validation of all control solutions and confirmation of CPU power. The success of this run will depend a lot on availability of hardware.
    • Hardware : all detectors participating in Technical Run
      • 8 LAV stations: HV (all power supplies should be available) + some FE crates (≥ 1 should be available) + some thresholds reading (≥ 1 FE board should be available)
      • 1 (2) STRAW tracker module: HV(should be available) + LV(should be available) + ELMBs
      • MUV2 and 3 (full system): HV (all power supplies should be available) + ELMBs
      • CEDAR (full system): HV (all power supplies should be available)+ NINO parameter setting/reading (≥ 1 FE board should be available) + ELMBs + cooling system?
      • LKr (already integrated in the Vertical Slice)
      • CHOD (HV system)
      • IRC/SAC (8 HV channels)
      • The hardware should be available at least 3 months in advance (February 2012)
      • The hardware for which the control will not be tested in the dry DCS run will not be controlled during the Technical run.

VF

dcs road map 3
DCS road map - 3
  • Dry DCS test run (June 2012 ) - continuation
    • DCS hardware:
      • Additional 3 front-end computers (KONTRON)
      • New 3 data servers
        • We are considering2 options
          • Reinforced version of PC farm computer (do we know the model?)
          • Rack mounted version of CCC blades
    • DCS Software
      • Final version of everything including FE boards control
      • ORACLE Data Base
        • Do other NA62 users plan use the ORACLE in 2012?
        • Coordination question: Will we have general NA62 policy (and responsible) regarding the ORACLE (remember the ORACLE service is not for free)
      • External development (and developers) should be available 2-3 weeks in advance

VF

work organization and near plans
Work organization and near plans
  • The first version of URDs should be ready in 2011.
    • Please specify what is valid for 2012 run and what for 2014.
  • Group by group discussion (January 2012)
    • Finalization of the URD
    • Work and responsibility sharing. In normal circumstances:
      • Central DCS team will take care about standard equipment
      • Sub-detectors should provide a solution for an integration of “custom made” equipment
    • Establishing of schedule suitable for both sides
    • Each sub-detector should identify a DCS responsible
  • The central DCS team (naturally) will deal with sub-detector controls on FIFO basis

VF