Version 0.96596

The Outline of Solar-B MO/DADRAFTThe Outline of Solar-B
Mission Operation & Data Analysis

Version: 0.965

A proposal fromThe Solar-B MO/DA Working Group
2002-07-1408

2002/07/1408

1-1

Version 0.96596

The Outline of Solar-B MO/DA

Change Records
Issue

Date

Authors

Comments

Version 0.1

2001-11-29

M. Shimojo

Written by Japanese

Version 0.7

2002-01-18

Written by English

Version 0.8

2002-02-11

M. Shimojo
T. Shimizu
M. Shimojo

Version 0.9

2002-02-26

Version 0.95

2002-07-03

Version 0.96

2002-07-08

Version0.965

2002--0714

M. Shimojo
T. Tarbell
T. Tarbell
T. Shimizu
M. Shimojo
T.Watanabe

Added the discussions of 3rd Solar-B science
meeting at Hawaii 2002/01/25-26..
Added the discussion of 1st Solar-B MO/DA
meeting at LMSAL 2002/02/20-21.
Editing for clarity, small additions to Data
Policy, comments about VSO and EGSO
Editing for clarity and change a figure in
the section 4.5.
Edjting for clarity

About the Document
The purpose of the document is to describe the latest plan on the mission operation anddata analysis of Solar-B that is now under discussion in the Solar-B MO & DA working
group. This document is still a draft plan and unintended for approval of has not yet
been authorized by the Solar-B project managers in ISAS, NASA, and PPARC, as well as
the principle investigators of the on board scientific instrumentstelescopes.

2002/07/1408

1-2

Version 0.96596

The Outline of Solar-B MO/DA

Contents
1.

Introduction ................................................................................................... 1-41-5

2.

Operations of the Solar-B Satellite and its Onboard Instruments ............... 2-52-6

2.1.

Principles of Solar-B operations .............................................................. 2.1-52.1-6

2.2.

The operation system of Solar-B .............................................................. 2.2-62.2-7

2.2.1.

The personnel of the Solar-B daily operation.................................. 2.2.1-62.2.1-7

2.2.2.

The flowchart of the Solar-B operation ....................................................2.2.2-10

2.3.

Responses to solar activity and coordination with ground-based observatories
2.3-13

2.4.

Scientists resident at ISAS from USA and UK ..............................................2.4-13

2.5.

Software required for daily operations .................................................2.5-142.5-13

2.5.1.

Software for the fundamental operation of Solar-B .................................2.5.1-14

2.5.2.

Software for the operation of the instruments .........................................2.5.2-15

2.5.3.

Special software for the instruments .......................................................2.5.3-17

3.

Scheduling and Submission of Observation Plans and Data Policy ................ 3-18

3.1.

Principles of observation plans and data policy .............................................3.1-18

3.2.

“Baseline” observations and “proposal” observations .....................................3.2-19

3.2.1.

Proposal submissions ...............................................................................3.2.1-19

3.2.2.

Scientific schedule coordinators .................................................. 3.2.2-203.2.2-19

3.2.3.

Proposals for “proposal” observationsエラー! ブックマークが定義されていません。3.2.2-20
3.2.4.

Data policy ................................................................................................3.2.3-20

3.2.5.

Responses to solar activity and coordination with ground-based observatories
3.2.4-20

3.3.

Coordination of data analysis .........................................................................3.3-20

4.

Archiving, Distribution and Analysis of Solar-B Data ..................................... 4-22

4.1.

Fundamental views on Solar-B data processing systems ..............................4.1-22

4.2.

Classification of Solar-B processed data .........................................................4.2-22

4.3.

The flowchart of the Solar-B data processing .................................................4.3-26

4.4.

The Archiving System of Solar-B data............................................................4.4-28

4.5.

The Solar-B data-providing system for the main Solar-B sites at UK and US
4.5-28

4.6.

The Solar-B data-providing and searching system for end-users ........4.6-294.6-30

4.7.

Software required for Solar-B data processing.....................................4.7-314.7-32

2002/07/1408

1-3

Version 0.96596

The Outline of Solar-B MO/DA

1. Introduction

The purpose of this document is to provide the outline of Mission Operation and Data
Analysis for Solar-B.

The document is based on the following documents andpresentations.



The Outline of Solar-B Mission Operation & Data Analysis (Ver. 0.8:J-MO/DA team)Mission Operations and Data Analysis (@FPP-CDR [Tarbell])

Science Implementation

Data Products of the XRT (@3rd Solar-B science meeting [DeLuca])

EIS Ground Based Software Requirements (MSSL/SLB-EIS/SP/022.01)



EIS Science Data Products (@3rd Solar-B science meeting [Harra])

EIS Operation Planning (16/7/01)(XRT: SAO Solar-B Homepage "http://hea-www.harvard.edu/solarb/")(EIS: MSSL Homepage “http://www/mssl/ucl/ac.uk/Solar-B/eis_planning.htm)
Methods for Visualizing Solar Data (@3rd Solar-B science meeting [Berger])

Minutes/resumé of tThe 1st Solar-B MO/DA Meeting @ Lockheed 2002/02/20-21

The following three topics are described in the document.



Operations of the Solar-B satellite and its on board instruments



Scheduling and submission of observation plans and data policyArchiving, distribution and analysis of Solar-B data

2002/07/1408

1-4

Version 0.96596

The Outline of Solar-B MO/DA

2. Operations of the Solar-B Satellite and its Onboard Instruments

2.1. Principles of Solar-B operations
Basic principles of the operationFundamental policies for the operation of the Solar-B
satellite and its on board instruments are summarized as follows:A) The Solar-B team shall coordinate observation plans among the three instruments
aboard Solar-B for, maximizing the scientific results from Solar-B observations. The
items to be coordinated areTarget of the observations



