Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/~qc/admin/QC_scientist_guidelines.pdf Дата изменения: Thu Nov 5 15:44:32 2015 Дата индексирования: Sun Apr 10 01:44:27 2016 Кодировка: Поисковые слова: jupiter

Page 1 of 3 QC Scientist Guidelines Reinhard Hanuschik, Head, Quality Control Group Version 4.0 (November 2015) This document summarizes the high-level tasks of the Quality Control Scientist. It is periodically revised. Printed in red are new tasks, printed in grey are tasks which have become obsolete with respect to the previous version. Detailed procedures and reports are posted on the internal QC Operations Web page (www.eso.org/~qc/groupIndex.html). All QC Scientists are expected to be familiar with this documentation. Research: QC Scientists are allowed up to 20% of their time for research. However, this is an operational position ­ ESO science operations have higher priority than personal research. Annual performance appraisal will be based on functional work only. Instrument-specific Responsibilities For each assigned instrument, the QC Scientists have the following responsibilities: General Be familiar with all assigned instruments, their calibration plan, calibrations, and their purpose Configure and maintain the operations-critical tool calChecker (and its components CAL4CAL and tellTracker, if applicable); analyze issues as quickly as possible, in-line with the policies agreed with PSO. Customers are: o PSO For all supported instrument modes, create and certify master calibration data, for following customers: o external user community (through the Archive calSelector service) o PSO (on-line pipeline system), quality feedback o QC group (for IDP projects) Collect, analyze, and report instrument QC1 parameters. Develop new QC1 parameters as appropriate, after discussion within IOT and in particular with the Instrument Scientist . Maintain high-level QC1 parameter description and process documents. Maintain QC1 database tabl es in collaboration with DBCM. Customers of QC1 parameters are: o Archive (QC1 database) o PSO (internal/external Web pages) o external user community (external Web pages) Collect scores for all processed ABs. Configure the scoring system for each instrument as complete as possible, and maintain it to keep it up-to-date and make it significant. Customers of scores are: o PSO (HC monitor) Configure and maintain the web pages and the process for the Health Check Monitor


Create associations for science data, insert them into the Archive. Customers are: o External users of calSelector Create associations for science data, store them on the QC web server. Customers are: o QC group (IDP projects) Deliver and maintain calSelector association rules. Customers are: o External users of calSelector Configure and maintain the calibration maps for all supported flavours of OCA rules New: if applicable, process the science data for the assigned IDP project ; process the stream data as soon as all required master calibrations are available, normally on a monthly basis, and ingest them; monitor the quality of the IDPs by doing spot checks on the QC reports, checking red scores etc.; monitor ingestion issues; if existing, monitor the IDP quality check pages on the WISQ monitor; maintain the Release description; if required, interact with ASG group about issues. Customers are: o external user community (phase 3 interface) Create and maintain QC information web pages ("tutorial", data types, pipeline recipes, calibration map), following a common structure. Customers are: o ESO operations & technical teams (PSO, USD etc.) o external user community Maintain the Reference Frames web pages, as approved by Group Head If applicable, monitor the pre-imaging part of their instruments. Customers are: o PIs of pre-imaging runs Participate in Instrument Operations Team (IOT)






Page 2 of 3 o Keep track of instrument operations status, upgrades and pipeline status o Provide expertise about data, feed back QC issues Visit regularly Paranal Observatory (as directed by Group Head) o Interact with Instrument Scientist, Day and Nighttime Astronomers o Achieve and update overview of instrument operations Follow-up and interact with pipeline development, maintenance, & commissioning efforts Interact with SDP group about improving pipelines towards science -grade data products Provide input for quarterly reports (see outline on QC Ops Web pages) Fulfill general group tasks and responsibilities as directed by Group Head





QC Shiftleader Act as QC shiftleader as per weekly plan Check that the primary QC services are up and running, for all instruments. Analyze technical issues (database, data transfer, connectivity, muc performance); o if possible, fix them (use the qc_shift account) o if not, inform the appropriate groups at DMO The responsibilities cover normal working days and hours only. Tools, Process As appropriate for your instrument, and as directed by the QC Group Head: Understand how to process calibration data from all pipeline supported instrument modes Understand and operate DFOS infrastructure o Support the DFOS common process use only DFOS tools for the common workflows do not modify DFOS tools o Understand existing procedures/tools and documentation o Set up the configuration files properly o Develop new procedures/tools as directed by DFOS responsible and approved by Group Head Understand how to operate DFS infrastructure (esorex, CONDOR etc.) Understand how to operate DFS pipelines o Understand applicable DRS at general level o Understand recipes, products, algorithms Develop, operate and maintain tools for QC reports, certification and trending o use dfos tool qcDocu to provide documentation about algorithms, report design etc. General Documentation Read and familiarize with the DFO handbook Read and maintain external documentation: http://www.eso.org/qc/ o ...and all pages underneath this link related to your instruments Read and contribute to QC Operations Web pages: http://www.eso.org/~qc/groupIndex.html o ...and all pages underneath this link Support On-Site VLT Science Operations Visit Paranal Observatory at least once per year for 4 -8 days. o Frequency and length of visits is instrument status dependent and must be co-ordinated with Group Head On-site responsibilities o Participate in daytime on-site QC process (daytime calibrations) o Discuss and interact with on-site staff about QC tools, collect feedback, provide explanations and tutorials o Discuss instrument specific Calibration Plan, pipelines, and QC process with Paranal instrument responsible Current Instrument Assignments Listed on QC Operations Web pages Appendix: Policy for data usage in scientific projects/collaborations The QC scientists are in a privileged position because of their direct and total access to all ESO science data. This privileged access can only be granted for operational tasks.






If you want to conduct scientific research on archival data, no matter your own research project, you must respect ESO access policy. This data which have already been released to the PI, either through a data Portal, or through a VM data package provided on the mountain. This policy applies to ESO data which are still under access protectio

Page 3 of 3 if as part of a collaboration, or as means you can only work with package, or through the User n. It does not apply to public data.