The Overview of Solar-B Mission Operation & Data Analysis

The Overview of Solar-B Mission Operation & Data

Analysis

Masumi Shimojo

Solar-B MO/DA Working Group

2003/02/03 3rd Solar-B MO/DA Meeting @ ISAS

Today’s Topics• Operation of Solar-B

– Work flow

– Personal setup

– Developments of Software for Operation

• Data Policy• Distribution and Analysis System

– Data Category

– Distribution

– FITS format for Solar-B

– Software for data analysis

The talk is based on the 1st and 2nd Solar-B MO/DA Meeting

Principles of Solar-B Operations Planning

1. The Solar-B team shall coordinate observation plans among the three instruments aboard Solar-B for maximizing the scientific results from Solar-B observations.

2. In order to maximize the scientific returns from Solar-B observations, the Solar-B team, when appropriate, shall cooperate with other satellites and ground-based observatories.

3. The “observation plan” (i.e., observation tables and commands) of each instrument should be prepared independently, once the coordination is agreed

Control of Scientific Instruments

SOT, XRT, and EIS are controlled according to the observing programs (so-called ‘Observation Table’) onboard.

Controller: SOT, XRT MDP EIS EIS-ICU

MDPFPP

XRT-E

XRT-D

SOT Observation Table

XRT Observation Table

EIS-ICU EIS

Observation Table

command

command

command

Each instrument can run its observation plan independently.

Independent each other

Instrument Coordination

Science Targets Primary Coordination Items:

(1) Selection of target regions (2) Usage of data recorder Related to data rate, i.e., image sequences of each instrument

Selection of Target Regions

The operation for a scientific target will affect the operation for others because

- Narrow field of view (FOV) instruments Satellite body pointing is only a way to change FOV

- Different duration necessary for each observation The timing of spacecraft maneuver is restricted by observing sequence of each instrument

Conflicts of Scientific Targets

Intimate communications among SOT, XRT and EIS are required.

E

N

XRT

SOT

EIS

320 arcsec

160 arcsec

360 arcsec

512 arcsec

Field of View

Solar disk size

Conflicts of Scientific Targets

Example

XRT whole-sun observations may interrupt SOT and EIS observations. It will depend on frequency of the XRT observations.

Time scale in which each observation should not be interrupted.

- Single scan of SOT spectro-polarimeter: 1-3 hours for 320160 coverage

- Single scan of EIS raster image: 10 min - 1 hour

- Time span for local helioseismology: 10 hours (by Dr. Sekii)

Twice per day is in maximum for mission long period

Personnel Setup:1

SOT Chief Observer (SOT_CO)

XRT Chief Observer(XRT_CO)

EIS Chief Observer(EIS_CO)

Solar-B Chief Planner[CP]

Telescope operation planners

Japanese scientists for real-time operation(@KSC?)

CP Supporter(@Sagamihara, ISAS)

“Tohbans(Scientists)” Necessary for Daily Operations @ Japan

One of chief observers concurrently holds Solar-B chief planner after Initial phase.

5 persons/week250 persons in year

Policy: Equally contribute to operations from US, UK & J

Roles of Chief Observers [CO]

• Detailed status check of telescope

Prepare SOT observation tables Command plans for SOT operation 　　 (commands in real time & S/C OP/OG)

Negotiated conditions: DR usage Schedule of obs. table upload S/C maneuver Coordinated observations

Example:SOT

Given conditions

OP: Operation Program; A group of time-line commands consisting of OG. 4096 time-line slots are prepared for OP. Each time line is executed at a time defined by time interval between consecutive two time lines. The unit of time interval is 0.5 sec. OP is started at a single Kagoshima contact pass. OG: OrGanized command; One OG has 8 command slots. Discrete command or block command data is included in each slot. 512 OG can be stored in S/C DHU. Time interval between two slots in an OG is 62.5 msec.

Example of OP:

CE #OG Interval

00 0 121 NOP 01 3 32 KSC LOS 02 22 85 ?SC AOS

777 511 OP STOPMax 4095

Name of OG

OP/OG

Example of OG: DC+BC+…+ BC00: 33 01 0201:02: 34 05 0303:04: 22 00 01 05:06:07: 33 01 00

