Version 0.99C

The Outline of Solar-B MO&DA

DRAFT

The Outline of Solar-B
Mission Operation & Data Analysis

Version: 0.99C

The Solar-B MO&DA Working Group
2005-09-20

2005/09/23

1-1

Version 0.99C

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

M. Shimojo
T. Tarbell

Version 0.95

2002-07-03

T. Tarbell

Version 0.96

2002-07-08

Version 0.965

2002-07-14

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
meetingat
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.
Editing for clarity

Version 0.97

2002-07-16

T. Shimizu

Editing for clarity

Version 0.98

2003-01-23

M. Shimojo

Version 0.99

2003-10-17

T. Tarbell

Version 0.99B

2004-02-04

T. Tarbell

Added the comments at 2nd Solar-B
MO&DA Meeting at SAO 2002/07/17-19.
Added comments from 4th MO&DA Mtg,
March, 2003, at NRL and US MO&DA
Mtg., Oct 2003, at LMSAL.
Added
Introduction to the mission
Comments from SWG meeting, Nov 2003

Version 0.99C

2005-09-21

T. Tarbell

Comments from MO&DA meeting, Oct,
2004 at SAO and US MO&DA Mtg., Aug,
2005, at NRL

About the Document
The purpose of the document is to describe the plan for the mission operations and data
analysis of Solar-B that has been developed in the Solar-B MO & DA working group
and Science Working Group. Version 1.00 is signed by representatives of JAXA, NASA,and PPARC to indicate its acceptance by the Science Working Group.

2005/09/23

1-2

Version 0.99C

The Outline of Solar-B MO&DA

Contents
1.

Introduction............................................................................................................ 1-4

2.

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

2.1.

Principles of Solar-B operations ............................................................................ 2-9

2.2.

The operation system of Solar-B ........................................................................... 2-9

2.2.1.

The personnel of the Solar-B daily operation ................................................... 2-9

2.2.2.

The flowchart of the Solar-B operation ............................................................. 2-9

2.3.

Scientists resident at ISAS from US and UK ...................................................... 2-9

2.4.

Software required for daily operations ................................................................. 2-9

2.4.1.

ISACS-PLN ......................................................................................................... 2-9

2.4.2.

Software for the fundamental operation of Solar-B ......................................... 2-9

2.4.3.

Software for the operation of the instruments ................................................. 2-9

2.4.4.

Special software for the instruments ................................................................ 2-9

2.4.5.

The summary table of the Solar-B operation tools ........................................... 2-9

3.

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

3.1.

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

3.2.

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

3.2.1.

Proposal submissions ................................................................................. 3.2.1-28

3.2.2.

Scientific schedule coordinators ................................................................ 3.2.2-28

3.2.3.

Data policy ............................... エ ラ ー ! ブ ッ ク マ ー ク が 定 義 さ れ て い ま せ ん 。

3.2.4.

Responses to solar activity and coordination with ground-based observatories
3.2.3-29

3.3.

Coordination of data analysis .... エ ラ ー ! ブ ッ ク マ ー ク が 定 義 さ れ て い ま せ ん 。

4.

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

4.1.

Fundamental views on Solar-B Data processing system ................................ 4.1-30

4.2.

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

4.3.

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

4.4.

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

4.5.

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

4.6.

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

4.7.

Software required for Solar-B data processing ............................................... 4.7-40

5.

Acronyms .............................................................................................................. 5-42

2005/09/23

1-3

Version 0.99C

The Outline of Solar-B MO&DA

1. Introduction
1.1 Overview of the Solar-B Mission

Solar-B is an international cooperative mission between JAXA/ISAS of Japan, NASAof the United States, and PPARC of the United Kingdom. It builds on the great successof the Yohkoh (or Solar-A) mission and is the second of NASA’s Solar Terrestrial Probes(STP), which address fundamental science questions about the physics of spaceplasmas and flow of mass and energy through the solar system. It will perform
coordinated, simultaneous measurements of the different layers of the solar
atmosphere from a Sun-synchronous orbit around the Earth. Three instruments will
perform these measurements, a Solar Optical Telescope (SOT), an Extreme Ultraviolet
Imaging Spectrometer (EIS), and an X-Ray Telescope (XRT). The instruments willmeasure the Sun’s magnetic field in the photosphere and the ultraviolet and X-ray
radiation, emitted by the transition region/low corona, and the upper corona. Scientists
will use the data obtained with the instruments to increase the scientificunderstanding of the sources and mechanisms of solar variability. The primaryscientific goal of the Solar-B mission is to observe how changes in the photosphericmagnetic field propagate through the different higher layers of the solar atmosphere.
Achievement of this goal requires continuous, simultaneous observations, of specificsolar features, by all three instruments.
The Solar-B mission contributes to NASA’s strategic objective “to explore the
Sun-Earth system to understand the Sun and its effects on Earth” and to two of threeobjectives in the STP Program:•To describe the system behavior of the magnetic variable star, our Sun, and its

interaction with the entire solar system; and,•To understand the critical physics that link the Sun, Earth, and theinterstellar medium.

2005/09/23

1-4

Version 0.99C

The Outline of Solar-B MO&DA

The SOT and its focal plane instruments provide quantitative measurements of theSun’s full vector magnetic field on spatial scales of 200 to 300 km over a field of viewlarge enough to contain small active regions. The instrument fields of view,
sensitivities, and cadence allow changes in the Sun’s magnetic energy to be related toboth steady state (coronal heating) and transient (flares, coronal mass ejections)changes in the solar atmosphere.
The SOT is a diffraction-limited Gregorian telescope with a 0.5 meter aperture. The
distance between the primary and secondary vertices is 1.5 meters. The field of view isgreater than 400 arcsec in diameter. The wavelength band observed is between 380
nanometers (nm) and 660 nm.
SOT’s instrument package, referred to as the Focal Plane Package (FPP), collects highresolution spectra and images of the photosphere and chromosphere, some with fullpolarization analysis. Processing on-board and on the ground makes magnetograms,
Dopplergrams, and accurate vector magnetic measurements from these data products.
The FPP contains four distinct sub-systems:•

A broadband filter imager (BFI)•

A narrowband filter imager (NFI)•

A spectro-polarimeter (SP)•A Correlation Tracker (CT)EIS records extreme ultraviolet (EUV) spectra and images of the multi-thermal (10^5
to 10^7 K) plasmas in the quiet Sun, active regions, and flares at high spectral, spatial,
and temporal scales characteristic of these processes
The EIS instrument incorporates two major optical components:•

A multi-layer coated normal incidence off-axis telescope with high spatial

resolution; and,•A

multi-layer

coated,normal-incidence,

toroidalgrating,

stigmatic

spectrometer covering two diagnostically important EUV wavelength bands centeredon 19.50 nm and 27.00 nm.
XRT provides quantitative measurements of the emissions from the high temperature(10^6 – 10^7 K) component of the solar corona as a function of time and position. It is a
Wolter I grazing incidence telescope similar to that used on Yohkoh, with a large
format back-illuminated CCD. Pixels are 1 arcsecond and field of view is slightly larger
than the full solar disk when pointed at disk center.