Usage of the data recorder (DR)B) In order to obtain many more scientific results as much as possible, the Solar-B team,when appropriate, shall cooperate when appropriate with coordinated observations
proposed by other satellites and ground-based observatories.
C) Each instrument can run its observation plan independently. The “observation plan”(i.e., observation tables and commands) of each instrument shouldcan be preparedindependently, onceafter the coordination is agreedhas been negotiated.
Along with the basic principlesfundamental policies, the following schemes of the
Solar-B operation are system is proposed as a baselines guideline for further
discussions:.
A) Dutiesy and contributions to the Solar-B operations are as equally shared amongas
possible from Japan, USA, and UK scientists inof the Solar-B teamB) Chief observers (SOT_CO, XRT_CO, EIS_CO) are assigned for scientific operations
planning and health check of theeach instruments. The chief observers reside instay
at the ISAS/SAGAMIHARA campus, Japan.
C) Persons dedicated only to satellite operations planning (“SSOC TOHBAN” in
Yohkoh case) are not assigned. Instead, one of the chief observers should takes
responsibility care forof satellite operations planning, after the sufficient training
has taken place in the initial observing period of theof initial 3-month obervations or
more.
D) Scientists are involved in theneed to join daily real-time operations of Solar-B.
(Since the real-time operation team (engineers offrom the contractorscompanies) at
KSC cannot speak English,) Japanese speaking scientistsscientists who speak

2002/07/1408

2.1-5

Version 0.96596

The Outline of Solar-B MO/DA

Japanese well are assigned for the persons in charge of the real-time operation.
(With the “equal” contribution policy,) Iit is consideredbest that at least one of thechief observers is a Japanese speaking scientist.

2.2. The operation system of Solar-B
2.2.1. The personnel of the Solar-B daily operation
The following 6 or 7 persons are assigned for the daily Solar-B operation.



Chief Observers

(3)

SOT Chief Observer[SOT_CO]XRT Chief Observer[XRT_CO]EIS Chief Observer[EIS_CO]Will be nominated oOne person for eachone instrument in shifts of two weeks(TBD).
➪ The length of shiftperiod (two -weeks) will be changed according tois flexible depending on the nature of observingthe schedules.
Each instrument team should setup their staffing coordinates theschedule of its COs.

Are resident ofResident for the shift at ISAS-SAGAMIHARA/Japan.

Plan the observations, including preparing of the observation tables andcommand plans for the instrument.



Check the instrument status at least daily.

Contribute to collecting and analyzing calibration data.

Japan, US and UK scientists and/or graduate students (who have experience as
the chief observer or the supporter) serve as chief observers. It is best that Ooneof the three chief observers speaksis Japanese, as mentioned before.



Solar-B Chief Planner [CP]

Is The instrument teams will provide a scientist provided(?) by the instrument
teams to serve as “Solar-B Chief Planner” in shifts of TBD duration. Initially,
this person will be different from the chief observer of the for that instrument.



Coordinates the observing plans among the telescopes.

Works on making satellite pointing parameters and satellite commands.



Calculates the parameters of the pointing of the satellite and makes thepointing commands.

2002/07/1408

2.2.1-6

コメント [TW1]: やっぱり削除かな。

Version 0.96596

The Outline of Solar-B MO/DA

Compiles the OP/OG and the command plan requested byafter the three chief
observers, and input the observation tables and commands to ISAC-PLN (TheOP/OG.

and The command plan is automatically generatedmade by“ISAC-PLN”). He/She also transferssends the OP/OG and the commands plan
to KSC for the approval.

Persons responsible for the real-time operation [KSC TOHBAN] (2)Are tThe conductors of the real-time operation.



Stay at Kagoshima Space Center (TBD).



Perform real-time health checks of the Solar-B satellite.

Consist of tTwo persons (one operations expert, and one operations trainee) in
shifts of two weeks.



Need a Japanese speaking skill.

A supporter of the Solar-B chief planner [Supporter](1)



Is aOne person in shifts of one week, if necessary (at maximum?).

Supports the Solar-B chief planner and learns the Solar-B satellite andtelescope operations.



Is a Trainees for Solar-B satellite and telescope operations, are assigned.

And his/her staffing schedule is arranged by tThe science schedule coordinators.
plan the staffing schedule of supporter.

In addition to the persons allocated for the daily operations, the following persons will
support the daily operations and execute the following tasks. Since these following tasksneed continuity, a specificone person will be asignedallocated for a long period of time.



The Ground-Base Contacts Coordinator [GCC](1)

Is aAn ISAS staff member or an engineer from a company.



Schedules the ground-based contacts (KSC and other ground-base stations)

Checks the data transfer amongfrom the ground-base stations

Calibrates the attitude data and makes the S/C attitude database.

Scientific Schedule Coordinator [SSC]

(3 [TBD])

Consist of tThree senior scientists (each fromin Japan, USA and UK,
respectively) perby instrument. and/or by continent (TBD).

CoordinateManage the observation schedule and the proposals.

2002/07/1408

2.2.1-7

Version 0.96596

The Outline of Solar-B MO/DAWill be cContact persons for proposal submissions. If necessary, they will bealso consultants for proposal preparation, and.



WillScience Schedule Coordinators can assign a member of the instrument
teams to consulted on the proposal, if they need help about the instrument.



The coordinator in Japan Mmanages personnel scheduling of the chief planners
and KSC TOHBANs.



Solar-B Database Coordinator [SDC](1)



Is A software engineer.



Stays at ISAS-SAGAMIHARA.



CreateMakes and maintains the Solar-B database system



Maintains the ISAS data analysis computer system of Solar-B.

During the initial phase of the Solar-B operation (about 3 months after the Solar-B
launch), a special setup ofdaily operation setup could be requestedis necessary. In
addition to the daily operation setup as described above, additional persons (satellite
and instrument experts) might have to participate inare required for the daily
operations. One of the persons should be dedicated to “Solar-B chief planner” in addition
to the three3 chief observers during the initial phase daily operation.



