Observation Software based on BOSS zna o P

Observation Software based on BOSS zna o P r e t p orksho Dr Esz Ww S t n e 08 Instrum ing 6 Oct 20 Garch G al r e en p 2008 Ins rk. Sho Sw Wo O Details/De iew v r ve mo 1 a vation Obser SW zn ter Po z s E y b

Content GENERAL OVERVIEW • The observation software (OS) • Common Framework (BOSS) – Users and requirements – Software architecture – Three examples of BOSS Applications FLAMES, AMBER and VISTA DEMO PART with details Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 2

Observation Software Instrument OS is responsible for the toplevel coordination of : 0. . N Intrument subsystems 0. . N Detector subsystems 0. . N Special subsystems 0. . N OS subsystems 0. . 1 Telescope Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 3

Generic OS Framework (BOSS) BOSS - A general purpose observation software making all OS and SOS at ESO look alike Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 4

Requirements Users § astronomer, operator, instrument software developer § archive system, SOS Main Generic objectives § § § Executing Exposure Optimised exposure sequence Monitoring and error handling Specification of the system Allow specification of instrument specific properties Instrument Specific objectives § Additional actions § Additional image handling Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 5

Exposure control basics Operation life cycle SETUP PHASE START PHASE RUNNING PHASE END PHASE Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 6

Exp-1 Generic Optimised Exposure Sequence SETUP PHASE START PHASE RUNNING PHASE Allow setup and start of a new exposure at given stages of the running phase and during the end phase Exp-2 SETUP PHASE END PHASE Overlapping exposures using the same detectors Increased Complexity of Synchronisation START PHASE RUNNING PHASE Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 7

Specification of subsystems • Configure system with standard subsystems BOSS Application • Overload system with special subsystems Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 8

Instrument specific properties The general algorithm is saved in one place but the concrete steps may be changed by the subclasses. Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 9

APPLICATIONS VLT, VLTI VISTA La Silla Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 10

FLAMES SOS Archive Kueyen GIRAFFE UVES during integration at Paranal. on the Nasmyth platform B Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna Telescope Oz. Poz during commissioning phase at Paranal (March 2002) 11

VLTI- instrument - AMBER BOSS- Support of VLTI instruments Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 12

VISTA instrument BOSS- Support of multiple image handling - Performance test OS INS DET TEL VISTA requirement: Rate: 256 MB/10 sec Upto 1. 2 TB data/night Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 13

Size of BOSS based OS-es BOSS Non BOSS-based OS BOSS based OS applications Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 14

DETAILS and DEMO XXXX OS FIERA IRACE TCCD ICS 1 TEL Is it true I don’t have to write any code? • No code necessary (at least at the beginning) • But you still have to configure the system Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 15

• Configuration of subsystems Specification of subsystems OCS. INS 1. NAME OCS. INS 1. DICT 1 OCS. INS 1. ENVNAME OCS. INS 1. PROCNAME OCS. INS 1. KEYWFILT OCS. INS 1. TIMEOUT "ICS"; "XXXX_ICS"; "RTAPENV"; "xxi. Control"; "INS. *. *. *"; 60000 OCS. DET 1. NAME "IRDCS"; OCS. DET 1. DICT "IRACE"; OCS. DET 1. ENVNAME "RTAPENV"; OCS. DET 1. PROCNAME "iracq. Server"; OCS. DET 1. KEYWFILT "DET 1. *. *. *"; OCS. DET 1. TIMEOUT 1000 ; OCS. DET 1. DBROOT "<alias>iracq"; OCS. DET 1. TYPE "IRACE“ • Database branch for each subsystem POINT boss. SERVER : Appl_data: XXXX: OS BEGIN ALIAS "xxo" ATTRIBUTE boss. INTERFACE_LIST subsystems BEGIN ATTRIBUTE boss. INTERFACE_TCCD tccd ATTRIBUTE boss. INTERFACE_IRACE irdcs ATTRIBUTE boss. INTERFACE_FIERA fiera ATTRIBUTE boss. INTERFACE_ICS ics ATTRIBUTE boss. INTERFACE_TCS tcs END Default values associated with the name of the subsystem: OCS. <CAT>. DBIFROOT OCS. <CAT>. DBSTATE OCS. DETi. DBSTATUS Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 16

Configuration of MODES It is compulsory to specify the INS. MODE for each exposure. What is the mode? 1. OS mode is associated with ICS mode INS. MODE OS 1. 2. , INS. PATH ICS Associated with setup keywords that are forwarded to the subsystems Associated with subsystems from which the OS collects header information Specification of mode in the configuration: OCS. MODE 1. NAME "IR_IMAGING"; OCS. MODE 1. SETUP "-function INS. FILT 1. NAME FREE INS. LAMP 1. ST F "; OCS. MODE 1. SUBSYST "IRDCS UT 0 ICS"; OCS. MODE 1. PATH "INFRARED"; Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 17

Ready to start the default OS For manual startup use the name of the instrument, associated with the configuration. % boss. Control XXXX & % boss. Archiver XXXX & Name of the processes associated with the INS. CON. PREFIX: xxo. Control boss. Archiver_xxo Check the global state of the OS It is the minimum state of its subsystems. Ignore subsystem if not available. Telescope during Day. Time are typically ignored. AVAILABILITY of subsystems configurable : OCS. <CAT>. ACCESS IGNORE # or NORMAL can be set: ACCESS –subsystem <> -mode IGNORE Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 18

