ASTRI - Astrofisica con Specchi a Tecnologia Replicante Italiana

Size: px

Start display at page:

Download "ASTRI - Astrofisica con Specchi a Tecnologia Replicante Italiana"

Loren Clark
8 years ago
Views:

1 Code: Issue 1 DATE Page 1 ASTRI Software Requirements and Use Cases Prepared by: Name: Joseph Schwarz Signature: Date: May 09, 2012 Gino Tosti + ALL Reviewed by: Name: Signature: Date: Approved by: Name: Signature: Date:

2 Code: Issue 1 DATE Page 2 TABLE OF CONTENTS LIST OF ACRONYMS 3 APPLICABLE DOCUMENTS 3 REFERENCE DOCUMENTS 3 1. INTRODUCTION 3 2. SCOPE 4 3. OBSERVING OBJECTS DEFINITION Proposal Observing program Observing Block Observing Session Observation Run 4 4. REQUIREMENTS General requirements Examples Observation Preparation Tools Operation Software Error! Bookmark not defined Define here the ASTRI Operation modes ASTRI Control Language Data Acquisition and Data Rates Scheduler Data Processing and Calibrations Archiving 5 5. USE CASES Observe with ASTRI Schedule Observing Blocks Execute Observing Blocks Observing Modes 7 6. APPENDIX 7

3 Code: Issue 1 DATE Page 3 DISTRIBUTION LIST ASTRI Team LIST OF ACRONYMS APPLICABLE DOCUMENTS [AD1] Contract REFERENCE DOCUMENTS [RD1] 1 1. INTRODUCTION This document is a preliminary collection of User Requirements and Use Cases to be used to define the software requirements for the ASTRI Control System Software. Because the various parts of the system should be developed in a highly consistent way, from the very beginning of design (although they may however be installed progressively) providing a global sets of use cases can be also useful to individuate the critical elements of the system that shall be implemented first. Add reference to Applicable and Reference documents

4 Code: Issue 1 DATE Page 4 2. SCOPE The main goals of this document is to collect requirements and use cases for each of the ASTRI subsystems that will work together to perform the Science and technical/characterization observations for which the ASTRI telescope was planned. This document describe what the ASTRI Software shall be able to do and not how it will be implemented. 3. OBSERVING OBJECTS DEFINITION In this Section we introduce the main entities, used to manage the whole observing process, that is constantly referred to in the Requirements and the Use Cases. 3.1 Proposal An observer submits a proposal to perform a set of observations. In ASTRI this could be any kind of science observation request 3.2 Observing program This is how the information in the proposal are arranged to allow an evaluation of the feasibility of the requested observations. After this check the information are arranged in a way that they can be scheduled and executed by the system. In order to be scheduled the requested observations are arranged in Observing Blocks (). An observing program can be executed over long period of time. 3.3 Observing Block This is the basic units in which the observation of each science program can be divided. () Observing block are prepared by the user and include all information used by the system during the observing session. Each Observing program can consist of one or more Observing block (eg. One for each target source) 3.4 Observing Session The time continuous execution of one or more scheduling blocks in constitutes an observing session. Each observerving session consist of obsersevation runs() 3.5 Observation Run The observation run is the basic entity in which and observation session can be split during the execution of the program. An observation run executes all the operations: from telescope pointing to data acquisition. () 4. REQUIREMENTS 4.1 General requirements Requirement priorities 0 Essential feature 1 To be ready for the Test and Verification Phase

5 Code: Issue 1 DATE Page 5 2 To be ready for the Science operations Examples SR01.01 The ASTRI software shall allow to scientist/operator/engeneer a simple operation of the telescope and data acquisition system Priority: 0 SR01.02 The operator/engeneer shall be able to send direct orders to the hardware through a the ASTRI Control Language. Priority: 0 SR01.03 Etc 4.2 Observation Preparation Tools 4.3 Operation Software Define here the ASTRI Operation modes SR02.01 Manual Operation Mode SR02.02 Automatic Operation Mode SR02.03 Calibration Operation Mode SR02.04 Maintenance Opearation Mode SR02.05 Etc ASTRI Control Language Data Acquisition and Data Rates Scheduler 4.4 Data Processing and Calibrations 4.5 Archiving 5. USE CASES ASTRI is a proposed prototype for the CTA Small-size telescope array. In the contest of Cherenkov telescopes the typical observation of a target is performed alternating off-axis ( wobble-mode ) observations of at angular resolution in order to obtain an optimal subtraction of cosmic-ray and electron backgrounds. 5.1 Observe with ASTRI This is just an example Use Case ObserveWithASTRI This Use Case outlines the basic process of science observations with ASTRI Role(s)/Actor(s): Primary: Observer Secondary: the Operator, the Proposal Review Panel (PRP) Priority: Critical Performance: minutes to years Frequency: hours ()

6 Code: Issue 1 DATE Page 6 Preconditions: 1. The ASTRI System has reached at least partial operational state and accepts observation requests. Basic Course: 1. The Observer creates a detailed Observing Program (UC_ Create Observing Program). Exception Course: The observing program is not feasible and then rejected by the PRP Postcondition: The Observing Program is stored as one or more Observing Blocks in the Observing Block Repository. Its OBs are ready to be queued for observing. (UC_ScheduleOB) 2. The Program's SBs are dynamically scheduled for observing. Observations are scheduled in units of Scheduling Blocks. Alternate Course: The programme may be observed interactively. 3. The ASTRI Control System executes Scheduling Blocks (UC_ExecuteOB): if necessary the system allocates requested resources and initiates pipeline data reduction, or releases those resources after execution. Postcondition: The raw data goes into the archive. 4. The Data reconstruction Pipeline reduce the data and the event list are written written into the archive. 1. The Calibration Pipeline writes reduced Calibration Data into the archive, and makes relevant results and data quality evaluation available to the scheduling and observing processes (UC_ProcessCalibrations). 2. The Quick Look Pipeline displays calibration data and applies it on the fly to science data in order to display interim science results. 3. The Science Data Pipeline processes science data, writes reduced science data into the archive, optionally displays results, and optionally makes data quality evaluation available to the scheduling process (UC_ProcessScienceData). Postconditions: 1. The science goals are reached so that the results may be published for the improvement of human knowledge. Issues to be Determined or Resolved:... Owner: Caio Sempronio 5.2 Schedule Observing Blocks Use Case ScheduleOB Role(s)/Actor(s): Primary: Secondary:. Priority: Major Performance: seconds Frequency:

7 Code: Issue 1 DATE Page 7 Preconditions: 1. OBs shall be present in the OB Repository Basic Course: Alternate Couse: Postconditions: Notes: Owner: 5.3 Execute Observing Blocks Use Case ExecuteOB Role(s)/Actor(s): Primary: Secondary:. Priority: Major Performance: seconds Frequency: Preconditions: 1. OBs to be executed Basic Course: Alternate Couse: Postconditions: Notes: Owner: 5.4 Observing Modes 6. APPENDIX

Error Budget Tree for the ASTRI prototype: structure and mirrors

Code: ASTRI-SPEC-OAB-3100-002 Issue: 2 DATE 02/04/2012 Page: 1 Error Budget Tree for the ASTRI prototype: structure and mirrors Prepared by: Name: Rodolfo Canestrari Paolo Conconi Enrico Giro Gabriele