With 9 analysis filters, thetelescope covers a broad range of temperatures, with low temperature response

2005/09/23

1-5

Version 0.99C

The Outline of Solar-B MO&DA

enhanced compared with Yohkoh/SXT.

It can also take visible G-band images forcoalignment with SOT and EIS.
ISAS provides the overall mission management, mission operations, the spacecraft, thelaunch vehicle, and the SOT. In addition, the ISAS provides the tip-tilt mirror assembly,
which is an integral part of the SOT Image Stabilization System. The ISAS also
provides the charge-coupled device (CCD) and its associated electronics for the XRTcamera.
NASA is providing all of the FPP and the polarization modulator wheel located between
the SOT and the FPP. NASA will provide the opto-mechanical elements of the XRT
components including the X-ray and visible light optics, filter wheel and filters, front
door, camera focus mechanism, shutter, telescope structure, and integration of the
instrument components into the XRT. NASA will provide the optical components for
the EIS including the primary mirror assembly, the diffraction grating and grating slit
sub-assemblies, and the front filters, spectrograph entrance filter, and the mechanism
driver electronics.

In addition, NASA supports participation in systems-level

integration, mission operations preparations, mission operations, and data analysis.
PPARC is providing the major elements of the EIS including the spectrometer
structure and thermal control system, the CCD detector system and radiator, theinstrument control unit electronics, and the front filter enclosure. PPARC will integrate
the NASA provided EIS components into the EIS instrument.
The spacecraft, designed and built by ISAS, provides structural interfaces, power,
attitude control and pointing, data storage and transmission capability, andenvironmental protection services to the science instruments. It is designed for athree-year baseline mission, with a goal of an extended mission for many years beyond
this.
The spacecraft provides an offset pointing capability that allows the optical axis of the
SOT to be pointed at any point on the Sun, solar limb, and/or at any point less than orequal to 1 arc-minute above the solar limb.
Data storage and transmission/downlink are managed centrally by the spacecraft. The
Mission Data Processor computer controls the science observing functions of the FPP
and XRT and passes commands and data to EIS, which has its own internal
Instrument Control Unit.
The Solar-B spacecraft will be delivered to orbit by a Japanese launch vehicle from the2005/09/23

1-6

Version 0.99C

The Outline of Solar-B MO&DA

Kagoshima Space Center, Japan. The planned launch date is September 2006. The
Solar-B orbit is an approximately 600 km circular Sun-synchronous orbit with anominal 97 degree inclination.
Spacecraft control, data collection, and tracking are under the control of the ISAS andwill be conducted from the ISAS facility in Sagamihara, Japan. NASA will provide
resources and/or NASA assets to assist in early launch operations tracking and science
data downlink support. The European Space Agency will provide 15 additional
downlinks per day using a ground station at Svalbard, Norway. This, support will
dramatically increase the scientific return from Solar-B, helping to ensure that theSolar-B scientific goals can be achieved.

1.2 Purpose of this Document
The purpose of this document is to provide the outline of Mission Operation and Data
Analysis for Solar-B. The following three topics are described in the document.

¨

Science operations of the Solar-B satellite and its instruments¨

Scheduling and submission of observation plans¨

Data policy, archiving, distribution and analysis of Solar-B data

The document is based on the following documents and presentations.

¨

Mission Operations and Data Analysis (@FPP-CDR [Tarbell])¨

Science Implementation(XRT: SAO Solar-B Homepage "http://hea-www.harvard.edu/solarb/")¨

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)(EIS:MSSLHomepage“http://www/mssl/ucl/ac.uk/Solar-B/eis_planning.htm)¨

Methods for Visualizing Solar Data (@3rd Solar-B science meeting [Berger])¨

Minutes/résumés of the 1st Solar-B MO&DA Meeting @ Lockheed 2002/02/20-21¨

Minutes/résumés of the 2nd Solar-B MO&DA Meeting @ SAO 2002/02/17-19¨

Etc…do we really need these? It would be better to list living documents withsome relevance, such as the ISAS Interim Reports, EICA’s, etc.

2005/09/23

1-7

Version 0.99C

The Outline of Solar-B MO&DA

2005/09/23

1-8

Version 0.99C

The Outline of Solar-B MO&DA

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

Principles of Solar-B Science Operations
Basic principles of the operation of the Solar-B satellite and its instruments are
summarized as follows. The Solar-B team consists of the individual instrument teams,
the Project Scientists, and their collaborators participating in science operations.
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.
Items to be coordinated are¨

Target of the observation¨

Usage of the data recorderB) In order to maximize the scientific returns from Solar-B observations, the Solar-Bteam, when appropriate, shall cooperate with other satellites and ground-based
observatories.
C) The “observation plan” (i.e., observation tables and commands) of each instrument
should be prepared independently, once the coordination is agreed.
D) To ensure effective operations, initially all operations will be conducted from ISAS
and KSC. After operations become routine, team members will have the option toparticipate from remote sites.

Certain operations may be performed effectively

from remote sites, allowing team members located in Japan, US, UK, and Norway
to devote a greater part of their time to scientific collaborations.
Along with the basic principles, the following scheme of Solar-B science operations will
be implemented:
I.

Duties and contributions to the Solar-B science operation are equally shared
among Japan, US, and UK scientists in the Solar-B teamII.

Chief observers (SOT_CO, XRT_CO, EIS_CO) are assigned for scientificoperation planning and health-check of the instruments. In the early phases ofthe mission, chief observers will work at the ISAS/SAGAMIHARA campus,
Japan.

III.

Initially there will be a separate Chief Planner dedicated to coordination among
the instruments and satellite science operations planning. The instrument teams

2005/09/23

2.1-9

Version 0.99C

The Outline of Solar-B MO&DA

are responsible for providing a Chief Planner on a rotating basis.
IV.

Scientists are involved in the daily real-time operations of Solar-B. Since thereal-time operations team (engineers of the contractors) at KSC cannot speak
English, Japanese-speaking scientists are assigned for the persons in charge ofthe real-time operation. It is assumed that one of the chief observers is aJapanese speaking scientist.

1. The operation system of Solar-B
2.1.1. The personnel of Solar-B daily operation
The following positions are needed for the daily Solar-B operations.

¨

Chief Observers

Ø(3)

SOT Chief Observer[SOT_CO]XRT Chief Observer[XRT_CO]EIS Chief Observer[EIS_CO]One person will be nominated for each instrument in shifts of at least one
week.

Ø

Each instrument team shall establish their staffing schedule.

ØInitially COs will work at ISAS, but once operations have become routine may
be located remotely.

ØCOs plan the observations, including preparation of the observation tables andcommand plans for the instrument.

Ø

Check the instrument status at least daily.

ØContribute to collecting and analyzing calibration data.

Ø