SOT, XRT, EIS Engineering Advisors(1)Will be assigned aAt minimumleast one person for each instrument, andwill be Staying at ISAS-SAGAMIHARA/Japan during the initial phase.

Will be rResponsible for power-up and functional checkout of the instrument, as
well as:Preparing the command plans for power up and functional checking

Monitoring the instrument status during real-time operations

Functional checkout and calibration of the instrument, and

Establishing standard procedures for instrument calibrations

SOT, XRT, EIS Software coordinators(1)Will sSetting up the system and environment for data archives and data analysis:Installing and checking the database softwareMaking and installing the data analysis software

2002/07/1408

2.2.1-8

書式変更 : 箇条書きと段落番号

Version 0.96596

The Outline of Solar-B MO/DA

Setting the data analysis environments

2002/07/1408

2.2.1-9

Version 0.96596

The Outline of Solar-B MO/DA

2.2.2. The flowchart of the Solar-B operation

The Flowchart of Solar-B Operation
Solar-B Team

Scientists

Observing Plansof Solar-B Team

Proposals ofObservation

Monthly Operation Meeting

Weekly Operation Meeting

Daily Operation Meeting<Every 15th(TDB) Meeting @ Tel-Conference>
Participants : Project Manager, PIs,
Scientific Schedule Co-ordinator,
Database Co-ordinator, Chief Observers
Aims : Status Review of Satellite, Instruments and Database
Adoption of proposals
Discussion of the observation plans and staffing forfollowing 3 months
Decision of the Monthly Observation Plan
<Every Friday (TDB) Meeting @ ISAS>
Participants : Project Manager, Chief Observers,
Scientific Co-ordinator, Dec.,
Ground-base Contacts Coordinator, Chief Planner
Aims : Status review of satellite, instruments on the last week
Selection of some target regions
Review of observation plans on this week
(Pointing, Table uploading schedule)<Every Morning (10:30 JST [TDB]) Meeting @ ISAS>
Participants : Chief Observers, Decchi, Chief Planner
Ground-base Contacts Co-ordinator
Aims : Status review of telescopes and satellites on the day
Allotment of the data recorder to telescopes
Final decision of the target region (Pointing)Decision of the plan the real time operations

Operation Planning@ SSOCReal Time Operation @ KSC

See <The Work Flow of Solar-B Operations @ SSOC>

Solar-B Observation
Solar-B/Satellite & PI
Health Check System
See <Solar-B/The flowchart of Observation Data>

Data Reformat System

Solar-B
Database System

Scientists

2002/07/1408

2.2.2-10

Version 0.96596

The Outline of Solar-B MO/DA

The workflow of Solar-B mission operation
Solar-B Chief Planner(One of COs and DECCHI)

SOT, XRT, EIS Chief Observers

Ground-base Contacts Coordinator

Scientific Schedule
Coordinator
The plans andproposals ofObservations< Monthly Operation Meeting >Orbital Elements(Preliminary)

Schedulingwith groundbase stations

Ground-baseContacts Schedule

Predict
Environmentsof thesatellites

The monthly plansof observations

Calculate
Average
Downlink

Make the plan ofObservations(If there is not any
proposals and plans)Satellite's
Environments Data
(SAA, Night, etc.)

Average Downlink
for Solar-B<Weekly Operation Meeting>
Orbital Elements(Final version)

Scheduling withground-basestations

Ground-baseContacts Schedule(Final)Predict
Environments ofthe satellite(For ISAC-PLN)

The weekly plan of
the observations
Calculate
Average
Downlink

Satellits's
Enviroments Data
(SAA, Night, etc.)

Average Downlink
for Solar-B (Final)

Compile theContacts
Schedule for
ISAC-PLN

Ground-baseContacts Schedule(For ISAC-PLN)<Daily Operation Meeting>Make theplan ofReal TimeOperations

Make theplan ofpointing

Compilethe plan of
RealTime
Operations

Make thecommads
for pointing

The command plansof real-time
operations

Pointing Commands

Make theobservingtablesCompile theobservingtablesThe observing
tablesMake thecommandplans for
instruments

ExampleCompile thecommandplan forinstuments

Data or Document

Check theoutput data
rate from
instrments

The command planfor instruments
Data(ISAC-PLN
Format [binary])

ISAC-PLN System

The command plansof real-time
operations

OP

Data
(ISAC-PLN
Format [XML])

Observing Tables

Computer
ProgramComputer
Programs(Output data
are ISAC-PLN
format data)

Check OP &commands
Handwork

Send to KSC (by ISAC-PLN System)

2002/07/1408

2.2.2-11

Version 0.96596

The Outline of Solar-B MO/DAMonthly Meeting [Tele-conference]Participants: Project Manager, Principal Investigators, Science Scheduling

Review of the satellite and instruments status



Review of the proposals that have been received during the month

Adoption of proposals

Discussion of the observation plans and staffing for the following 3 months

Coordinate staffing for the following (2nd) monthDecisions on the next monthly plan.



Prioritize theeach observations offor the next month, and make the priority list

Coordinators, Chief Observers, Database Coordinatorof the observations.


Weekly Meeting [@ISAS every Friday]Participants: Project Manager, Chief Observers, Chief Planner, Supporter,
Ground-base Contacts Coordinator, Science Scheduling Coordinator(Japan)

Review of the satellite and instruments status in the week

Review of the schedule of ground-base contacts for the next week

Review of the observation plans for the next weekSelection of some target regions and decisions on the pointing maneuverschedule of next week (nearly final)

Decisions on the schedule of observation plans for next week (nearly final)

Allocation of the data recorder (DR) for each instrument (nearly final)

Daily Meeting [@ISAS every weekday (TBD) morning]Participants: Chief Planner, Supporter, Chief Observers,

Confirm the target regions

Confirm the allocation of the DRConfirm the pointing and the schedule of pointing maneuvers.

