ASTROSAT Proposal Processing System (APPS) IUCAA G. C. Dewangan D. Bhattacharya APPS Team PSPL Tushar Agrawal Praveen Kumar 22 January 2014 ASTROSAT Proposal Processing System (APPS) A Software System for ASTROSAT ● ● ● ● ● Provide service to the community in planning, preparation and submission of proposals, review and selection To streamline proposal-driven operation of ASTROSAT APPS is a Web Application. It would automate the process of proposal preparation, submission and evaluation process . It would also provide the details of successful proposals as input to the MCAP DB which will be used for Astrosat long-term Planning (ASTRAL), scheduling, and observations . APPS Requirement ● ● ● ● ● ● ● ● Automate proposal submission and review process for the ASTROSAT Ability to handle multiple streams of proposal cycles Multi-instrument configuration Flexible instrument parameter definition Review and evaluation by one/two level ATAC, ATC & external referees Complete Instrument Configuration (Revision and piggyback science) Different types of reports, reminders and outputs Maintain User Authentication database and the proposals database APPS Requirement Manage different Proposal Cycles & Proposal Types ● Proposal Cycles • • • • • AO cycle GTO cycle ToO cycle CAL cycle PV (one cycle only) • Scientific Category • • • • • • • • • • Proposal Types (for AO, GTO, CAL, PV cycles) Soar System Star & Stellar System Compact objects in Binaries SN, SNR & Isolated NS Diffuse emission – Gal / Extragal AGN & quasars Surveys Galaxies Cosmology • Regular Proposals - Consisting of one or more targets and single observation of each target • Monitoring Proposals – Repeated observations of a single target • Anticipated ToO proposals – Target of Opportunity which is foreseen. • Scan mode proposals – For scanning observations of some portion of sky • Tracking mode proposals – For tracking of moving targets APPS Requirement Different User Classes Mandatory Users: To be appointed or set by ISRO • Administrator – overall responsibility, create proposal cycles, set various users, ATAC structures, specify instrument configurable parameters, generate reports & statistics, input for MCAP DB • Payload Science Team members – submit GTO proposals • Payload Operation Centre Team Members – submit CAL proposals • ATAC (Sub-TAC) chair & Members, ToO Chair, CAL manager – proposal review • ATC chair & Members – proposal review • Piggyback science group members – Configure instruments left by proposers General Users • Guest Observers – submit AO/GTO proposals APPS Policy Requirements • Appointment of mandatory users • Policy matters for different proposal cycles & types (start/end dates, review period, reminders, ToO requirements, etc.) • Configurable parameters for each payload and detector, default values, ranges, additional parameters for PV/CAL cycles • ATAC/ATC structure, policies for review process & selection criteria • External tools assisting proposal preparation • Overhead times for instrument configuration changes APPS - Work Flow AO Cycle Workflow Admin creates a new cycle Submission start date Proposals are submitted AO Cycle Workflow Admin creates a new cycle Proposals are submitted Submission end date Submitted proposals are reviewed by ATC, ATAC & external AO Cycle Workflow Admin creates a new cycle Proposals are submitted Submitted proposals are reviewed by ATC, ATAC & external referees ATC members review the proposal ATAC chair invites external referees ATC chair evaluates the proposal External referees review the proposal ATAC members review the proposal ATAC Chair evaluates the proposal & allots time. AO Cycle Workflow Admin creates a new cycle Proposals are submitted Submitted proposals are reviewed by ATC, Revision ATAC & external start date referees PI/PO revise the proposal AO Cycle Workflow Admin creates a new cycle Admin generates XML files for MCAP DB Proposals are submitted Submitted proposals are reviewed by ATC, ATAC & external referees PI/PO revise the proposal Revision end date Payload Science team members configure unused instruments (piggyback science) AO Cycle Workflow Admin creates a new cycle Admin generates XML files for MCAP DB Proposals are submitted Submitted proposals are reviewed by ATC, ATAC & external referees PI/PO revise the proposal Revision end date GTO & PV cycles follow same workflow Payload Science team members configure unused instruments (piggyback science) AO Cycle Workflow (Two Level Hierarchy) Admin creates a new cycle ATAC Chair assigns proposals to sub-TAC groups Proposals are submitted Submitted proposals are reviewed by ATC, ATAC & external referees ATC members review the proposal ATC chair evaluates the proposal Sub TAC chair invites external referees External referees review the proposal Sub TAC members review the proposal Sub TAC chair reviews the proposal ATAC Chair evaluates the proposal & allots time AO Cycle Workflow (Two Level Hierarchy) Admin creates a new cycle ATAC Chair assigns proposals to sub-TAC groups Proposals are submitted Submitted proposals are reviewed by ATC, ATAC & external referees ATC members review the proposal ATC chair evaluates the proposal Sub TAC chair invites external referees External referees review the proposal Sub TAC members review the proposal Sub TAC chair reviews the proposal ATAC Chair evaluates the proposal & allots time ToO Cycle Workflow Admin creates a new cycle Proposals are submitted Submitted proposals are reviewed CAL cycle follows same workflow ToO chair reviews the proposal with the help of external referees if necessary ToO Chair evaluates the proposal & allots time. If partial time allotted, ToO chair revises the proposal XML input files are generated by the administrator User Interface ● Administrator General Observer (Proposers) ● Payload Science Team members ● Payload operation scientists ● ATAC and ATC chairs and members ● Secretary to ATAC chair ● User Interface Administrator Interface Editing inst. Config parameters Flexible Parameter Interface Inst. parameters can be defined/deleted/edited ● Payloads/detectors can be excluded ● Detector overhead times can be edited ● Setting SXT configurable parameters Validation mechanism Any change made by the administrator is validated before it is implemented. A validator can approve/reject the changes made by administrator Proposal form cover page ● Title ● Abstract ● Co-Is ● Primary observer Target list RA/DEC automatically taken from NED/Simbad Instrument configuration Attachments Verify & Submit APPS Output & Test Results ● ● APPS maintains two databases – User authentication database – Proposals database APPS outputs – Proposal coversheet in pdf format – Statistics and Reports (for Submitted and Accepted proposal) – MCAP input file : An XML file containing all the details of accepted proposals in a given cycle (AO, GTO, PV) or for a single accepted proposal in ToO Proposal Coversheet in pdf format Reports & Statistics (pdf documents) Generating MCAP input file XML file – Input for MCAP DB Instrument overhead times added <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <!-==== MCAP Assumptions ==== Not applicable integer field : -99 Not applicable float field : -99.0 Not applicable string field : not_applicable Not applicable observation date field : not_applicable Field “configured_by” 0 : Not selected, default configuration. Field “configured_by” 1 : Configured by the proposer. Field “configured_by” 2 : Configured by the piggyback science team. --> <MCAP> <Cycle> <cycle_id>A02</cycle_id> <instrument_config_version>1</instrument_config_version> <obs_cyc_start_date>2013-01-25</obs_cyc_start_date> <obs_cyc_end_date>2013-05-25</obs_cyc_end_date> <obs_cyc_date_unit>YYYY-MM-DD</obs_cyc_date_unit> <instrument_overhead_time_secs> <instrument_id>uvit1</instrument_id> <instrument_overhead_time>30.0</instrument_overhead_time> </instrument_overhead_time_secs> <instrument_overhead_time_secs> <instrument_id>uvit2</instrument_id> <instrument_overhead_time>30.0</instrument_overhead_time> </instrument_overhead_time_secs> <instrument_overhead_time_secs> <instrument_id>uvit3</instrument_id> <instrument_overhead_time>30.0</instrument_overhead_time> </instrument_overhead_time_secs> <instrument_overhead_time_secs> <instrument_id>laxpc1</instrument_id> <instrument_overhead_time>0.0</instrument_overhead_time> </instrument_overhead_time_secs> <Proposal> <proposal_id>A02_009</proposal_id> <proposal_type>Regular Pointing</proposal_type> <proposal_title>A test proposal for cyclotron lines</proposal_title> <priority_grade>A</priority_grade> <quota>india</quota> <abstract>Cyclotron lines are useful indicators of neutron star surface magnetic fields. This proposal intends to observe two High Mass X-ray Binaries to better define the properties of their cyclotron lines.</abstract> <pi_id>dipankar</pi_id> <po_id>dipanjan03</po_id> <source_table_notes>These are brightest Cyclotron Line sources</source_table_notes> <total_observationtime_secs>510000.0</total_observationtime_secs> <total_observationtime_unit>secs</total_observationtime_unit> <coversheet_location>/root/Downloads/APPS_UPLOADS/A02_009_coversheet.pdf </coversheet_location> <source> <target_id>T1</target_id> <source_name>Vela X-1</source_name> <ra_2000>9 2 6.860</ra_2000> <ra_unit>hh mm ss.sss</ra_unit> <dec_2000>-40 33 16.903</dec_2000> <dec_unit>[+/-] dd mm ss.sss</dec_unit> <variable>No</variable> Units for all <source_size>0.0010</source_size> relevant parameters <source_size_unit>arcmin</source_size_unit> <obs_time>490000.0</obs_time> <obs_time_unit>secs</obs_time_unit> <stare_time>490000.0</stare_time> <stare_time_unit>secs</stare_time_unit> <v_mag>17.0</v_mag> <xray_flux>1.0E-8</xray_flux> <xray_flux_unit>erg/cm^2-s</xray_flux_unit> <primary_intrument>czt1</primary_intrument> Default UVIT configuration If not configured by anyone <detector_configuration> <detector_id>uvit1</detector_id> <configured_by>0</configured_by> <param_name>instrument_state</param_name> <param_value>standby</param_value> <param_unit>not_applicable</param_unit> </detector_configuration> CZTI-1 One exposure <exposure_details> <detector_id>czt1</detector_id> <exposure_id>czt1_E1</exposure_id> <exposure_time_sec>40000</exposure_time_sec> <exposure_time_unit>secs</exposure_time_unit> <exposure_paramter_value> <param_name>mode</param_name> <param_value>Normal Mode</param_value> <param_unit>not_applicable</param_unit> </exposure_paramter_value> <exposure_paramter_value> <param_name>veto_spectrum</param_name> <param_value>Enable</param_value> <param_unit>not_applicable</param_unit> </exposure_paramter_value> <exposure_paramter_value> <param_name>czt_uld</param_name> <param_value>255</param_value> <param_unit>not_applicable</param_unit> </exposure_paramter_value> <exposure_paramter_value> <param_name>event</param_name> <param_value>3 Words</param_value> <param_unit>not_applicable</param_unit> </exposure_paramter_value> <exposure_paramter_value> <param_name>no_pe_packet</param_name> <param_value>15</param_value> <param_unit>not_applicable</param_unit> </exposure_paramter_value> </exposure_details> APPS development so far .. ● Request from ISRO – April 2010 ● IUCAA submitted a proposal to ISRO – 16 June 2010 ● Concept design presented on 28 June 2010 ● APPS design plan presented at GS-PDR on 29 July 2010 ● Officially approved – December 2010 ● SRS document (first release) - 8 April 2011 ● Design Document (first release) - 12 August 2011 ● SRS & Design Review and approval by ISRO team – 21/22 Feb 2012 ● Software Development started – 23 Feb 2012 ● Development status - Completed (December 2012) ● Testing and bug fixing – Complete (March 2013) (Sent to ISRO, being tested there) Test APPS Access APPS from IUCAA site https://180.149.51.196:9191/apps/auth/login.jsp Create your login/password & start experimenting Send APPS issues/bugs to [email protected] Thank You
© Copyright 2024 ExpyDoc