Review the contents (image quality etc) of the level-0 files generated by thereformatter (See also the roles of Solar-B database coordinator).

ØJapan, US and UK scientists and/or graduate students (who have experienceas the chief observer or the supporter) serve as chief observers. One of thethree chief observers speaks Japanese.

¨

Solar-B Chief Planner [CP] (1 or 0)ØSolar-B Chief Planner (CP) is a scientist provided by the instrument teams in
shifts of at least a week. Initially, this person will be different from the chief

2005/09/23

2.1.1-10

Version 0.99C

The Outline of Solar-B MO&DA

observer of the instrument.
Ø

CP works at ISAS Sagamihara campus.

Ø

Main tasks of the CP are as follows:²

To coordinate the observing plans among the telescopes and resolves
conflicts when necessary,²

To do routine works with automated software for making the sequence ofsatellite commands needed for nominal science observing, details of which
are described later, and²

To compile all the submitted commanding plans on the ISACS-PLN
system and finalize the real-time command plan for USC operations and
OP/OG (onboard command sequence).

ØCoordination of observing plans (1)One of the important coordination is the usage of data recorder (DR) among
three instruments. After the DR usage plan is defined in weekly and daily
meetings, the CP will perform the following routine tasks:²

To provide DR usage planning information to the COs,²

To check whether the observations planned by the COs will not cause
overflows in DR, and²
ØTo generate the sequence of commands for downlinks.

Coordination of observing plans (2)Satellite pointing schedule (selection of targets for observing) is defined inweekly and daily meetings. The CP will operate AOCS 1 -team provided
software and make commands for routine pointing to change the targets ofinterest.

ØRoutine works
The CP performs routine works with AOCS-team provided software to prepare
satellite commands needed for nominal science observing, including updatingof orbital elements and parameters for AOCS-related timers and so on.

ØFinalizing real-time commanding plan and OP/OG²

After receiving the commands and observation tables from the COs, theCP complies all the received commands and tables and generates thereal-time commanding plan for USC contacts and OP/OG plan. TheISACS-PLN system is used for this automated process.

²

The CP reviews the generated OP/OG and real-time commanding planwith graphical time-chart of major commands (pointing, downlink, eclipse,

1 Attitude and Orbital Control System

2005/09/23

2.1.1-11

Version 0.99C

The Outline of Solar-B MO&DA

etc).
²

Finally, the CP submits the OP/OG and real-time commanding plan toreal-time TOHBAN for approval.

¨

Persons responsible for the real-time operation [Real-Time TOHBAN] (3)ØReal-Time TOHBAN are the conductors of the real-time operations

Ø

Stay at SAGAMIHARA campus after the initial phase.

ØJapan (ISAS/JAXA) basically takes responsible for real-time operations.
However, due to limited human resource in Japan, ISAS/JAXA’s latest
baseline during nominal science observing period after initial phase is asfollows. (See also Section 2.1.2):²

The uploading of observation plans (OP/OG, observation tables) is
performed in the evening passes, whereas the morning passes arebasically used for data downlinks only.

²

One operation team works for the morning passes and another team forthe evening passes. From the Solar-B project side, one person participatesin the morning operations and two persons including at least one scientist
or graduate student in the evening operations.

Ø

Real-time TOHBANs checks the status of the satellite and instruments in realtime at AOS (acquisition of signal) and LOS (loss of signal).
²

If anomaly is found by the status check, the real-time TOHBAN can issue
pre-determined commands to give the instrument a safe condition, by
following operation manual.

²

The recovery operation of the instrument will be scheduled at evening
operations, if it is not urgent.

¨A supporter of the Solar-B Chief Planner [Supporter](0 or 1)ØServes in shifts of one week, if necessary.

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

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 tasks need
continuity, a specific person will be assigned for a long period of time.

¨

The Ground-Base Contacts Coordinator [GCC]

2005/09/23

2.1.1-12(1)

Version 0.99C

The Outline of Solar-B MO&DAØ

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

Ø

Schedules the ground-based contacts (KSC, ESA, and NASA ground stations)using the orbital elements supplied by NASDA.

¨

ØChecks the data transfer from the ground stations.

Ø

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

Scientific Schedule Coordinators [SSC]Ø

(6 [TBD])

Consist of senior scientists designated by each of the instrument PIs, who willreside at their home institutions.

Ø

Coordinate the long-term (monthly) observation schedule and the proposals.

ØWill be contact persons for proposal submission. If necessary, they will be also
consultants for proposal preparation, and¨ØWill assign a member of the instrument teams consulted on the proposal.

ØManage the rotation of the chief planners among the instrument teams.

Solar-B Database Coordinator and his team [SDC](1)

Ø

SDC leads the data and analysis portion of the Solar-B project.

Ø

SDC manages his team at ISAS/JAXA, which includes computer systemadministrator and some engineers for maintaining databases and checking theprocess of Level-0 reformatter.

Ø

SDC and his team will take the following tasks:¨

To create and maintain the Solar-B database system¨To maintain the data archive and analysis system of Solar-B at ISAS¨

To administrate the SOLAR-B computer system at ISAS¨

To check the progress of the Level-0 reformat process. Since he checks
only whether the reformat process is running without anomalies, each CO
shall review the contents (image quality) of the Level-0 files.

¨

When he finds anomaly on the Level-0 reformatter process, he identifies
the source of the anomaly and reports it to the reformatter’s maker in
instrument team if it is in the reformatter. The reformatter’s maker in
instrument team shall resolve the problem remotely.

¨

To oversee the Level-0 file registration process to DARTS system.

During the initial phase of the Solar-B operation (until about 3 months after the
Solar-B launch), a special setup of operation could be requested. In addition to thedaily operation setup as described above, additional persons (satellite and instrument

2005/09/23

2.1.1-13

Version 0.99C

The Outline of Solar-B MO&DA

experts) might have to participate in the daily operations as described below.

¨

SOT, XRT, EIS Engineering Advisors(3)ØWill be assigned at minimum one person for each instrument, andØ

Will be staying at ISAS-SAGAMIHARA/Japan during the initial phase.

ØWill be responsible 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 establishingstandard procedures for instrument calibrations.

¨

SOT, XRT, EIS Software coordinators(3)ØWill set up the system and environment for data archives and data analysis:²

Installing and checking the instrument-specific database software²

Making and installing the data analysis software

Throughout the mission, specialized engineering support for satellite operations will
occasionally be needed to handle such things as orbital maneuvers and momentum
management, thermal and power engineering during eclipse season, lunar occultions,safehold recoveries, and other spacecraft contingency responses.
spacecraft contractors will be responsible for these activities.

2005/09/23

2.1.1-14

ISAS/JAXA andVersion 0.99C

The Outline of Solar-B MO&DA