Confirm the operation plans of the next-day real-time operations in next day.



If there are some changes in the schedule of the ground-base contacts,

Ground-base Contacts Coordinator

reallocate the data recorder for each instrument.
The deadline for input to the next day’s operation plan inputs (commands,
observation tables, etc.) to the Solar-B Chief Planner is 15:00 JST each day.

2002/07/1408

2.2.2-12

Version 0.96596

The Outline of Solar-B MO/DA

The entire Solar-B operation plan for the next day, including the command plans
during KSC real-time operations, the OP/OG, and the observation tables, iscompleted and sent to KSC for approval by the evening. The KSC TOHBANs makethe final check of the operation plan in the evening.



As a general guide line, the operation plans are approved daily bases. However, iIn
case an urgent operation plan changes isare requested as the result of checking thedata downlinked foundduring in the morning passes real-time operations, theplanners should make the revised plan for the evening real-time operations as soon
as possible. However, the general policy is that they do not change the operationplans during the day.

2.3. Responses to solar activity and coordination with ground-based
observatories
See “3. Scheduling and submission of observation plans, and data policy”

2.4. Scientists resident at ISAS from US and UK
We (the Japanese team of Solar-B) would like to ask the UK and US teams forabout
several scientists resident at ISAS.

At least two scientists staying at ISAS from each instrument team:
Theyir aims are

Chief Observer of theeach instrument

A scientist for jJoint data analysis and scientific discussions among US,
UK, and Japan.



In the initial phase of the solar-B operation, additionalsome scientists and/or
engineers fromof each instrumenttelescope team need to stay at ISAS.

We should note that Japan side does not have the manpower for the management of the
Solar-B database, and Wwe, the Japanese team, expect major contributions offrom the
US and UK teams for the management of the Solar-B database.

2002/07/1408

2.4-13

Version 0.96596

The Outline of Solar-B MO/DA

2.5. Software required for daily operations
In order to reduce the burden of operations and increase the time for the scientificplanning, all software for the operation is expected to be of the highest quality and very

コメント [TW2]: 「ソフトウエアの質が高user friendly. In the following sections, we describe the software for the operation of theい」というのは具体的にはどういう意味で

satellite and instruments.

すか？

2.5.1. Software for the fundamental operation of Solar-B
Responsible parties for software development are indicated in the parentheses.



Prediction of the satellite environments(Japan)This software predicts the timing of ground -stationbase contacts, South Atlantic
Anomaly, Pole anomaly and night periods of the satellite, calculating from theorbital elements. The software produces the graphical time chart and the list of
events. These are very useful not only for planning of observations but also fortroubleshooting of the spacecraft. In ISAS, the software is called “AOSLOS”.



Estimating the downlink data size

(Japan)After the coordinanegotiating with the ground-base stations, the schedule of thestationground-base contacts of Solar-B is made from AOSLOS data and theschedule of the ground-base stations. The software estimates the volumecapacity

コメント [TW3]: この文章意味不明で、修of downlink data using the contacts schedule. The estimated data sizecapacity is

正できず: 「局受信のスケジュールを局受

used for coordinating the usage of the data recorder (DR).

信のスケジュールから作る」？

Support Software for Creating OP, OG and the real-time commanding plans(Japan)In the Solar-B project, the ISAC-PLN software package is available used for the
management of the command plans, OP, OG, and the observing tables. The
package can also create OP and the real-time operation plans based on the list of
events, such as (examples of events are ground-base station contacts, SAA andsatellite nights). Hence, tThe support software creates the event lists from the
AOSLOS data and the plan of observations, and therefore, it. The software has aninterface to ISAC-PLN.



Supporting software for checking OP and the real-time commanding plans

2002/07/1408

2.5.1-14

Version 0.96596

The Outline of Solar-B MO/DA(Japan)ISAC-PLN creates OP and the real-time command plans based on the inputs from
Chief Planner and Chief Observers. The software makes the graphical time-line
charts, based on taking OP, the real-time operation plans and the prediction of thedata output rate from each instrument into account. The time-line also indicates thestoraged data volumeusage of the data recorder.



Making commands required for the satellite pointing(Japan)The chief planners for all 3 instruments can request theto change of thespacecraft pointingfield of view by a maneuver of the satellite. THence thesatellite, therefore, may be able to change the pointing several times aduring oneday. Since the parameters for commanding spacecrafta maneuver are complicated,and miscommandingtakes in making them may lead to have serious consequences,
the software should calculate the parameters for s/c maneuvers from the solar
coordinates of the target regions as inputs. The software will be developed by thecompany that develops the attitude control system of Solar-B.



Health check reformat software (CCSDS > IDL)

(Japan)For the health check and monitoring system, the raw-telemetry data must be
reformatted from CCSDS format to the IDL-readable format. The prototype of thisreformatter software was already used in the proto-model system test held last year.



Health check and monitoring system for the Satellite(Japan)During the real-time operations at KSC, the KSC TOHBANs checks the health ofSolar-B using the health check and monitoring systems. The system is used forchecking the fundamental status of Solar-B, for example, battery voltages,
temperatures, and etc.. The company that develops the telemetry system provides
the software.

2.5.2. Software for the operation of the instruments
It must be possible for users to design their own observational studies to address aparticular scientific question. Software must be available to all users to chooseexplore

コメント [TW4]: この文章も私には何を言

instruments setup parameters and to simulateview the observationexpected data

おうとしているのか、理解ができませんし

return.

たので、無修正です。

2002/07/1408

2.5.2-15

Version 0.96596

The Outline of Solar-B MO/DA

The database system of Solar-B operation and observation(Instrument teams and Japan)
All previous observational studies must be archived so that they can be recalled

コメント [TW5]: 「observational study」

by name, identification number or scientific objective, for ease of rerunning and/orの定義がこのパラグラフの前に必要。

