1 / 13

Detector User Requirements

Detector User Requirements. URD status, introduction. URD status, overview. (Readout & Fieldcage). . URD status, subsystems. High Voltage and Low Voltage System are relatively clear and well described Cooling

gusty
Télécharger la présentation

Detector User Requirements

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Detector User Requirements URD status, introduction

  2. URD status, overview (Readout &Fieldcage)  DCS Workshop

  3. URD status, subsystems • High Voltage and Low Voltage • System are relatively clear and well described • Cooling • Progress is made on the ‘plant’ part (common effort with ST/CV)but needs to be written up • Lacking information on the ‘detector specific’ part • Many things are still unclear • Studies and prototyping is ongoing DCS Workshop

  4. URD status, subsystems • FEE control • Is very detector specific • Effort going on in understanding the requirements and study of common solutions (Peter) • Who is using VME and for what • “Environment”(temperature, humidity, pressure, …) • Not very well defined • No major technical problem if monitor only DCS Workshop

  5. URD status, subsystems • “Equipment Control”Remote monitor and control of various equipment (crates and “boxes”) • Very little information • Detector specific subsystemsCalibration, alignment, liquid circulation system etc. • First priority is to identify these systems • To be handled on case by case basis DCS Workshop

  6. URD, next iteration We always said the URD is a “working” document, so: • Update your URD with any new information you have • But also new issues to think about… • Operational Requirements • Gas System • Planning • Budget DCS Workshop

  7. URD, next iteration • Operational requirements • How will the sub systems be operated • A state diagram is a very convenient way to represent this • Define the states your subsystem can be in • Define what commands can trigger transition from one to another state • Define what (external) events can cause transition from one state to another • Good basis to define and implement a Finite State Machine DCS Workshop

  8. URD, next iteration • Operational requirements (cont’d) • How will the subsystems interact • Software (via FSM) and/or Hardware (interlocks) • What operational modes will there be and what does that mean for DCS, DAQ, TRG, … • Calibration: laser On, DAQ local run, Calibration trigger • Needed as input for design of “ECS” DCS Workshop

  9. URD, next iteration • Operational requirements (cont’d) • What data is stored where and how • Configuration data (what needs to be configured?) • Data describing the state of your detector: “conditions data”, and what will be its use (offline processing, “quasi” online processing, detector debugging, …) DCS Workshop

  10. URD, next iteration • Operational requirements (cont’d) • How to continue? • Presentations of Giacinto and Peter • We will draft a ‘generic’ state diagram for HV and LV, to be commented by you. Can be used as ‘example’ for other subsystems. • Working with TPC on ‘operational mode’ table, this can be a source of inspiration for you. DCS Workshop

  11. URD, next iteration • Gas system • Control system provided by Gas Working Group • DCS will have to interface with this control system • Users will have to define what parameters they are interested in and what will be their use DCS Workshop

  12. URD, next iteration • Planning • We are very much interested to know when you need what functionality • Not only ‘final’ system but also lab and beam tests • Tools exist, but we need to know you need them to propose them and to get you started with them • Budget • We would like to know what you have included in your budget for your DCS DCS Workshop

  13. URD, next version • The next version of your URD • URD template will be updated • Existing URD’s will be amended • But you still have to fill it… • Make sure we have your latest version! DCS Workshop

More Related