2.1.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 Coordinator,
Database Coordinator, 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 Schedule Coordinator (JAPAN),
Supporter, Ground-base Contacts Coordinator,
Chief Planner
Aims : Status review of satellite, instruments for the previous
week, Selection of some target regions
Review of observation plans for up-coming week
(Pointing, Table uploading schedule)<Every Morning (10:30 JST [TDB]) Meeting @ ISAS>
Participants : Chief Observers, Supporter, Chief Planner
Ground-base Contacts Coordinator
Aims : Status review of telescopes andsatellites for the previous day.
Allotment of the data recorder to telescopes
Final decision of the target region (Pointing)Decision on the plan for real-time operations

Operation Planning@ SSOCReal Time Operation @ KSC

Solar-B Observation
Solar-B/Satellite & PI
Health Check System

Data Reformat System

Solar-B
Database System

Scientists

2005/09/23

2.1.2-15

Version 0.99C

The Outline of Solar-B MO&DA

The w orkflow of S olar-B m ission operation
Solar-B C hief P lanner(O ne of C O s and Supporter)

SO T,XR T,EIS C hief O bservers

G round-base C ontacts C oordinator

S cientific S chedule
C oordinator
The plans andproposals of
O bservations< M onthly O peration M eeting >O rbitalElem ents
(P relim inary)

Schedulingw ith groundbase stations

G round-base
C ontacts Schedule

P redict
Environm entsof thesatellites

The m onthly plansof observations

C alculate
A verage
D ow nlink

M ake the plan ofO bservations(If there are not any
proposals and plans)Satellite's
Environm ents D ata(SA A ,N ight,etc.)

A verage D ow nlink
for Solar-B<W eekly O peration M eeting>O rbitalElem ents
(Finalversion)

Scheduling w ith
ground-basestations

G round-base
C ontacts Schedule(Final)P redict
Environm ents ofthe satellite(For IS A C -P LN )The w eekly plan of
the observations
C alculate
A verage
D ow nlink

Satellite's
Environm ents D ata(SA A ,N ight,etc.)

A verage D ow nlink
for Solar-B (Final)

C om pile theC ontacts
S chedule for
IS A C -P LN

G round-base
C ontacts Schedule(For ISA C -P LN )<D aily O peration M eeting>

M ake theplan ofR ealTim e
O perations

M ake theplan ofpointing

C om pile
the plan of
R ealTim e
O perations

M ake thecom m ads
for pointing

The com m and plansof real-tim e
operations

P ointing C om m ands

M ake theobservingtablesC om pile theobservingtablesThe observing
tablesM ake thecom m andplans for
instrum ents

Exam pleC om pile thecom m andplan for
instrum ents

D ata or D ocum ent

C heck theoutput data
rate from
instrum ents

The com m and planfor instrum ents
D ata
(ISA C -P LN
Form at [binary])

ISA C -P LN System

OP

D ata
(ISA C -P LN
Form at [XM L])

The com m and plansof real-tim e
operations

O bserving Tables

C om puter
P rogram

C om puter
P rogram s(O utput data
are IS A C -P LN
form at data)

C heck O P &com m ands
H andw ork

Send to KSC (by ISA C -P LN System )2005/09/23

2.1.2-16

Version 0.99C

The Outline of Solar-B MO&DA[The nominal timetime-line of SOLARSOLAR-B Daily Operation]
Time
(JST)
Day 1
10:30

Tasks for Day 1

Tasks for Day 2< Dead line of the observation tables andcommanding plan for instruments of Day 1>

10:30 <Daily Meeting>•Review statuses of the satellite and instruments ofthe previous day of Day 1.

• CP provide DR usage planning information of Day 2
to the COs.
• Confirm the observation plans, the allocation of DR,
and the pointing schedule of Day 2

11:00•The CP checks whether the observations plannedby the COs will not cause overflows in DR.
• The CP generates the sequence of commands fordownlinks.
•The CP complies all the received commands andtables and generates the real-time commanding
plan for USC contacts and OP/OG plan of Day1.
•The CP reviews the generated OP/OG and realtime commanding plan with graphical time-chart ofmajor commands (pointing, downlink, eclipse, etc).

15:00• CP and Real-Time TOHBAN (Evening team)
open the small meeting and discuss the operationof Day 1.

15:30• Rea-time TOHBAN (Evening team) start toprepare for the evening real-time operation.

17:??

• COs start to create the observation tables andcommanding plans for Day 2•The CP operates AOCS-team provided software andmakes commands for routine pointing to change thetargets of interest.
•The CP performs routine works with AOCS-teamprovided software to prepare satellite commands
needed for nominal science observing, including
updating of orbital elements and parameters for
AOCS-related timers and so on.

<Evening Passes at KSC> (2 or 1 passes)• Real-Time TOHBAN upload new OP and OG atfirst pass of Day 1.
• Real-Time TOHBAN also upload the observing
tables of Day 1.
• Real-Time TOHBAN check the status ofsatellites and instruments, simply.

Day 2
05:??

<Morning Passes at KSC> (2 or 1 passes)• The morning passes are basically used for data
downlinks, only. (They do not upload OP, OG and tables.)• If anomaly is found by the status check, the realtime TOHBAN can issue pre-determinedcommands to give the instrument a safe condition,
by following operation manual.

09:00• CO and CP check the status of the instruments
and the satellite using the data that are downlinked
in the morning passes at USC.
< Dead line of the observation tables andcommanding plan for instruments of Day 2>

10:30

l

Monthly Meeting [Tele-conference]ØParticipants: Project Manager, Principal Investigators, Science Scheduling
Coordinators, Chief Observers, Database Coordinator

2005/09/23

2.1.2-17

Version 0.99C

The Outline of Solar-B MO&DA

Ø

Review status of the satellite, instruments and databaseØ

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 the observations of the next month, and make the priority list of theobservations.

l

Weekly Meeting [@ISAS every Friday after the daily meeting]ØParticipants: Project Manager, Chief Observers, Chief Planner, Supporter,
Ground-base Contacts Coordinator, Science Scheduling Coordinator(at least one)²Ø

Remote participants by telecon

Review of the satellite and instruments status in the next week, starting
MondayØ

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

Review and decisions on the schedule of observation plans for next week
(nearly final)Ø

Selection of some target regions and decisions on the pointing maneuverschedule of next week (nearly final)ØlAllocation of the data recorder (DR) for each instrument (nearly final)

Daily Meeting [@ISAS every weekday (Monday - Saturday) morning]ØParticipants: Chief Planner, Supporter, Chief Observers, Ground-baseContacts
CoordinatorØRemote participants by telecon

Ø

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.

Ø

If there are some changes in the schedule of the ground-base contacts,
reallocate the data recorder for each instrument.

2005/09/23

2.1.2-18

Version 0.99C

The Outline of Solar-B MO&DAl

The deadline for input to the next day’s operation plan (commands, observationtables, etc.) to the Solar-B Chief Planner is 10:30 JST each day.

l

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 real-time TOHBANs
make the final check of the operation plan in the evening. As a goal for operations
after the initial phase, the plan might be uplinked during evening USC passes, toreduce the time delay between preparation and execution of the plan, to be more
responsive to changing solar conditions.

l

