1 / 11

EIS Operation Planning

EIS Operation Planning. H. Hara (NAOJ) 2007 Dec 10. EIS Science Operation. Team core science Initial science targets Proposal from users. Preparation for EIS Science Operation. Merging EIS SO in S/C operation. - Obs. table - S/C CMDs. EIS Planning EGSE (EISCO). Observation

tommy
Download Presentation

EIS Operation Planning

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. EIS Operation Planning H. Hara (NAOJ) 2007 Dec 10

  2. EIS Science Operation • Team core science • Initial science targets • Proposal from users Preparation for EIS Science Operation Merging EIS SO in S/C operation - Obs. table - S/C CMDs EIS Planning EGSE (EISCO) Observation Planning Science ISACS-PLN Feedback Plan approved for EIS operation Feedback Final S/C plan Line selection Exp. duration Compression FOV size etc. Data rate Compression Instrument CAL Check of Obs. Table using PM Outcome Uplink station Analysis Data check Data for analysis Level0 data Level2 data Spacecraft Data Reformat EGSE eis_prep for level0- to-level1 conversion is ready in SSW. Users Observation in orbit Telemetry Downlink stations (USC, SVAL) JAXA data storage (DARTS) Data centers

  3. Observation Proposals • See details in http://solar-b.nao.ac.jp/operation_e/proposal_e.shtml • To broaden community involvement in the Hinode mission the science team is offering the opportunity to participate in the definition and development of the observing program. This can take the form of either collaborative investigations with other ground or space based observatories or a request for a set of observational sequences to meet a specific scientific objective formulated by the requestor. To facilitate this program the Hinode team has created a group of seven Scientific Schedule Coordinators (SSCs)to both review requests and assist requestors in preparing their plans. It is the policy of the Hinode Science Working Group that all observing requests that are consistent with the objectives of Hinode will be accepted. However it is strongly recommended that individuals discuss their proposed observations with one of the SSCs before preparing and formally submitting their request to ensure that their proposed observations are not already part of the core team's program. Please note that having your observation program selected and implemented does NOT entitle you to exclusive use of the data. The Hinode open data policy applies to all data. Where the observation program involves more than one instrument, the requestor should contact an SSC associated with his primary instrument. • 55 Hinode Operation Plans (HOP) have been proposed.

  4. Planning Constraints • Nominal allocation of telemetry for EIS is 50 kbps. A study with higher data rate cannot run for a long time. • The 24 hour planning period begins around 11 UT • Hinode daily planning meetings occur at 01:30 UT • 2-day weekend plans begin at around 11 UT Saturday • Hinode is re-pointed every ≈ 6 hours for the XRT synoptics • an EIS study should be < 6 hours in duration • Pointing information is needed for the daily meeting one day before the observations • small pointing adjustments are possible at the daily meeting on the observation day

  5. Science Schedule Coordinators • Chief Coordinators • John M. Davis (john.m.davis (at) nasa.gov) • Tetsuya Watanabe (watanabe (at) uvlab.mtk.nao.ac.jp) • Scientific Schedule Coordinators - Instrument Specific • Solar Optical Telescope (SOT) • Tom Berger (berger (at) lmsal.com) • Takashi Sekii (sekii (at) solar.mtk.nao.ac.jp) • X-Ray Telescope (XRT) • Leon Golub (Golub (at) head.cfa.harvard.edu) • Kiyoto Shibasaki (shibasaki (at) nro.nao.ac.jp) • EUV Imaging Spectrometer (EIS) • Len Culhane (jlc (at) mssl.ucl.ac.uk) • Tetsuya Watanabe (watanabe (at) uvlab.mtk.nao.ac.jp) • John Mariska (mariska (at) nrl.navy.mil)

  6. For A New EIS Observation • See details inhttp://solar.bnsc.rl.ac.uk/~young/solarb_eis/eis_study_guide.html • A sequence of observation is called ‘Study’ in the EIS plan. • A ‘Study’ consists of ‘Rasters’. • A ‘Raster’ contains a ‘Line List’. • Line Lists, Rasters, and Studies are created by users using software, EIS Planning Tool, in SSW (solar software). • EIS Planning Tool http://msslxr.mssl.ucl.ac.uk:8080/SolarB/PlanningTool_v3.0.jsp

  7. Flow of EIS Observations • Prepare a Study using SSW by proposers. • A Study file in the text format is sent to MSSL. e-mail to Khalid Al-Janabi: kfj@mssl.ucl.ac.uk • The Study is verified by the EIS proto-models at MSSL. • The Study is registered in the EIS official database in SSW. • The Study is set in a daily plan by EIS chief observers at ISAS. • EIS in orbit observes the sun according to the Study description.

  8. Preparation of EIS Observations • Create Line Lists and Rasters • Can select and modify Line Lists and Rasters that have been registered in the official database. • IDL> eis_mk_raster • Create Studies • Can select Rasters that have been registered in the official database. • IDL> eis_mk_study • Create Daily Plan at ISAS by EIS CO • IDL> eis_mk_plan

  9. IDL> eis_mk_raster

  10. IDL> eis_mk_study

  11. Timeline

More Related