modifying. When new studies are designed, they shouldcan be cross-checked
withagainst theseis archives for close or exact matches so that the user can
examine the real data that was obtained from a in the previous similar
observations. Cross-checking by introducingand assigning an intelligent
identification scheme will limit the size of the archive and the capability ofaid
new users in designing the studyies. The exact form of the identification scheme is
yet to be decided. AThere shall be a validation process will be introduced toensure that studies cannot harm the instrument.

コメント [TW6]: 直した本人もどうもしっくり意味がわかっていない。

Software for creating the observing tables(Instrument teams)

Chief Observers make the observing tables for each instrument based on theobservation plans. This software creates the command sequence of the observing
tables based on the observing plan of the chief observer. The software hasinterfaces with ISAC-PLN, and refers the database of Solar-B operation andobservation, as well as with instrument-specific databases and/or software. The
software also has an interface with the Solar-B database for collecting the ID,
name and comments of the observing tables. The comment items of observing
tables will follow theare based on SOHO IAP (TBD).

Support software for command plans for the instruments(Instrument teams)
When an instrument needs to some commands tofrom the MDP (e.g., to stop theobservation when the satellite changes the pointing), Chief Observers makecommand plans for the instruments. Tthe command plans may include many
real-time commands and the sequences and timings of the delayed commands forvarious instruments via MDP. Hence, this software needs to refercreates thecommands plans, based on the event lists and eachthe Chief Observer’s plan. The
software also has an interface with ISAC-PLN.



Estimating the output data rate and size offrom the prepared observing table(Instrument teams)
This software generate makes the time-line of the observationing sequence from2002/07/1408

2.5.2-16

Version 0.96596

The Outline of Solar-B MO/DA

the observing tables and estimates the output data size between the
ground-stationbase contacts. The Chief Observer checks that the estimated data
size from observing table does not exceed the allocated size of DR for the
instrument.



Health check and monitoring system for the instruments(Instrument

teams)
During the real-time operations at KSC, the KSC TOHBANs checks the health of
the instruments using this system. The system displays the status of the
instruments and real-time images. The data distribution system at KSC is asthesame as that at ISAS/SAGAMIHARA, which wasis used duringfor the Proto-Model
test, and will be during the Flight-Model test, as well. Hence Wwe will use the same
software developed infor the PM and FM tests, and in the real-time operations at
KSC with minorsome revisions.

2.5.3. Special software for the instruments


Making MDP/SOT Doppler parameters.

(Japan + SOT team)Since the wavelength setups of the spectropolarimeter and the narrowband
tunable filter of SOT are affectinfluenced by the orbital motionvelocity of thesatellite, MDP accomodateshas an on board software to calculate the Doppler
velocity of the orbit based on the Doppler parameters. The software calculates the
Doppler parameters from based on the spacecraft orbital elements uplinked in a
regular time interval.

Communication with the Deferred Command Store (DCS)(EIS team)

Software will be developed in the EIS team to send the observing plans must be
sent to the DCS for communication with the spacecraft.

Software must be

available to do this and Tthe EIS planning tool has an interface to thesoftwarewith it.

2002/07/1408

2.5.3-17

Version 0.96596

The Outline of Solar-B MO/DA

3. Scheduling and Submission of Observation Plans and Data Policy

3.1. Principles of observation plans and data policyi.

Solar-B data should be open to the public as quicklyearly as possible. (TheJ-side proposal baseline for discussions regarding the data policy is asfollows:) The Solar-B team and their collaborators take priority for using
the data for TBD period (for example, 6 months) after logged in IAS
collection. After the elapse of this period, all the data are open to the
public.

i.ii.

Solar-B

operations

will

be

operatedplannedaccordingtothepre-determined “initial 3-month observation plan” during the firstinitial 3(TBD) months. Each of the initial phase observation plans shouldduring
the initial phase will be reviewed and prioritized by the Solar-B team. For
finalizing making the “initial observation plan”, the Solar-B team should
receive have comments from outside the Solar-B team.
ii.iii.

The “baseline” observations starting after the initial phase will come outof from the successful observation plans tested during prepared for the
initial phase3-month plan. “Proposal” observations will be allocatedamong the scheduled in “baseline” observations.

iii.iv.

Proposals for “proposal” observations from inside and outside the Solar-B
team will beare submitted to the scientific scheduling coordinators (see2.2.1).

iv.v. A “gentlemen’s agreement” (what is a better term? Consensus inside andoutside the Solar-B team?)is required necessary to ensure data-use

priority offor graduate students to pursuinge their PhD researches and to
avoid unnecessary copetitions or duplications withwithout competition or
duplication by other scientists. Members of the instrument teams, andespecially the scientific scheduling coordinators should be aware of the
PhD research projects in progress and should urgestrongly discourage anyother scientists to avoid overlapping of their research topicsfrom work

2002/07/1408

3.1-18

書式変更 : 箇条書きと段落番号

Version 0.96596

The Outline of Solar-B MO/DA

which overlaps closely with a PhD topic.
It is not easy to predict the lifetime of the Solar-B. Hence, we should carefully review
the science priority and observation plans before the launch of Solar-B, and crystallize(?)
define the initial observations intoas the initial 3-month observation plan. (The Solar-B
team should start to discuss science priorities.y Creating and the initial 3-months
observation plan isshould be one of the mostan important tasks of the Solar-B team
before the launch.)topic at future Solar-B science meetings.

3.2. “Baseline” observations and “proposal” observations
Observations after the initial 3 (TBD) months will consist of “baseline” observations and“proposal” observations. The “baseline” observations will beare standard observations
that are performed by the Solar-B team continuously throughfor itsthe mission life.
“Baseline” observations will emerge from come from the observation plans conductedduring prepared for the initial 3 (TBD) -monthes observation plan. The “proposal”
observations will be executedare based on the proposals that are submitted to thescientific scheduling coordinators. The Solar-B team welcomes Jjoint observations withother satellites and ground-based observatories will be promoted.