Roles of Chief Planner [CP]

•Supporter is the supporting staff of Chief Planner since CP is one of COs after Initial phase.

Prepare Make OP and OG from the orbital elements and the requests from CO Command plans for maneuver of the satelliteCommand plan for real-time operation @ KSC


Given conditions

Roles of Chief Planner [CP]

•Supporter is the supporting staff of Chief Planner since CP is one of COs after the early phase.

Prepare Make OP and OG from the orbital elements and the requests from CO Command plans for maneuver of the satelliteCommand plan for real-time operation @ KSC


Given conditions

Personnel Setup : 2

Scientific Schedule Coordinators [SSC]

Solar-B Database Coordinator at ISAS [SDC]

Ground-Base Contacts Coordinator [GCC]

Those who Support Daily Operations

3 senior scientists in US, UK & Japan respectively per instrument. (TBD) Windows for proposal submission.Observation scheduling for monthly meeting“Tohbans” scheduling

Schedule downlink contacts Manage the arrival of data from KSC & other ground-base stations Make S/C attitude database from AOCS data

Archiving at ISASMaintenance of Solar-B database at ISAS

Initial phase of operation

SOT, XRT, EIS Engineering Advisor

Staying at ISAS-SAGAMIHARAPower-up and functional checking of the instrument Assist chief observers when the accidents occurs

Meetings

Meetings will be good opportunities for planning good coordinated observations

Every Monday morning (JST)

Every morning (JST)

Once per month

Monthly Operation Meeting

Weekly Operation Meeting

Daily Operation Meeting

Proposal Team plans

deadline

Meetings

Meetings will be good opportunities for planning good coordinated observations


Weekly Operation Meeting

Daily Operation Meeting

Proposal Team plans

deadline

Selection level of target regions

Scientific goalsduration, target type, instruments involved

Baseline target selected

Target for tomorrow freezed

Mission Operation

SOT- Real-time commands- Commands used in OP- Observation Table

XRT- Real-time commands- Commands used in OP- Observation Table

deadlineTime

(15:00JST)

Merger(ISAC-PLN)

OP/OG

CMD

TBL

S/C Chief Planner

ISAS

KSC

satellite operation

system

EIS- Real-time commands- Commands used in OP- Observation Table

Work Area of Science Operation Team

at ISAS

OP/OGfor S/C

CMDfor S/C

MorningEvening

Daily Operation Meeting Target for tomorrow freezed

Operation Planning

Real-time operation (1)

Real-time operation (2)

Morning

Evening

Baseline: Target is freezed in previous day

AM

PM

Target changeMinor change in operation plans

Possible

Scientists resident at ISAS from US and UK

• At least one scientists staying at ISAS from each instrument team– Chief Observer of each instrument

– Joint data analysis and scientific discussion among US, UK and Japan

• In initial phase of the solar-B operation, some scientists and engineers (→Engineer Advisor) of each instrument team will need to stay at ISAS.

The list of tools for operationSoftware User Responsibility Input OutputPrediction of satellite environments CP ISAS Orbital

elementsSoE

Chart

Prediction of ground-base contacts GCC ISAS Orbital element

SoE

List (text)

Compile SoE/Macro for Pointing CP AOCS maker

ISAS

Obs.plan SoE

Macro

Compile SoE/Macro for S/C operation CP ISAS Obs. Plan SoE, Macro

Compile SoE/Macro for instruments CO PI Obs.plan SoE, Macro

Compile Observation Table CO PI Obs.Plan Obs. Table

Predict the data output rate CO PI SoE, Macro List (text)

Make graphical chart of operation CP ISAS SoE, Macro Chart

S/C health check system KSC MELCO Raw-teleme.

Reformatter for Health Check data ISAS Raw-teleme. Health check

health check system for instruments KSC,CO

PI Health check

Reformatter and I/O routines for level-0 PI Raw-teleme Level-0

Reformatter for level-Q PI Health check

Level-0Level-Q

The tools are need before EIC/MIC test

If the tools are made before EIC/MIC test, the tools are very useful for the test

Solar-B Operation Database• MO/DA working group think that the database for supporting of

operation is needed for solar-B operation.• Solar-B Operation Database includes…