In nominal operations, the plans are approved on a daily basis. However, in casean urgent operation change is requested as the result of checking the data
downlinked during the morning passes, the planners should make the revised planfor the evening real-time operations as soon as possible.

Scientists resident at ISAS from US and UK
For the first year of operations, the EIS team expects to provide three scientists at
ISAS. NRL and MSSL will each provide one scientist who will reside in Japan. In
addition, EIS team members from the UK, Norway, and the US will rotate to ISAS forroughly three weeks at a time to provide a third person to participate in EIS operations
and data
analysis. When foreign visitors are not available, Japanese EIS scientists will provide
the additional manpower to keep the staffing at the desired level. Staffing at the 3
person-year/year level will make it possible for each person to participate effectively inboth operations and data analysis.
The US FPP team intends to provide one scientist who will reside in Japan full-time(apart from occasional visits back to the US). This person will divide his/her time
between mission operations and science data analysis approximately equally. In
addition, the FPP team will always have one scientist visiting Japan on a rotating basis
in shifts of approximately 2 weeks. During the first year, there will usually be a second
scientist visiting Japan for operational training purposes. US FPP scientists will also
visit Japan for purely scientific collaborations apart from mission operations, forperiods of a few weeks to a few months at a time.

2005/09/23

2.1.2-19

Version 0.99C

The Outline of Solar-B MO&DA

The US XRT team intends to provide the following persons in Japan to support Solar-B
science operations during the first year of operations:•

Full time resident
An SAO scientist will be resident in Japan for the first year of operations. We

will rotate this person back to SAO for 1 month periods every 3 months. The US XRTteam will provide a scientist to cover each month that the resident scientist is awayfrom Japan.
•

Half time resident
The US XRT team will rotate scientists through Japan for periods of 3 week

(or longer). The combined coverage of these scientists will be for 1/2 year during thefirst year of operations.
In the initial phase of the solar-B operation, additional scientists and/or engineers fromeach instrument team need to be available at ISAS for commissioning and contingency
operations.

Software required for daily operations
In order to reduce the burden of operations and increase the time for scientific planning,
all software for the operation is expected to provide simple, automated and user
friendly tools for local and remote operation planning. In the following sections, we
describe the software for the operation of the satellite and instruments.

2.1.3. ISACS-PLN(TBS)

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

¨

Prediction of the satellite environments
This software predicts the timing of ground station contacts, SAA, HLZ, andnight periods of the satellite, calculating from the orbital elements. The software
produces the graphical time chart and the list of events. These are very useful

2005/09/23

2.1.4-20

Version 0.99C

The Outline of Solar-B MO&DA

not only for planning of observations but also for troubleshooting of thespacecraft. In ISAS, the software is called “AOSLOS/DP-10”.

¨•

Japan team takes responsibility for the developments.

•

USER

: Chief Planner

•

INPUT

: Orbital Elements•

OUTPUT: SoE (SAA, HLZ, Night, Eclipse, etc.)

Estimating the downlink data size
After coordinating with the ground stations by Ground-base Contacts
Coordinator, the information on the station contacts of Solar-B is provided withthis software. The software estimates the volume of downlink data using thecontacts schedule. The estimated data size is used for coordinating the usage ofthe data recorder (DR).
•Japan team takes responsibility for the developments.

•

USER

: Chief Planner

•

INPUT

: Orbital Elements•

OUTPUT: List of Ground-base Contacts
SoE (Ground-base Contacts Schedule)
List of the Average Downlink Rate¨

Support tools for creating OP, OG and the real-time commanding plans
In the Solar-B project, the ISAC-PLN software package is available 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 station contacts, SAA and satellite nights. The support software
creates the event lists from the AOSLOS data and the plan of observations, andtherefore, it has an interface to ISAC-PLN.

¨•

Japan team takes responsibility for the developments

•

USER

: Chief Planner

•

INPUT

: Observation Plans•

OUTPUT: SoE and Macros for Special Operations

Supporting tool for checking OP and the real-time commanding plans
ISAC-PLN creates OP and the real-time command plans input from Chief Planner
and Chief Observers. The software makes the graphical time-line charts, taking

2005/09/23

2.1.4-21

Version 0.99C

The Outline of Solar-B MO&DA

OP, the real-time operation plans and the prediction of the data output rate fromeach instrument into account. The time-line also indicates the stored data volumeof the data recorder.

¨•

Japan team takes responsibility for the development

•

USER

: Chief Planner

•

INPUT

: OP (or SoE/Macros)•

OUTPUT: Graphical Time-chart of Operations

Making commands required for the satellite pointing
The chief observers for all 3 instruments can request the change of spacecraft
pointing. The satellite, therefore, may be able to change the pointing several
times a day. Since the parameters for commanding spacecraft maneuvers arecomplicated, and miss-commanding may lead to serious consequences, thesoftware should calculate the parameters for S/C maneuvers from the solar
coordinates of the target regions as inputs.
Japan team and the contractor for AOCS (Attitude Orbital Control System)•take responsibility for development•

USER: Chief Planner

•

INPUT

: Observation Plans•

OUTPUT: SoE and Macros for the pointing
List of the pointing parameters¨

Checking the usage of DR and Making the commands for the limitation oftelemetry
After making the commands and the observation tables by COs, CP checks theusage of DR based on the data output rates from all instruments and makes the
MDP commands for the limitation of telemetry. The software supports the checkand makes the commands for the limitation of telemetry.
•

Japan team takes responsibility for the developments.

•

USER

: Chief Planner

•

INPUT

: List of Ground-base Contacts
The data output rates calculated by COs.

•OUTPUT: SoE and/or Macros for the limitation of telemetry
Graphical chart of the data size stored in DR¨

Health check reformat software

2005/09/23

2.1.4-22

Version 0.99C

The Outline of Solar-B MO&DA

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 has already been developed during integration and test.

¨•Japan team take responsibility for the development

•

USER

: REAL-TIME TOHBAN, Chief Observer, etc.

•

INPUT

: raw-telemetry data (from SIRIUS)•

OUTPUT: Health Check data

Health check and monitoring system for the Satellite
During the real-time operations at USC, the REAL-TIME TOHBAN checks thehealth of Solar-B using the health check and monitoring systems. The system isused for checking the fundamental status of Solar-B, for example, battery
voltages, temperatures, etc. The company that develops the telemetry systemprovides the software.
•

Japan team and S/C contractor (MELCO) take responsibility for thedevelopments

•

USER

: REAL-TIME TOHBAN

•

INPUT

: raw-telemetry data

2.1.5. Software for the operation of the instruments
Chief observers need tools for planning observations of the instruments. The tools
assist chief observers in planning the command sequences and observing tables, which
extract scientific returns as much as possible from the observations. Software must be
available to choose instrument setup parameters and to simulate the observation. The
user interface software must operate consistently from both ISAS and remote locations.
A validation process will be in place to ensure that observation plans do not violate
health and safety constraints of the instruments.

¨