3.2.1. Proposal submissionsAll proposals shall be in English.

In order to receive proposals from scientists and students inside and outside theSolar-B team, the scientific schedule coordinators will beare assigned as contact
points and also as consultants for the proposals.

Proposals will beare discussed at monthly operation meetings.

Hence, astandardthe baseline deadline forof the submission will be setis before the monthly
operation meeting in which the particular operations will first be discussed for the
first time, typically 3 months before the observations will be taken place.
The Solar-B team will provides the guidelines for proposal submission.

The Solar-B team will provide documents and software helpfulnecessary for
proposal preparing proposals ation (for example, those of predicting the photon
counts and of simulating observations).

2002/07/1408

3.2.1-19

Version 0.96596

The Outline of Solar-B MO/DA

3.2.2. Scientific schedule coordinators
The scientific schedule coordinators are the contact points and consultants for(preparation or evaluation of ?) observation proposals. Using the received proposals,
they prepare a draft monthly schedule of observations schedule presented in for the
Solar-B monthly operation meeting.

Each instrument team shall haveThere is a science schedule coordinator, to whom
for each instrument. P proposals should be sent. to science schedule coordinators.

They will beare authorized to select some from incoming observation proposals
observations, and to draft for defining a draft of the monthly observation schedules.
They will be are also authorized to reject proposals, if the proposals are inadequetly
not properly submittedprepared, the same observation plans are already proposed,or the essential parts of the proposedscientific plans overlap too much with a PhD
thesis in progress, etc.

3.2.3. Data policySee. “3.1 Principles of observation plans and data policy”

3.2.4. Responses to solar activity and coordination with ground-based
observatories

Target of Opportunity campaigns will can be insertedentered in thea monthly
planning.s

Proposals for these campaigns should be sent to Science Schedule Coordinators.



Chief Observers and the Chief Planner decide the target in the daily meeting basedon the priority list of observations [see 2.2.2]. They have the discretion to choose
targets of opportunity, in case they are included in when the monthly plan allows
them.

3.3. Coordination of data analysis
To protect the ensure data priority offor graduate students to pursuinge their PhD
researches, without competition or duplication by other scientists, the Solar-B teamshould providemakes the list of PhD research themes of graduate students in the
Solar-B team. The list will beis accessible from the homepage of Solar-B. Members of the

2002/07/1408

3.3-20Version 0.96596

The Outline of Solar-B MO/DA

instrument teams and especially the scientific scheduling coordinators should be awareof the PhD research projects in progress and should strongly make strong efforts to avoid
overlapping of their research topics with others.discourage any other scientists fromwork which overlaps closely with a PhD topic.
Open Items


Need to define who are is involved in the Solar-B team.



Need to define who are collaborators of the Solar-B team.



Need to find What is the best way to encourage scientists from outside the Solar-B
team to makewith “proposal” observations.? They should have the same priority forusing the data, as the Solar-B team members do (?).



Need to specify the length ofHow long do we need for the initial phase? (is 3 monthOK?)

Need to specify the length for privileged data use: Is it the proper solution to givedata priority to the Solar-B team and their collaborators for 6 months (TBD) after
logging in ISAScollection?

How to protect the data during the above 6 months (TBD)?
Option 1: Using software (ex. Password? Closed website?)
Option 2: Gentlemen’s agreement?



Need to specify the level for acceptance of proposals: In wWhat quality and how
much in detail proposals do we accept the proposals?

2002/07/1408

3.3-21Version 0.96596

The Outline of Solar-B MO/DA

4. Archiving, Distribution and Analysis of Solar-B Data

4.1. Fundamental views on Solar-B Data processing systemA) The Solar-B telemetry data processing system uses the ISAS satellite databasesystem: the SIRIUS database for raw telemetry and the SDTP protocol for obtaining
raw telemetry data.
B) Existing aAnalysis tools, such as that already exist (for example, the SSW or
SolarSoft package,) will beare also usableed for Solar-B data analysis, if whenappropriate.
C) For health checks of the instruments, we will reviseuse the health check systemused in developed for the proto-model system test, with some revisions.
D) To ensuremake efficient data accessibility possible not only amongfor the Solar-B
science teams but also infor the wider solar community, the Solar-B data providing
system shallwill be designed to be compatible, if possible, with the Virtual Solar
Observatory (VSO) and the European Grid for Solar Observations (EGSO), or theirsuccessors.

4.2. Classification of Solar-B processed data
The Solar-B data are classified into the following categories based on the processing
levels.



Raw telemetry data

Health check data

Level-0 dataCalibration data

Level-1 data

Level-2 data

Level-Q data

In addition to these levels of data, we will needObserving logs and data catalogues used for archivingsearching

In thise section, we explain these data levels.

2002/07/1408

4.2-22

コメント [TW7]: 何を捜すの？

Version 0.96596

The Outline of Solar-B MO/DA

Raw telemetry dataThey are the data received at KSC and the other ground-based stations. The
format of the data is “CCSDS packet” format.

All raw telemetry data of Solar-B are archived on the “SIRIUS” database, . Thisis the ISAS satellites database at the ISAS/SAGAMIHARA campus., and ISAS
maintain all the data of the ISAS satellites are via this database on line in the
database.

The “SDTP” protocol (ISAS original protocol) is used to retrieveget the datafrom the SIRIUS database.



Health check dataThe data will beis reformatted from raw telemetry data to IDL-readable data.
The data include not only observationaling data but also status data of the
instruments.



These data are mainly used for the health check and monitoring systems of the
instruments. They are also used for planning the next day’s observations.



Raw telemetry data are compressed by MDP using JPEG or DPCM. Since theimages are displayed on the health check and monitoring systems, tThe data
areis decompressed, in case necessary, during the reformatting process.

One file per instrument or data species (real-time, playback???) is created for