– Observing target (coordinate)– Observing table that is uploaded to Solar-B– Information of target. (Ex. sunspot, granule)

• The database allow to automatic update from the planning tool.• The database have the interface for Level-0 reformatter and the

reformatter gets information from the database for putting some keywords to Level-0 data file.

• Chief Observers refer to old observing plans for new observing plan using the database

• The detail of the database will be discussed at next MO/DA meeting.

Update Software for S/C

Schedule of Tools Development for Solar-B Operation (DRAFT)

2002 2003 2004 2005EIC/MIC System Performance Test Flight Op.

2002/72nd MO/DA Meeting

2002/End or 2002/mar-AplInst. - ISAC-PLN ICD

2003/EndQuick Look Software

2004/Aug. Software for Op.Beta Ver. Release

2004/Apr Software for Op.Release

Development ISAC-PLN for Solar-B

Development QL Software for Inst.

Update ISAC-PLN for Solar-B

Update Quick Look Software for Inst.

Check QL Soft in EIC/MIC

Check Soft for Op. in System Performance Test

MTM/TTM

2003/2 3rd MO/DA Meeting

Development Software for S/C Operation

Development Software for Inst. Operation Update Software for Inst.

Today’s Topics• Operation System of Solar-B

– Personal setup

– Work flow



– Data Category

– Distribution



The Principles of Data policy:1

• The baseline for the data policy is that Solar-B data should be open to the public as early as possible. Considering data archiving and data use priority is give to the Solar-B team and their collaborators for 6 months after collection (TBD). After the period, the data is open to the public.

Data of Proposal Obs.(TBD) All data

All data

Observation6 month

Solar-B Team

Proposer(Collaborator)

All data

Non-teamMember

The Principles of Data policy:2• Solar-B will be operated with the “initial 3-month

observation plan” during initial 3(TBD) months. Priority of observations during the initial phase should be well defined not only in the Solar-B team but also in the wide solar community

• After the initial 3(TBD) months, observations in the initial 3-month plan will evolve to a “baseline” observation plan. Proposed observations will be inserted in the “baseline” observation plan

Team Plan

Proposal Plan

Solar-B Team

Proposer (Collaborator)

Initial Observation Plan

3 monthLaunch

The Principles of Data policy:3• Contact persons for observation proposal

submissions should be well defined. Observation proposals from the solar community and the Solar-B team are submitted to the scientific scheduling coordinators.

• Gentlemen’s agreement in data priority is necessary for Graduate students and PhD thesis themes.

Proposals ofObservation

Observing Plansof Solar-B Team


ScientistsSolar-B Team

<Every 15th(TBD) Meeting @ ISAS or Tel-Conference>Participants : Project Manager, PIs, Scientific Coordinator, Database Coordinator, Chief Observers

Aims : Status Review of Satellite,Instruments and DatabaseAdoption of proposals.

Dicusson of th observatin plans and saffig for folloig 3 monthsDecision of the Monthly Observation Plan

Scientific Schedule Coordinator

The main jobs of Science Schedule Coordinators (SSC)

• Contact persons for observation proposal submissions. (All proposals are sent to SSC.)

• Using received proposals, they prepare a draft monthly schedule of observations presented in the monthly operation meeting.

• They will be authorized to reject proposal observations in following case.– The proposals are inadequacy submitted.– The same observation plan are already proposed.– The essential part of proposed plan overlap with a

PhD thesis in progress.

Today’s Topics• Operation System of Solar-B

– Personal setup

– Work flow



– Data Category

– Distribution



Baseline of Data Distribution and Data Analysis

• All downlink data from Solar-B are transferred to ISAS. • The master observation database of Solar-B are made at

ISAS, and we make mirror sites in US and UK. • The format of Solar-B observation data is FITS format.• Solar-B team basically provides non-calibrated image

data (level-0 data) and the data for calibration (calibration data) to scientists.

• Solar-B team provides data I/O tools, calibration tools and some inversion software.

• Solar-B data analysis system is based on IDL + SSW

Solar-B Data category :1 • Raw-telemetry

• The data are CCSDS packets