Solar-B planning and operations database
Observation plans used in the planned and/or performed observations must bearchived by name, identification number or scientific objective, for ease ofrerunning and/or modifying. Each instrument team will design and develop its
own database.
•

Instrument teams take responsibility for the databases

•

USER

2005/09/23: Chief Observer

2.1.5-23

Version 0.99C

The Outline of Solar-B MO&DA

¨

•

INPUT

: Observation Plan•OUTPUT: Database tables

Software for creating the observing tables
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.

¨•

Instrument teams take responsibility for the tool

•

USER

: Chief Observer

•

INPUT

: Observation Plan•OUTPUT: Observing Table and Solar-B database

Instrument timeline command software
When an instrument needs to command the MDP (e.g., to stop the observation

when the satellite changes the pointing), the command plans may include many
real-time commands, coordinated with satellite activities such as pointing changes ortelemetry downlinks. Hence, this software needs to refer the Chief Planner’s command
plans and the event lists. The software also has an interface with ISAC-PLN.
•

Instrument teams take responsibility for the tool

•

USER

: Chief Observer

•

INPUT

: Observation Plan•OUTPUT: SoE and/or Macros for Instrument Operation, Solar-B

database¨

Observation simulation software for estimating the output data rate and size
This software simulates the observations from the observing tables andinstrumentcommandtimelineandestimates

the

data

outputbetweenthetheground-station contacts. The Chief Observer checks that the estimated data size does
not exceed the allocated size of DR for the instrument.
•

Instrument teams take responsibility for the tool

•

USER

: Chief Observer

•

INPUT

: Observing Table

2005/09/23

2.1.5-24

Version 0.99C

The Outline of Solar-B MO&DA•¨

OUTPUT: Displays of data output rate and the ASCII text file

Health check and monitoring system for the instruments
During the real-time operations at USC, the REAL-TIME TOHBANs check thehealth of the instruments using this system. The system displays the status of the
instruments and real-time images. The data distribution system at USC is as sameas that at ISAS/SAGAMIHARA, which was used during the Proto-Model test, andwill be during the Flight-Model test. We will use the same software developed in
the PM and FM tests, and in the real-time operations at USC with minor revisions.

¨•

Instruments team take responsibility for the tool

•

USER

: REAL-TIME TOHBANs, Chief Observer

•

INPUT

: Health Check data•

OUTPUT:real time display

Health and status monitoring for the instruments
The health and status of each instrument is also monitored frequently (though not
in real time) by team members at ISAS, their home institutions or other remotesites. For this purpose, web displays of status information are automatically madefrom the reformatted status information. Sample images from the mission science
data may also included in these displays as they become available.
•

Instruments team take responsibility for the tool

•

USER

: Chief Observer, Instrument teams

•

INPUT

: Instrument Status data•

OUTPUT:web-based status reports

2.1.6. Special software for the instruments¨

Making MDP/SOT Doppler parameters
Since the wavelength setups of the spectropolarimeter and the narrowband
tunable filter of SOT are affected by the orbital motion of the satellite. MDP
accomMO&DAtes an on board software to calculate the Doppler velocity based on
the spacecraft orbital elements uplinked in a regular time interval.
•

SOT team take responsibility for the tool

•

USER

: Chief Observer of SOT

•

INPUT

: Observation Plan, Orbital Elements, etc.

•

OUTPUT: Memory images of upload parameters

2005/09/23

2.1.6-25

Version 0.99C

The Outline of Solar-B MO&DA

2.1.7. The summary table of the Solar-B operation tools
Tools

Maker

User

Prediction of satellite environments

ISAS

CP

Estimating the downlink data size

ISAS

GCC

ISAS

CP

ISAS

CP
RT

ISAS
AOCS

CP

ISAS

CP

Support tool for creating OP/OG andreal-time commanding plan
Support tool for checking OP and thereal-time commanding plan
Making commands required for thesatellite pointing
Checking
DR and Making the
TLM_LMT commands
Reformatter for Health Check Data
(CCSDS > IDL-readable format)
Health check system for spacecraft
systemCreating the observation table
Support tool for commanding plan for
the instrument
Estimate the output data size from the
prepared observing table
Real time health check system for the
instrument

ISAS
MELCO
PI

CO
KSC
KSC
CP
CO

PI

CO

PI

CO

ISAS

PI

Status Web Pages for remote checking

PI

Making SOT/MDP Doppler parameters

SOT

2005/09/23

2.1.7-26

CO
KSC
Inst.
Team
CO

Input

OutputOrb. Elem.

SoE
SoE
Orb. Elem.
List
Obs. plan
SoE
Macro
SoE
Graphical
OP
Time-chart
SoE
Obs. planMacrodata rates SoE/Macrofiles
Time-chart
HealthRaw-telem.
Check data
(Display to
Raw-telem.
monitor)Obs. planObs. table
SoE
Obs. plan
Macro
Time-chart
Obs. table
ASCII file
HealthDisplay to
Check data monitor
Web Pages
Status Data
Orb. Elem.
Obs. plan

Parameter

Version 0.99C

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 policy
ØThe Solar-B team recognizes the importance of rapid dissemination of theobservatory’s data sets to the worldwide solar physics community for both thesuccess of the Solar-B mission and the benefit of solar physics. To this end, theSolar-B team will make all of its data available without restriction within six
months from the date of observation. Scientists collaborating with the Solar-B
team and Guest Investigators have unrestricted access to the data.

i.

Solar-B will be operated according to a pre-determined plan during theinitial phase of approximately the first 3 months of solar observations
after commissioning. Each of the initial phase observation plans shall be
reviewed and prioritized by the Solar-B SWG.

ii.

Observations starting after the initial phase will consist of the PI
baseline science programs and proposed observations from the wider
community.

iii.

Proposed observations will be submitted to the scientific schedulingcoordinators (see 2.2.1).

iv.

Data-use policy shall give a high priority to graduate students pursuing
PhD research. Users accessing the data catalog or search engine shall be
required to acknowledge a list of active PhD topics. Thesis advisors are
responsible for ensuring that their students’ PhD theses are represented
on the list, and that these thesis topics are not unreasonably broad or
extended. The list of PhD topics will be available from the homepage ofSolar-B. Disputes or conflicts will be addressed by the SSCs.

3.2. Baseline programs and proposed observations
Observations after the initial phase will consist of baseline program and proposed
observations that fall outside of the baseline. The baseline programs will be standard

2005/09/23

3.2-27

Version 0.99C

The Outline of Solar-B MO&DA

observations performed by the Solar-B team through its mission life. Baseline
programs are designed to address the fundamental science goals of the Solar-B mission.
Proposed observations will be executed based on the proposals submitted to thescientific scheduling coordinators.

Joint observations with other satellites andground-based observatories are encouraged.

3.2.1. Proposal requirementslAll proposals shall be in English.

l

In order to receive proposals from scientists and students inside and outside theSolar-B team, the Scientific Schedule Coordinators will be assigned as contact
points and also as consultants for the proposals.