コメント [TW8]: RL PB の「種別」のこと

each downlink (real-time passes only?)

でしょうか？

The health check data will beare createdonly used temporarily and not stored
in an archive.



Level-0 data

Reformatted raw telemetry data file.

The data format of Level-0 is FITS with binary table extension (TBD).



The data include a header that is constructedmade from the telemetry data (ex.
observing time, exposure time, pixel size, coordinates on the CCD, etc.) and theSolar-B operation database (Table ID, Table name, Comments from Chief
Observer, etc.).



Although the data are compressed by MDP using JPEG and DPCM, Tthe
Level-0 data are yet still non-decompressed data to save the data storage
volume and to save the network bandwidth.



One file per instrument, per downlink, or hourly (TBD); or one file per one map
or one raster (TBD).

2002/07/1408

4.2-23

Version 0.96596

The Outline of Solar-B MO/DA

Level-0 data are not calibrated.



RLevel-0 data include the raw data used for calibration (e.g., dark images), will
be included in Level-0 data, when appropriate.



Level-0 data are provided by the Solar-B data-providing system.

Calibration dataCalibration data are made from Level-0 data, pointing data of Solar-B,
pre-launch test data, appropriatesome spectrum synthesis models, etc.



The data are used to derivefor calibration of photon intensity, spectral line
wavelength, etc., and for attitude determinationderivation of accurate pointing
information..



The format of calibration data is the same as that of Level-0.

Calibration data are also provided by the Solar-B data-providing system.

When calibration data are revised, the instrument team should announce therevision using the homepage of Solar-B, e-mail, etc.

Level-1 data

Level-1 data are made from Level-0 and Calibration data using software of the
SSW/SOLAR-B package.



Level-1 data areis fully calibrated and haveincludes the headers. The header ofLevel-1 includes the contents of Level-0 header, the coordinates on the sun,information of the calibration data, etc.



The format of level-1 data is standard FITS (TBD).



The data are not provided by the Solar-B data providing system.

コメント [TW9]: 肯定文にしたいのですが…



Level-2 Data

Level-2 data are made from Level-1 data.



Level-2 data are in physical unitsquantities, and consist of files such as
longitudinal magnetogram, Dopplergram, vector magnetogram, filling factor, B
vector, etc.



The format of Level-2 is the same as the Level-1.

The level-2 data haveinclude the headers that includes the Level-1 headers andadditional information about the derivation.

Level-2 data areis compressed by loss-less compression methods.

Level-2 data which are standard data products made by the instrument teams
They are also provided by the Solar-B data-providing system. AdditionalSome

2002/07/1408

4.2-24

Version 0.96596

The Outline of Solar-B MO/DA

other Level-2 data volunteeredmade by the team members and submitted to thearchive may also be provided in the samethis way.
The suggestion from XRT team.
Level – 2 meta data: Combinations of Solar B level - 1 data sets, mission objectives
and external (e.g. GOES) data in a variety of formats (data bases linked to dataarchive, html ...).



Level-Q data

Level-Q data are made from Health check data or Level-0 data.



Level-Q data are made for monitoring the health and status of the instruments
and for reporting the status of Solar-B observations to other satellites andground-based observatories.



The data are accessible via the Solar-B homepage after every KSC contact,
immediately and automatically.



Examples of Level-Q data areStatus data of S/C and the instruments (text and plots)Snapshot images (and movies) observed with SOT filtergraph.



Magnetograms are made from the SOT filtergrams



Snapshot images (and movies) observed with XRTImages observed with EIS (using several main lines)Atlases of spectra observed with EIS.



The format of the data is PNG, JPEG or MPEG.

OnIn the Solar-B homepage, the future schedule of the observations (target
region, observing table descriptions, etc.) is also given.

2002/07/1408

4.2-25

Version 0.96596

The Outline of Solar-B MO/DA

4.3. The flowchart of the Solar-B data processing<System for Operation>

ISAS Satellite
Data Management
system

KSC Receiver &Data Distribution
SystemHealthCheck
Reformat

Instruments
Health Check
SystemSatellite
CommonHealth Check
SystemReal-Time Operation@ Kagoshima Space Center (KSC)@ Sagamihara Satellite Operation Center (SSOC)

Satellite
CommonHealth Check
SystemHealthCheck
Reformat

Instrument
Health Check
SystemDaily Health
Check of
Instrument
by CO

Level-Q
Reformat

Level-Q Data
(JPEG, MPEG)

Daily Status
Report ofInstrument

Quick Look system for
non-operation team(Web System)

Observing data from the other ground-base stations<Data Reformatting System>
SIRIUS
Database

Level-0
Reformat

Level-0 data

Pre-launchtest data

Pointing data

OrbitalEnvironments(SAA, Night, etc.)

CreateCalibration
data

Level-1
Reformat(Calibration)

Level-2 Reformat(Physical Quantities
Derivation)

Calibration data

Level-1 data

Level-2 data

The Archiving System of Solar-B Observing Data

2002/07/1408

4.3-26

Version 0.96596

The Outline of Solar-B MO/DA

The Archiving System of Solar-B Observing Data
The Solar-B Data Providing System for end-users (Web-based System)

Level-0 Data

Calibration Data

Level-2 Data

Data
Analysis by
Scientists

Software of
Calibration(SSW software)

Data
Analysis by
Scientists

Calibrated Data

Data
Analysis by
Scientists

User's System

User's System(If scientists get
Level-2 data)(If scientists get Level-0 data)

ExampleComputer
Program

Observation Data

Data orDocuments

Handwork

Database

Web System(Providing System)

Computer
Program(QL System)

Data Flow
Data Flow (by SDTP)
Data Flow(by HTTP or FTP)

Open ItemIs there enough bandwidth between SIRIUS-ISAS and the ground stations totransfer the Solar-B data efficiently? SIRIUS – KSC is OK.