Exposure control from command line life cycle SETUP PHASE START PHASE RUNNING PHASE Operation % SETUP -expo. Id 0 –function “INS. MODE OPT_IMAGING OCS. DET. IMGNAME myfilename” Returns: <expo. Id> %START “” % WAIT “” Returns: <exposure status> END PHASE Default command parameters: last expo. Id, detector if only one. %START -expo. Id <expo. Id > -det. Id FIERA %WAIT-expo. Id <expo. Id > -det. Id FIERA Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 19

Check the result- image • • The OS has changed the imagefilename according to standard. – Filename_day. Of. Year_four. Digit. Serial. Number. fits OCS. DET. NAMING “Standard-Naming” OCS. DET. NAMING “Request-Naming” OCS. DET. NAMING “Sequence-Naming” – – The filename not allowed to exceed 32 character Many partial header files are created during the observation. In normal operation mode all deleted. History of exposures Check the exposure table in the database Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 20

When the INS. MODE can be omitted Repeate exposure (after successful exposure) % SETUP -expo. Id 0” %START “” % WAIT “” One mode case % SETUP -expo. Id 0 –function OCS. DET. IMGNAME myfile” %START “” % WAIT “” Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 21

Multiple image handling • How to tell the OS if there are more then one image is created during the exposure ? Configure or setup: OCS. DETi. ARCMODE “MERGEALL” Default is: OCS. DETi. ARCMODE “NORMAL” • Is sorting extention slows done the Merging? No See example : IRACE in mosaic mode Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 22

Add keywords to FITS header Add new keywords by using the command ADDFITS after exposure has been setup and while the exposure is running. ADDFITS "-extnum 1 -info OCS. DET. WCS "world_coord_1" TEL. TARG. ALPHA 111111. 123456 OBSERVER myself" • Whenever possible refer to extention by its name (-extname ) • Optionally overload OS, (See User manual’s frequently Asked questions). Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 23

Exp-1 Generic Optimised Exposure Sequence Setup the first exposure on FIERA. . % SETUP -expo. Id 0 –function “INS. MODE OPT_IMAGING OCS. DET. IMGNAME myfilename” SETUP PHASE And start it. . %START “” START PHASE RUNNING PHASE Exp-2 SETUP PHASE END PHASE START PHASE Wait till integration finished. . % WAIT “-expo. Id 1 -det. Id FIERA –cond Can. Setup. Next. Obs” Setup the second exposure on FIERA. . % SETUP -expo. Id 0 ” Wait till headers collected. . % WAIT “-expo. Id 1 -det. Id FIERA –cond Can. Start. Next. Obs” %START “” … RUNNING PHASE Wait till all Merging queue finished. WAIT “-all” Ins. Sw Work. Shop 2008 - (see DEMO)SW by Eszter Pozna Observation 24

BYPASSING the OS • Forward command Typically used to control Looping TCCD: FORWARD –subsystem TCCD –command STARTLP FORWARD –subsystem TCCD –command STOPWAIT • Exposures carried out diretctly via Detectors are ignored by the OS Events from Detectors controlled separately from the OS are ignored. (No , erging take place) Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 25

END/ABORT exposures Interrupt exposures. . • • Aborted exposures are lost, after ABORT a error is returned to WAIT commands. End shortens the exposure time but save the exposure. Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 26

SOS example XSOS XXXX OS YYYY OS NGC IR NGCOPT ICS 2 Ins. Sw Work. Shop 2008 FIERA IRACE TCCD TEL ICS 1 Observation SW by Eszter Pozna 27

SOS • • Hierarchical subsystem names Hierachical setup keywords FITS hdr: Configure ICS hdrkw category : OCS. INS 1. HDRCAT “INS 2”; Otherwise acts the same way… Setup: OCS 1. DET 1. *. *, OCS 2. DET 1. *. *, OCS 1. DET 3. *. * Command –subsystem XXXX. TCCD XSOS DET 3. *. *. * YYYY OS DET 1. *. *. * NGC IR NGCOPT ICS 2 Ins. Sw Work. Shop 2008 XXXX OS DET 1. *. *. * TEL DET 3. *. *. * FIERA IRACE TCCD Observation SW by Eszter Pozna ICS 1 28

OVERLOADS Instrument specific code Many reason for overloads, – – – – • Additional commands Additional configuration keywords Additional header keywords Additional database events Additional keywords Additional special subsystem VLTI system (as ISS is not part of the VLTROOT, the VLTI interface available in a separate module - bossvlti) Sending additional commands 3 ways – – send wait for first reply Send wait for last reply (hangs!) Forward command Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 29

Help – – User manual, VLT-MAN-ESO-17240 -2265 see also ‘Frequently asked questions’ See examples in the Template instrument OS Your contact person I’m happy to help you. Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 30

Guide lines/Recommendation - All command should go through OS Communication between subsystems are not allowed Verify what are instrument specific functionalities Collect as much information as possible before the implementation Verify if requirements might be of general interest, to be considered to place it in the common software (BOSS). Check if someone has already dealt with similar problem. Avoid reimplementation of existing functionalities in BOSS. Add debug logs and error logs to your overloads. Report errors via SPR (check if error regards BOSS) Record the output in verbose mode Do not hang the OS Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 31

THANKS for YOUR Attention • Enjoy the LAB exercise • Have a Good OS development Ins. Sw Work. Shop 2008 Observation SW by Eszter Pozna 32