lProposals will not be treated as confidential information, since they may be
discussed bby the entire Solar-B team.

l

Proposals will be discussed at monthly operation meetings. Hence, a standard
deadline for submission will be set before the monthly operation meeting in which
the particular operation will be discussed for the first time, typically 3 months
before the observations will take place.

l

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

3.2.2. Role of Scientific Schedule Coordinatorsl

The SSCs are the contact points and consultants for preparation of observation
proposals. Using the received proposals and the baseline programs, they prepare a
draft monthly schedule of observations presented in the Solar-B monthly operation
meeting.

lEach instrument team shall have SSCs, one appointed by each PI, to whom
proposals should be sent.

l

SSCs will be authorized to select or reject proposal observations, and to draft themonthly observation schedules. Proposals may be rejected if, for example, the sameobservation plans are already proposed, the essential parts of the proposed plansoverlap with a PhD thesis in progress,

the science is not compelling, or the

proposed observations exceed instrument capabilities or violate health and safety
constraints..

2005/09/23

3.2.2-28

Version 0.99C

The Outline of Solar-B MO&DAlEvery month the SSCs will designate targets of opportunity (if any) and set
priorities for their observation.

3.2.3. Responses to solar activity and coordination with ground-based
observatorieslTarget of Opportunity campaigns can be inserted in the monthly planning.

lProposals for these campaigns should be sent to Science Schedule Coordinators.

lChief Observers and the Chief Planner choose the target in the daily meeting
based on the priority list of observations [see 2.2.2]. They have the discretion tochoose targets of opportunity, when they are included in the monthly plan.

2005/09/23

3.2.3-29

Version 0.99C

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)

The master archive of Solar-B data will be the DARTS system provided by ISAS.

C)Existing analysis tools, such as the SSW or SolarSoft package, will be also usable
for Solar-B data analysis.

D) For health checks of the instruments, the health check system developed forground integration and test will be used.
E)

To ensure efficient data accessibility not only among the Solar-B science teams but
also in the wider solar community, the Solar-B data providing system shall be
designed to be compatible, if possible, with the Virtual Solar Observatory (VSO),
European Grid for Solar Observations (EGSO),UK AstroGrid, CoSEC, 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¨

Status 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 for archiving

2005/09/23

4.2-30Version 0.99C

The Outline of Solar-B MO&DA

In this section, we explain these data levels.

¨

Raw telem etry dataØThey are the data received at KSC and the other ground-based stations. The
format is “CCSDS packet” format.

ØAll raw telemetry data of Solar-B are archived on the “SIRIUS” database, the
ISAS satellites database at the ISAS/SAGAMIHARA campus. ISAS maintainall the data of the ISAS satellites via this database on line.

ØThe “SDTP” protocol (ISAS original protocol) is used to retrieve the data fromthe SIRIUS database.

¨

Health check dataØThe data will be reformatted from raw telemetry to IDL-readable. The data
include not only observational 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.

Ø

The data are decompressed, in case necessary, during the reformatting
process.

ØOne file per instrument is created for each downlink (real-time passes only)

The health check data will be created temporarily and not stored in an archive.

•

Instrument status data
Status data for each instrument will be retrieved from the SIRIUS databaseand reformatted from the raw telemetry into a file format chosen by each instrument.
These status files will be permanently archived at ISAS along with the mission sciencedata.
¨

Level-0 dataØ

Reformatted raw telemetry data file.

ØThe data format of Level-0 is FITS with binary table extension. The format ofLevel-0 data has two types.
A. Standard FITS format (see Figure FITS-1)
The uncompressed image data are written as standard, multi-image
FITS files. The header information for each image are put the binary
table after the primary HDU. The unit of the file is one observable asdefined by each instrument. This is a single image for XRT. For SOT it

2005/09/23

4.2-31Version 0.99C

The Outline of Solar-B MO&DA

consists of all raw images obtained for a specific SOT data product; asingle filter image, or a set of images obtained to create a single
Doppler or magnetogram. SOT and XRT will use the format for Level-0
data.
B.

SOHO/CDS like format (see Figure FITS-2)
The uncompressed data are put the binary table and there are no
image data in primary HDU of FITS. The header information for eachwavelength are put the header of the binary table. The unit of the fileis one raster. EIS will be use the format for Level-0 data.

A: Standard FITS format

B: SOHO/CDS like format

Primary Header

Primary Header

Image Data-----------------------------------------Header : column 1-----------------------------------------Header : column 2------------------------------------------Header : column 3----------------------------------------:

Binary Table Header-----------------2 or 3 dimensions------------------16 bist integer---------------------

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

Figure FITS-1
ØFigure FITS-2

The header is constructed from the telemetry data (e.g. observing time,
exposure time, pixel size, coordinates on the CCD, etc.) and the Solar-B
operation database (Table ID, Table name, Comments from Chief Observer,etc.).

Ø

The Level-0 data may be recompressed using standard lossless compression
schemes (e.g. gzip) to save the data storage volume and network bandwidth.

ØLevel-0 data are not calibrated.

Ø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.

2005/09/23

4.2-32

Version 0.99C

The Outline of Solar-B MO&DA¨

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

Ø

The data are used to derive photon intensity, spectral line wavelength, etc.,
and for attitude determination.

Ø

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 are fully calibrated and have the headers. The header of Level-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 or the same as the Level-0.

ØData users will calibrate the Level-0 data and generate Level-1 data by using
the software provided by the Solar-B team. The Level-1 data generated byusers will not be archived in the Solar-B data providing system.

Ø

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

¨

Level-2 Data

Ø Level-2 data are made from Level-1 data.
Ø One category of Level-2 data is the data in physical units. In the other word thelevel-2 data consist of files such as longitudinal magnetogram, dopplergram,
vector magnetogram, filling factor, B vector, etc.
Ø The level-2 data have the headers that include the Level-1 headers andadditional information about the derivation.
Ø Level-2 data are compressed by loss-less compression methods.
Ø Level-2 data that are standard data products made by the instrument teams.
ØOnly SOT/SP Level-2 data

areprovided by the Solar-B data-providing

system.
Ø Additional Level-2 data volunteered by the team members and submitted to thearchive may also be provided in the same way. For example, Combinations ofSolar-B level - 1 data sets, mission objectives and external (e.g. GOES) data in

2005/09/23

4.2-33

Version 0.99C

The Outline of Solar-B MO&DA