2002/07/1408

4.3-27

Version 0.96596

The Outline of Solar-B MO/DA

4.4. The Archiving System of Solar-B dataThe master database, containing (Level-0, 2, Q and Calibration data) areis
constructed inmade at ISAS.

The Solar-B data archiving system use the resources of the ISAS-DARTS
system (http://www.darts.isas.ac.jp/). The purpose of the DARTS system is toarchive data and distribute

ISAS space science data obtained via ISAS

spacecrafts. The DARTS system is accessible from everywhere by using throughweb browsers.


The DARTS system provides only hardware (e.g., HD, Server) and some
software (e.g., Oracle) for the archiving and providing systems. The mission
specific system needs to be provided by the Solar-B team.

4.5. The Solar-B data-providing system for the main Solar-B sites at UK and US
We will make the copies of the Solar-B database at several institutes, for example, NAO
in Japan, LMSAL, SAO, NRL, GSFC in US and MSSL in UK. However, we will be notable to copy the full database (include Level-0, 1, 2, Q, cal. data) using the Internet. The
origin of the problem is the bandwidth of the inter-country network (Japan-US,
Japan-UK, US-UK). In the current status, the bandwidth of the network is not enoughto transfer Level-1 data. And the bandwidth of the inter-country networks does not growlike the Moore’s law. If we use the DVD-ROM or CD-ROM for the data transferring ofLevel-1 data, the delay between Japan – US, UK could be several months from theobservation (in YOHKOH case), which is too long.
In the Solar-B project, level-1 data will be not archived and provided using Solar-B
providing system since the calibration data couldwill be revised during initial phases.
Hence, we transfer only level-0, Q data and Calibration data using the Internet fromJapan to US and UK. However, the vector magnetograms and associated Level-2 data
have to be provided by the Solar-B team since the calibration and Stokes parameter
inversions are complicated. These Level-2 data will be provided from LMSAL (themanufacturdeveloper of FPP) to Japan, UK and other US sites using the Internet since
the size is less than 1/10 of that of original Level-0 spectropolarimeter data.

2002/07/1408

4.5-28

Version 0.96596

The Outline of Solar-B MO/DA

Level-0
RefromatSolar-B Databasein Japan

FPP/SP Level-1 & 2
Refromat @LMSAL

Solar-B Databases
in USTransfer
Level-0 & Cal. Data
using the internet
Transfer Level-2 data
(FPP/SP)
using the internet

Solar-B Databases
in UK

4.6. The Solar-B data-providing and searching system for end-users
A data-searching system is required for efficient data analysis. The system
uses relational database software (ex. Oracle, PostgresSQL). The following
figure is a plan of the Solar-B data-searching and providing system based on
the relational database and the web system
Open Item
If we use the Oracle system, we need a full-time Oracle system administrator atleast 1st year or two and a trained Oracle programmer.



The software must support a GUI interface to the database for end-users. Users
must be able to design queries to the database with the results viewable onscreen and optionally printable. The user interface should access Level-Q data.
[EIS team suggestion: The software support IDL GUI interfaces.]

2002/07/1408

4.6-29

Version 0.96596

The Outline of Solar-B MO/DA

Solar-B Data Searching and Providing Systemfor end-users (Scientists)
Level-0 Data

Calibration Data

Level-1 Data

Level-2 Data

Level-Q Data

Observing Data
Filenames

Solar-B / Observation Data Archive
Observations
Tables

The comments ofChief Observers

Filenames of data
The Relational Database of
Solar-B Observations

Pointing Data

OrbitalEnvironments Data
(SAA, Night)

Solar-B data
(Level-0,1,2, Calibration, Level-Q..)
Requests withsearch keys
(Time, Pointing, etc.)

Solar-B Data Providing Web-Server

Solar-B Data

Scientists

2002/07/1408

4.6-30

Data Requests(Time, Pointing,Region, event)Solar Geophysical
Data(Flare, No. of AR)

Version 0.96596

The Outline of Solar-B MO/DA

The data distribution and searching systems of Solar-B are located at several

sites including ISAS, USA and UK. The data of the relational database are
mirrored using the Internet every day (the observing data are not mirrored
using Internet).

4.7. Software required for Solar-B data processingLevel-0 reformat software (IDL > TBD format)


The Solar-B software developing team makes the softwareThe file format and header contents (not only Leve-0 but also Level-1 and 2)
are designed and managed by the Solar-B team.



Level-1 reformat software (calibration)Level-2 software (derivation of physical quantities)Each instrument team provides the software for calibration.
Each instrument team provides the software for derivations.

Level-Q reformat software (Images and movies for Quick Look)The Solar-B software developing team makes the softwareThe experiences of Yohkoh/SXT, SOHO and TRACE are very useful for the
Level-Q reformat and web system.



Data-providing and searching systemThe system is made based on the web server system and athe relational
database system.



SThere is a software packages for management of the relational database areavailable (e.g., Oracle, mySQL, PostgresSQL, IDL-DB [UIT]).



The web interfaces (User-DB) are important.

The search keys are based on the contents of FITS headers.



The system will be compatible if possible with the Virtual Solar Observatory
and European Grid for Solar Observations, or their successors

Data analysis softwareCommon parts of the data analysis software (ex. I/O of Level-0, 1 and -2) aremade by the Solar-B software developing team.



The SSW package is used for the development of the Solar-B data analysis
software.



Software that is closely related to the instruments (calibration, inversion, line
fitting, etc.) is provided by the instruments teams.

Solar-B data analysis software will become part of the SSW package, open to

2002/07/1408

4.7-31

コメント [TW10]: 何に？

Version 0.96596

The Outline of Solar-B MO/DA

the public.
The Solar-B team prepares the guidebook for Solar-B data analysis, which issimilar to YAG (Yohkoh Analysis Guide).



Who are the software developing team of Solar-B?

2002/07/1408

4.7-32