• Health check data• IDL-readable data (Solar-B original format) • The data is the temporary data for checking the instruments. (We already used the format at PM test.)

• Level-0 data• Non-calibrated, non-decompress data.• The format of Level-0 is FITS format with binary table extensions.• The data are distributed from Solar-B team to scientists.

• Calibration data• The data is the data for calibration (dark images, pointing data,

etc…)• The data are made from Level-0, pre-launch test, etc…• The data are distributed from Solar-B team to scientists

Solar-B Data category :2• Level-1 data

• Calibrated data (Brightness, wavelength, pointing, etc…)• The data made from Level-0 and calibration data.• Solar-B team does not distribute the data. • Solar-B team distributes the tools for creating the data.

• Level-2 data • Level-2 data are made from Level-1 and the other data• The data consist of files such vector magnetogram,

dopplergram,flare list,etc… • Solar-B ream does not distribute the data except vector

magnetograms that are made from SOT/SP data.

• Level-Q data• The data are used for the quick look.• The data made from health check data after each KSC passes.• The data are JPEG file, MEPG file, txt file, etc…• Examples of the data are,snapshot images or movies of XRT,

SOT, EIS, satellite status, etc…• The data are opened at the Homepage of Solar-B.

Solar-B Level-0 FITS formats

• Type-A [for SOT/XRT] (similar to TRACE data)

– Unit of file: about 1 hour

– Image data are putted in Primary HDU of FITS structure.

– The keywords of each image are putted in binary table.

• Type-B [for EIS] (similar to SOHO/CDS data)

– Unit of file: 1 raster

– Image data are putted in binary table

– The keywords of each image (wavelength) are putted in the binary table header.

B: SOHO/CDS like format

Primary Header

Binary Table Header------------------------------------------

Header : column 1 ------------------------------------------

Header : column 2-------------------------------------------

Header : column 3-----------------------------------------

:

Binary Table------------------------------------------Column 1 : Data [3 dimensions] -----------------------------------------Column 2 : Data [3 dimensions]

-------------------------------------------Column 3 : Data [3 dimensions]

-----------------------------------------:

JPEG Compression

A: TRACE like format

Primary Header

Image Data (1hour)------------------1 dimensions

-------------------8 bit integer

---------------------JPEG Compression

Binary Table Header

Binary Table------------------------------------------

Column 1 : Obs. Time-----------------------------------------

Column 2 : size of image-------------------------------------------

Column 3 : Wavelength-----------------------------------------

:

Pri

mar

y H

DU

Level-0 Reformat@ISAS• All downlink data from Solar-B are transferred to

ISAS.• These data are reformatted to Level-0 in ISAS.

– ISAS computer center (DARTS) supplies the hardware (computer and storage system) for Solar-B reformat process and data distribution.

– Solar-B team provide the software (reformatter, database

management system, web interface, etc.) to DARTS.• Level-0 data are transferred to US and UK from

ISAS using the Internet. And, we make the mirror of Solar-B observation database at US. and UK.

Solar-B Archive (ISAS) to US, UK Sites

Level-0Refromat@ISAS

Solar-B Databasein J apan

Solar-B Databasesin US

Solar-B Databasesin UK

FPP/ SP Level- 2 Refromat @LMSAL

TransferLevel-0 & Cal. Datausing the internet

Transfer Level-2 data(FPP/ SP)

using the internet

Solar-B Data Distribution for Scientists

• ISAS database and mirror sites have the data providing system for end-users(scientists).

• Scientists can get Solar-B data using Web system.

• The providing system has a data search system. Scientists can find the data using time, coordinate, wavelength etc. on the web (like TRACE data site).

Data analysis tools (suggestion)

• Data I/O tools (read/write Solar-B FITS files)

– The maker of the Level-0 reformatter makes Solar-B data I/O tools.

• Calibration tools (count, coordinate, wavelength …)

– Basically, PI team has the responsibility for the tools.

– The calibration tools of coordinates are developed by PI team, ISAS and NTspace.

(NTspace is the maker of Attitude Orbital Control System of Solar-B.)

• Analysis tools (Inversion code, line fitting, etc.) – Basically, PI team has the responsibility for the tools.

Documents

The Overview of Solar-B Mission Operation & Data Analysis