a variety of formats (data bases linked to data archive, 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 othersatellites and ground-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.

2005/09/23

4.2-34

Version 0.99C

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
SystemSatellite
CommonHealth Check
SystemHealthCheck
ReformatReal-Time Operation@ Kagoshima Space Center (KSC)@ Sagamihara Satellite Operation Center (SSOC)

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

Only SOT/SPThe Archiving System of Solar-B Observing Data

2005/09/23

4.3-35

Version 0.99C

The Outline of Solar-B MO&DA

The A rchiving System of Solar-B O bserving D ata
The Solar-B D ata P roviding System for end-users (W eb-based System )Level-0 D ata

C alibration D ata

Level-2 D ata

D ata
A nalysis by
Scientists

Softw are of
C alibration(SSW softw are)

D ata
A nalysis by
Scientists

C alibrated D ata

D ata
A nalysis by
Scientists

U ser's System

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

ExampleComputer
Program

Observation Data

Data orDocuments

Handwork

Database

W eb System(P roviding System )Computer
Program(QL System)

D ata Flow
D ata Flow (by SD TP )D ata Flow(by H TTP or FTP )4.4. The Archiving System of Solar-B data¨

The master database, containing Level-0, 2 2 , Q and Calibration data areconstructed in ISAS.

¨

The Solar-B data archiving system use the resources of the ISAS-DARTS

2 Only vector magnetograms made from SOT/SP data

2005/09/23

4.4-36

Version 0.99C

The Outline of Solar-B MO&DA

system (http://www.darts.isas.ac.jp/). The purpose of the DARTS system is toarchive and distribute space science data obtained via ISAS spacecraft. The
DARTS system is accessible everywhere through web 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, RAL in UK and UoO in Norway.
Level-0 data will be transferred via the internet using lossless compression andmulti-stream transfers to achieve an acceptable transmission rate. We estimate a dailyvolume of approximately 20GB of uncompressed data for SOT and XRT images, thereby
requiring a daily transfer of about 10GB/day of compressed files, or an average rate of~100kB/s. Tests of the link between ISAS and LMSAL consistently displaytransmissions rates of 100kB/s for single ftp streams, thereby just satisfying the
average requirement. Multiple ftp streams increase this rate proportionally andprovide sufficient headroom to maintain the Level-0 data flow.
In the Solar-B project, level-1 data will be not archived or provided by the Solar-B
providing system since the calibration data could be revised during initial phases.
Hence, we transfer only level-0, Q data and Calibration data using the Internet fromJapan to US and UK. The vector magnetograms and associated Level-2 data have to beprovided by the Solar-B team from their home sites, since the calibration and Stokes
parameter inversions are complicated and compute-intensive. These Level-2 data will
be provided from LMSAL (the manufacturer 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.

2005/09/23

4.5-37

Version 0.99C

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
A. Open Item
If we use the Oracle system, we need a full-time Oracle system administrator
at least 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 viewableon screen and optionally printable. The user interface should access Level-Q
data. [EIS team suggestion: The software support IDL GUI interfaces.]

2005/09/23

4.6-38

Version 0.99C

The Outline of Solar-B MO&DA

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

C alibration D ata

Level-2 D ata

Level-Q D ata

O bserving D ata
Filenam es

Solar-B / O bservation D ata A rchive
O bservations
Tables

The com m ents of
C hief O bservers

Filenam es of data
The R elationalD atabase of
Solar-B O bservations

P ointing D ata

O rbital
Environm ents D ata(SA A ,N ight)

Solar-B data
(Level-0,2,C alibration,Level-Q ..)R equests w ith
search keys
(Tim e,P ointing,etc.)

S olar-B D ata P roviding W eb-S erver

Solar-B D ata

Scientists

2005/09/23

4.6-39D ata R equests(Tim e,P ointing,R egion,event)Solar G eophysicalD ata(Flare,N o.of A R )Version 0.99C

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 catalogs of Solar-B observations andLevel-0 data are mirrored daily.

4.7. Software required for Solar-B data processing¨

ISAS will provide first stage of reformatting from raw telemetry to files sorted
by instrument and data type.

¨

Each instrument team will provide secondary reformatters to make Level-0
data products for the science data.

¨

ISAS will provide secondary reformatters to make Level-0 data products forstatus data (based on Astro-F software)¨

Level-1 reformat software (calibration)
Each instrument team provides the software for calibration.

²¨

Level-2 software (derivation of physical quantities)
Each instrument team provides the software for derivations.

²¨

Level-Q reformat software (Images and movies for Quick Look)
The instrument teams make the software²¨

Data-providing and searching system
Provided by TBD¨²

The system is on the web server system and a relational database system.

²

Software packages for management of the relational database are available(e.g., Oracle, mySQL, PostgresSQL, IDL-DB [UIT]).

²

The web interfaces are convenient for users.

²

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

²

The system will be compatible with the Virtual Solar Observatory andEuropean Grid for Solar Observations¨

Data analysis softwareØCommon parts of the data analysis software (ex. I/O of Level-0 and 1) 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 the public.

2005/09/23

4.7-40Version 0.99C

The Outline of Solar-B MO&DAØThe Solar-B team prepares the guidebook for Solar-B data analysis, which
is similar to YAG (Yohkoh Analysis Guide).

2005/09/23

4.7-41Version 0.99C

The Outline of Solar-B MO&DA

5. Acronyms

2005/09/23

5-42

Version 0.99C

The Outline of Solar-B MO&DA

CCD
C C SD S
COC oS E CCPCT
D A R TSDB
D PC M
DR
D VD
EG SO
E IS
E IS _C OESAF IT SFMFP P
GCC
G S FC
GUI
HD
HDU
H LZ
I/O
IA P
ID L
IS A C -P LN
IS A SJA X AJP E GKSC
LM S A L
LO S
M DP
M E LC O
M ODA
M PEG
M S FCM SSL
N A O (J)N ASA
2005/09/23

C harge-C oupled D evice
C onsultative C om itee for S pace D ata S ystem
C hief O bserver
C ollaborative S un E arth C onnector
C hief P lanner of S olar-B
C orrelation T racker
D ata A rchive and T ransm ission S ystem
D ataB ase
D ifferentialP ulse C ode M odulation
D ata R ecorder
D igitalV ideo D isk
E uropean G rid for S olar O bservatories
E xtrem e U ltraviolet Im aging S pectrom eter
C hief O bserver of E IS
E uropean S pace A gency
F lexible Im age T ransport S ystem
F light M odel
F ocalP lane P ackage
G round-B ase C ontact C oordinator
G oddard S pace F light C enter
G raphicalU ser Interface
H ard D isk
H eader and D ata U nit
H igh Latitude Z one
Input / O utput
Instrum ent (Input to the) A ctivity P lan
Interactive D ata Language
Intelligent S atellite C ontrolS oftw are - P lan
Institute of S pace and A stronauticalS cience
Japanese A erospace E xploration A gency
Joint Photographic Experts GroupK agoshim a S pace C enter (R eal-tim e O peration C enter)
Lockheed M artin S olar & A strophysics Lab
Loss of S ignal
M ission D ata P rocessor
M itsubishiE lectric C O rporation
M ission O peration and D ata A nalysis
M oving P icture E xperts G roup
M arshallS pace F light C enter
M ullard S pace S cience Lab
N ationalA stronom icalO bservatory (of Japan)
N ationalA eronautics and S pace A gency
5-43

Version 0.99C

The Outline of Solar-B MO&DA

2005/09/23

5-44