**The Outline of Solar-B**

**Mission Operation & Data Analysis**

Version: 1.00

The Solar-B MO&DA Working Group

2005-11-11

[Change Records]{.underline}

+------------+----------+----------+----------------------------------+
| Issue      | Date     | Authors  | Comments                         |
+------------+----------+----------+----------------------------------+
| Version    | 20       | M.       | Written by Japanese              |
| 0.1        | 01-11-29 | Shimojo  |                                  |
+------------+----------+----------+----------------------------------+
| Version    | 20       | M.       | Written by English               |
| 0.7        | 02-01-18 | Shimojo  |                                  |
|            |          |          |                                  |
|            |          | T.       |                                  |
|            |          | Shimizu  |                                  |
+------------+----------+----------+----------------------------------+
| Version    | 20       | M.       | Added the discussions of 3^rd^   |
| 0.8        | 02-02-11 | Shimojo  | Solar-B science meeting at       |
|            |          |          | Hawaii 2002/01/25-26..           |
+------------+----------+----------+----------------------------------+
| Version    | 20       | M.       | Added the discussion of 1^st^    |
| 0.9        | 02-02-26 | Shimojo  | Solar-B MO&DA meeting at LMSAL   |
|            |          |          | 2002/02/20-21.                   |
|            |          | T.       |                                  |
|            |          | Tarbell  |                                  |
+------------+----------+----------+----------------------------------+
| Version    | 20       | T.       | Editing for clarity, small       |
| 0.95       | 02-07-03 | Tarbell  | additions to Data Policy,        |
|            |          |          | comments about VSO and EGSO      |
+------------+----------+----------+----------------------------------+
| Version    | 20       | T.       | Editing for clarity and change a |
| 0.96       | 02-07-08 | Shimizu  | figure in the section 4.5.       |
|            |          |          |                                  |
|            |          | M.       |                                  |
|            |          | Shimojo  |                                  |
+------------+----------+----------+----------------------------------+
| Version    | 20       | T.       | Editing for clarity              |
| 0.965      | 02-07-14 | Watanabe |                                  |
+------------+----------+----------+----------------------------------+
| Version    | 20       | T.       | Editing for clarity              |
| 0.97       | 02-07-16 | Shimizu  |                                  |
+------------+----------+----------+----------------------------------+
| Version    | 20       | M.       | Added the comments at 2^nd^      |
| 0.98       | 03-01-23 | Shimojo  | Solar-B MO&DA Meeting at SAO     |
|            |          |          | 2002/07/17-19.                   |
+------------+----------+----------+----------------------------------+
| Version    | 20       | T.       | Added comments from 4^th^ MO&DA  |
| 0.99       | 03-10-17 | Tarbell  | Mtg, March, 2003, at NRL and US  |
|            |          |          | MO&DA Mtg., Oct 2003, at LMSAL.  |
|            |          |          | Added Introduction to the        |
|            |          |          | mission                          |
+------------+----------+----------+----------------------------------+
| Version    | 20       | T.       | Comments from SWG meeting, Nov   |
| 0.99B      | 04-02-04 | Tarbell  | 2003                             |
+------------+----------+----------+----------------------------------+
| Version    | 20       | T.       | Comments from MO&DA meeting,     |
| 0.99C      | 05-09-21 | Tarbell  | Oct, 2004 at SAO and US MO&DA    |
|            |          |          | Mtg., Aug, 2005, at NRL          |
+------------+----------+----------+----------------------------------+
| Version    | 20       | T.       | Comments from MO&DA Mtg., Oct    |
| 1.00       | 05-11-11 | Tarbell  | 2005 at NRL, and SWG Mtg., Nov   |
|            |          |          | 2005                             |
+------------+----------+----------+----------------------------------+

[About the Document]{.underline}

The purpose of the document is to describe the plan for the mission
science 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 ISAS/JAXA, NASA, and PPARC to
indicate its acceptance by the Science Working Group.

Contents

[1. Introduction 1.1.1-4](#introduction)

[2. Operations of the Solar-B Satellite and its Instruments
1.1.1-8](#operations-of-the-solar-b-satellite-and-its-instruments)

[2.1. Principles of Solar-B operations
1.1.1-8](#principles-of-solar-b-science-operations)

[2.2. The operation system of Solar-B
1.1.1-9](#the-operation-system-of-solar-b)

[2.2.1. The personnel of the Solar-B daily operation
1.1.1-9](#the-personnel-of-solar-b-daily-operation)

[2.2.2. The flowchart of the Solar-B operation
1.1.2-13](#the-flowchart-of-the-solar-b-operation)

[2.3. Scientists resident at ISAS from US and UK
1.1.2-18](#scientists-resident-at-isas-from-us-and-uk)

[2.4. Software required for daily operations
1.1.2-19](#software-required-for-daily-operations)

[2.4.1. ISACS-PLN 1.1.3-19](#isacs-pln)

[2.4.2. Software for the fundamental operation of Solar-B
1.1.4-20](#software-for-the-operation-of-solar-b)

[2.4.3. Software for the operation of the instruments
1.1.5-22](#software-for-the-operation-of-the-instruments)

[2.4.4. Special software for the instruments
1.1.6-24](#special-software-for-the-instruments)

[2.4.5. The summary table of the Solar-B operation tools
1.1.7-26](#the-summary-table-of-the-solar-b-operation-tools)

[3. Scheduling and Submission of Observation Plans and Data Policy
1.1.7-27](#scheduling-and-submission-of-observation-plans-and-data-policy)

[3.1. Principles of observation plans and data policy
1.1.7-27](#principles-of-observation-plans-and-data-policy)

[3.2. "Baseline" observations and "proposal" observations
1.1.7-27](#baseline-programs-and-proposed-observations)

[3.2.1. Proposal submissions 1.1.8-28](#proposal-requirements)

[3.2.2. Scientific schedule coordinators
1.1.9-28](#role-of-scientific-schedule-coordinators)

[3.2.3. Data policy **Error! Bookmark not
defined.**](#__RefHeading___Toc31106120)

[3.2.4. Responses to solar activity and coordination with ground-based
observatories
1.1.10-29](#responses-to-solar-activity-and-coordination-with-ground-based-observatories)

[3.3. Coordination of data analysis **Error! Bookmark not
defined.**](#__RefHeading___Toc31106122)

[4. Archiving, Distribution and Analysis of Solar-B Data
1.1.10-30](#archiving-distribution-and-analysis-of-solar-b-data)

[4.1. Fundamental views on Solar-B Data processing system
1.1.10-30](#fundamental-views-on-solar-b-data-processing-system)

[4.2. Classification of Solar-B processed data
1.1.10-30](#classification-of-solar-b-processed-data)

[4.3. The flowchart of the Solar-B data processing
1.1.10-35](#the-flowchart-of-the-solar-b-data-processing)

[4.4. The Archiving System of Solar-B data
1.1.10-36](#the-archiving-system-of-solar-b-data)

[4.5. The Solar-B data-providing system for the main Solar-B sites at UK
and US
1.1.10-37](#the-solar-b-data-providing-system-for-the-other-solar-b-sites-in-japan-uk-us-and-norway)

[4.6. The Solar-B data-providing and searching system for end-users
1.1.10-38](#the-solar-b-data-providing-and-searching-system-for-end-users)

[4.7. Software required for Solar-B data processing
1.1.10-41](#software-required-for-solar-b-data-processing)

[5. Acronyms 1.1.10-42](#acronyms)

# Introduction

1.1 Overview of the Solar-B Mission

Solar-B is an international cooperative mission between ISAS/JAXA of
Japan, NASA of the United States, and PPARC of the United Kingdom. It
builds on the great success of 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 space plasmas 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 will measure 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 scientific
understanding of the sources and mechanisms of solar variability. The
primary scientific goal of the Solar-B mission is to observe how changes
in the photospheric magnetic field propagate through the different
higher layers of the solar atmosphere. Achievement of this goal requires
continuous, simultaneous observations, of specific solar 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 three objectives 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 the
interstellar medium.

The SOT and its focal plane instruments provide quantitative
measurements of the Sun's full vector magnetic field on spatial scales
of 200 to 300 km over a field of view large 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 to both
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 is greater 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 high resolution spectra and images of the photosphere and
chromosphere, some with full polarization 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, toroidal grating, stigmatic
spectrometer covering two diagnostically important EUV wavelength bands
centered on 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, the telescope covers a broad range of
temperatures, with low temperature response enhanced compared with
Yohkoh/SXT. It can also take visible G-band images for coalignment with
SOT and EIS.

ISAS/JAXA provides the overall mission management, mission operations,
the spacecraft, the launch vehicle, and the SOT. In addition, ISAS/JAXA
provides the tip-tilt mirror assembly, which is an integral part of the
SOT Image Stabilization System. ISAS/JAXA also provides the
charge-coupled device (CCD) and its associated electronics for the XRT
camera.

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, the instrument 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/JAXA, provides structural
interfaces, power, attitude control and pointing, data storage and
transmission capability, and environmental protection services to the
science instruments. It is designed for a three-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 or equal 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 the 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 a nominal 97 degree inclination.

Spacecraft control, data collection, and tracking are under the control
of ISAS/JAXA and will 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 the
Solar-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 (@3^rd^ Solar-B science meeting \[DeLuca\])

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

-   EIS Science Data Products (@3^rd^ 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 (@3^rd^ Solar-B science meeting
    \[Berger\])

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

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

# 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

```{=html}
<!-- -->
```
-   Usage of the data recorder

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

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 to participate 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
    team

II. Chief observers (SOT_CO, XRT_CO, EIS_CO) are assigned for scientific
    operation planning and health-check of the instruments. In the early
    phases of the 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 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 the real-time operations team (engineers of the
    contractors) at KSC cannot speak English, Japanese-speaking
    scientists are assigned for the persons in charge of the real-time
    operation. It is assumed that at least one of the chief observers is
    a Japanese speaking scientist.

# The operation system of Solar-B

# 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 and command 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 the reformatter.

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

```{=html}
<!-- -->
```
-   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 Observer of the
        instrument.

    -   CP works at ISAS Sagamihara campus.

    -   During normal science operations the CP main tasks are as
        follows:

        -   To coordinate the observing plans among the telescopes and
            resolve conflicts when necessary,

        -   To provide inputs to automated software routines for
            generating sequences of satellite commands needed for
            nominal science observing, details of which are described
            below.

        -   To compile an integrated science operations command plan
            from all the submitted plans, and hand it over to the Real
            Time Tohbans (described below) for execution.

    -   Coordination of Data Recorder usage

> Management of the mission science data rate is critical to the daily
> science operations. After the Data Recorder (DR) usage plan is defined
> in weekly and daily meetings, the CP will perform the following
> routine tasks:

-   To provide DR daily usage planning information to the COs,

-   To verify the instrument observation~~s~~ plans submitted by the COs
    are consistent with the DR daily usage plan.

-   To input the daily ground station contact information into the
    communication planning software to generate commands sequences
    required for routine satellite data downlink.

```{=html}
<!-- -->
```
-   Coordination of solar target selection

> The selection of solar targets for observing is defined in weekly and
> daily meetings. The CP will input the daily science target coordinates
> into the software provided by the Attitude Orbital Control System
> (AOCS) team to generate commands sequences required for routine
> satellite pointing. The CP also performs routine tasks with AOCS-team
> provided software to prepare satellite commands needed for nominal
> science observing, including updating of orbital elements and
> parameters.

-   Compile daily real-time commanding plan and OP/OG

    -   After receiving the commands and observation tables from the
        COs, the CP compiles all the received commands and tables and
        generates the commanding plan. The ISACS-PLN system is used for
        this automated process.

    -   The CP reviews the generated OP/OG and real-time commanding plan
        with graphical time-chart of major commands (pointing, downlink,
        eclipse, etc).

    -   Finally, the CP submits the OP/OG and real-time commanding plan
        to the Real Time Tohban for review and approval.

-   For off-nominal situations, the CP will hand over operations to the
    Special Engineering Support Team described below.

```{=html}
<!-- -->
```
-   Real-Time Operators \[RT Tohbans\] (3)

    -   RT Tohbans are responsible for the safe and successful operation
        of the satellite and spacecraft subsystems. They conduct all
        real-time satellite operations.

    -   RT Tohbans work at SAGAMIHARA campus after the launch and early
        operations phase.

    -   Japan (ISAS/JAXA) basically takes responsibility for real-time
        operations. Due to limited human resource in Japan, ISAS/JAXA's
        baseline during nominal science observing period after initial
        phase is as follows. (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 are nominally used for data downlinks only.

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

    -   RT Tohban reviews the OP/OG plan received from the CP to ensure
        the safe operation of the satellite and spacecraft subsystems
        will be maintained.

    -   RT Tohban checks the status of the satellite, spacecraft
        subsystems, and instruments in real time during ground contact
        periods.

        -   If any anomaly is found in the status check, the RT Tohban
            can issue pre-determined commands to put the instrument
            and/or spacecraft into a safe configuration, by following
            the operations manual.

        -   The recovery operation of the instrument and/or spacecraft
            will be scheduled at evening operations, if it is not
            urgent.

        -   For off-nominal situations, the CP will hand over operations
            to the Special Engineering Support Team described below.

-   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 and telescope 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\] (1)

```{=html}
<!-- -->
```
-   Is an ISAS/JAXA 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 JAXA space tracking
    department.

-   Checks the data transfer from the ground stations.

```{=html}
<!-- -->
```
-   Scientific Schedule Coordinators \[SSC\] (7 )

    -   Consist of senior scientists designated by each of the
        instrument PIs, who will reside 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 collection and processing activities of the
        Solar-B project at ISAS.

    -   SDC manages his team at ISAS, which includes computer system
        administrator and some engineers for maintaining databases and
        checking the process 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 any anomaly in the Level-0 reformatting
            process, he reports it to the instrument team for
            resolution.

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

During the initial phase of the Solar-B operations (until about 3 months
after the Solar-B launch), additional persons (satellite and instrument
experts) may 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

    ```{=html}
    <!-- -->
    ```
    -   Will work at ISAS-SAGAMIHARA/Japan during the initial phase.

    ```{=html}
    <!-- -->
    ```
    -   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
            establishing standard procedures for instrument
            calibrations.

```{=html}
<!-- -->
```
-   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

```{=html}
<!-- -->
```
-   Special Engineering Support Team

The launch and early operations will be handled by ISAS/JAXA and
contractor engineers familiar with the satellite. After early operations
are complete and the satellite is nominal, operations will be handed
over to the CP, COs, Engineering Advisors, and RT Tohbans as described
above. Nevertheless, 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 occultations, safehold
recoveries, and other spacecraft contingency responses. ISAS/JAXA and
spacecraft contractors will be responsible for these activities.

# The flowchart of the Solar-B operation

![](media/image1.wmf)

![](media/image2.wmf)

![](media/image3.wmf){width="5.264583333333333in"
height="9.120833333333334in"}

-   Monthly Meeting \[Tele-conference\]

    -   Participants: Project Manager, Principal Investigators, Science
        Scheduling Coordinators, Chief Observers, Database Coordinator

    -   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 (2^nd^) month

    -   Decisions on the next monthly plan.

    -   Prioritize the observations of the next month, and make the
        priority list of the observations.

-   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
        maneuver schedule of next week (nearly final)

    -   Allocation 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-base Contacts

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

```{=html}
<!-- -->
```
-   The deadline for input to the day's operation plan (commands,
    observation tables, etc.) to the Solar-B Chief Planner is 10:30 JST
    each day.

-   The entire Solar-B operation plan for the next day, including the
    command plans during real-time operations, the OP/OG, and the
    observation tables, is completed by the 15:00 JST. Then the RT
    Tohbans make the final check of the operation plan for that evening.
    The plan will be uplinked during evening passes and will take effect
    after the second evening pass. Plans will cover approximately 36
    hours of operations, in case the evening uplinks the following day
    are not successful.

-   In nominal operations, the plans are approved on a daily basis.
    However, in case an urgent operation change is requested as the
    result of checking the data downlinked during the morning passes,
    the planners should make the revised plan for 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. The third position will be provided by EIS team
members from the UK, Norway, and the US, who will rotate to ISAS for
roughly three weeks at a time. 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 in both
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, for periods of a few weeks
to a few months at a time.

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 XRT team will provide a scientist to cover each
month that the resident scientist is away from 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 the first year of operations.

In the initial phase of the solar-B operation, additional scientists
and/or engineers from each 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.

# ISACS-PLN 

ISACS-PLN is a software system to convert requests for operation of the
instruments and spacecraft into the format required by the ISAS/JAXA
ground system and Solar-B. Inputs to the system are:

-   Sequence of Event (SOE) files, which can be automatically created
    for predictable events such as telemetry downlinks, orbital
    eclipses, SAAs, etc.

-   Operations Request Language (ORL) files, which consist of

    -   Sequences of commands

    -   Execution definitions which relate Sequences with Events

-   Memory load images for observation tables and software loads

In the ISACS-PLN system, we can accumulate knowledge of satellite
operations which makes routine operation safe and easier to accomplish.
ISACS-PLN uses the Satellite Information Base (SIB), the master database
of commands and telemetry. The knowledge base of bus commands is
contained in ORL files, which minimize handwork for nominal operations.
Requests from user accounts are checked against the knowledge base of
allowed commands, which ensures that CP and COs cannot send
inappropriate or hazardous commands to the spacecraft. The knowledge
base of satellite operation, which rarely changes, is maintained by
ISAS/JAXA. The CP and COs will make daily inputs of ORL files and memory
loads, as needed to carry out nominal science operations.

# 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, and night 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 not only for planning of observations
> but also for troubleshooting of the spacecraft. 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.)

```{=html}
<!-- -->
```
-   Estimating the downlink data size

> After coordinating with the ground stations by the Ground-base
> Contacts Coordinator, the information on the station contacts of
> Solar-B is provided with this software. The software estimates the
> volume of downlink data using the contacts schedule. The estimated
> data size is used for coordinating the usage of the 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

-   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 OP, the real-time operation plans and the
> prediction of the data output rate from each instrument into account.
> The time-line also indicates the stored data volume of the data
> recorder.

-   Japan team takes responsibility for the development

-   USER : Chief Planner

-   INPUT : OP (or SoE/Macros)

-   OUTPUT : Graphical Time-chart of Operations

```{=html}
<!-- -->
```
-   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 change the pointing
to different solar targets several times a day. Since the parameters for
commanding spacecraft maneuvers are complicated, and mis-commanding may
lead to 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 not allow the Chief Planner to
enter other AOCS commands beyond those required for solar target
selection.

-   Japan team and the contractor for AOCS 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 the DR and telemetry allocation

> After making the commands and the observation tables by COs, CP checks
> the usage of DR based on the data output rates from all instruments
> and makes the MDP commands for the telemetry allocation to each
> instrument. ISAS-provided software supports the check and makes the
> commands.

-   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 allocation of telemetry

> Graphical chart of the data size stored in DR

-   Health check reformat software

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

-   Japan team take responsibility for the development

-   USER : RT Tohban, Chief Observer, etc.

-   INPUT : raw-telemetry data (from SIRIUS)

-   OUTPUT : Health Check data

```{=html}
<!-- -->
```
-   Health check and monitoring system for the Satellite

> During the real-time operations, the RT Tohban checks the health of
> Solar-B using the health check and monitoring systems. The system is
> used for checking the fundamental status of Solar-B, for example,
> battery voltages, temperatures, etc. The contractor that develops the
> telemetry system provides the software.

-   Japan team and the S/C contractor (MELCO) take responsibility for
    the development

-   USER : RT Tohban

-   INPUT : raw-telemetry data

# 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 be archived by name, identification number and scientific
> objective, for ease of rerunning and/or modifying. Each instrument
> team will design and develop its own database.

-   Instrument teams take responsibility for the databases

-   USER : Chief Observer

-   INPUT : Observation Plan

-   OUTPUT : Database tables

```{=html}
<!-- -->
```
-   Software for creating the observing tables

> Chief Observers make the observing tables for each instrument based on
> the observation plans. This software creates the command sequence of
> the observing tables based on the observing plan of the chief
> observer. The software has interfaces with ISAC-PLN, and refers the
> database of Solar-B operation and observation, 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

```{=html}
<!-- -->
```
-   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 or telemetry 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

```{=html}
<!-- -->
```
-   Observation simulation software for estimating the output data rate
    and size

This software simulates the observations from the observing tables and
the instrument command timeline and estimates the data output between
the ground-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

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

```{=html}
<!-- -->
```
-   Health check and monitoring system for the instruments

During the real-time operations, the RT Tohbans check 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
as same as that at ISAS/SAGAMIHARA, which was used during the
Proto-Model and Flight-Model testing. We will use the same software
developed in the PM and FM tests, and in the real-time operations with
minor revisions.

-   Instruments team take responsibility for the tool

-   USER : RT Tohbans, Chief Observer

-   INPUT : Health Check data

-   OUTPUT: Real Time display

```{=html}
<!-- -->
```
-   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 remote sites. For this purpose, web displays of
status information are automatically made from 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

# Special software for the instruments

-   Making MDP/SOT Doppler parameters

> Since the wavelength settings of the spectropolarimeter and the
> narrowband tunable filter of SOT are affected by the orbital motion of
> the satellite, the MDP has software to calculate the Doppler velocity
> based on the spacecraft orbital elements uplinked at regular time
> intervals.

-   SOT team take responsibility for the tool

-   USER : Chief Observer of SOT

-   INPUT : Observation Plan, Orbital Elements, etc.

-   OUTPUT : Memory images of upload parameters

# The summary table of the Solar-B operation tools

+--------------------------------+-------+------+----------+----------+
| **Tools**                      | **Ma  | **Us | *        | **       |
|                                | ker** | er** | *Input** | Output** |
+--------------------------------+-------+------+----------+----------+
| Prediction of satellite        | ISAS  | CP   | Orb.     | SoE      |
| environments                   |       |      | Elem.    |          |
+--------------------------------+-------+------+----------+----------+
| Estimating the downlink data   | ISAS  | GCC  | Orb.     | SoE      |
| size                           |       |      | Elem.    |          |
|                                |       |      |          | List     |
+--------------------------------+-------+------+----------+----------+
| Support tool for checking OP   | ISAS  | CP   | SoE      | G        |
| and the real-time commanding   |       |      |          | raphical |
| plan                           |       | RT   | OP       |          |
|                                |       |      |          | Ti       |
|                                |       |      |          | me-chart |
+--------------------------------+-------+------+----------+----------+
| Making commands required for   | ISAS  | CP   | Obs.     | SoE      |
| the satellite pointing         |       |      | plan     |          |
|                                | AOCS  |      |          | Macro    |
+--------------------------------+-------+------+----------+----------+
| Checking　DR and Making the    | ISAS  | CP   | data     | S        |
| TLM_LMT commands               |       |      | rates    | oE/Macro |
|                                |       |      | files    |          |
|                                |       |      |          | Ti       |
|                                |       |      |          | me-chart |
+--------------------------------+-------+------+----------+----------+
| Reformatter for Health Check   | ISAS  | CO   | Ra       | Health   |
| Data                           |       |      | w-telem. | Check    |
|                                |       | KSC  |          | data     |
| (CCSDS \> IDL-readable format) |       |      |          |          |
+--------------------------------+-------+------+----------+----------+
| Health check system for        | ISAS  | KSC  | Ra       | (Display |
| spacecraft system              |       |      | w-telem. | to       |
|                                | MELCO | CP   |          | monitor) |
+--------------------------------+-------+------+----------+----------+
| Creating the observation table | PI    | CO   | Obs.     | Obs.     |
|                                |       |      | plan     | table    |
+--------------------------------+-------+------+----------+----------+
| Support tool for commanding    | PI    | CO   | Obs.     | SoE      |
| plan for the instrument        |       |      | plan     |          |
|                                |       |      |          | Macro    |
+--------------------------------+-------+------+----------+----------+
| Estimate the output data size  | PI    | CO   | Obs.     | Ti       |
| from the prepared observing    |       |      | table    | me-chart |
| table                          |       |      |          | ASCII    |
|                                |       |      |          | file     |
+--------------------------------+-------+------+----------+----------+
| Real time health check system  | PI    | CO   | Health   | Display  |
| for the instrument             |       |      | Check    | to       |
|                                |       | KSC  | data     | monitor  |
+--------------------------------+-------+------+----------+----------+
| Status Web Pages for remote    | PI    | I    | Status   | Web      |
| checking                       |       | nst. | Data     | Pages    |
|                                |       | Team |          |          |
+--------------------------------+-------+------+----------+----------+
| Making SOT/MDP Doppler         | SOT   | CO   | Orb.     | P        |
| parameters                     |       |      | Elem.    | arameter |
|                                |       |      |          |          |
|                                |       |      | Obs.     |          |
|                                |       |      | plan     |          |
+--------------------------------+-------+------+----------+----------+

# Scheduling and Submission of Observation Plans and Data Policy

# Principles of observation plans and data policy

-   The Solar-B team recognizes the importance of rapid dissemination of
    the observatory's data sets to the worldwide solar physics community
    for both the success of the Solar-B mission and the benefit of solar
    physics. During the commissioning and initial observing period,
    several sample datasets will be released to the entire community.
    Then, the Solar-B team will make all of its data available
    immediately without restriction beginning no later than six months
    after launch.

i.  Solar-B will be operated according to a pre-determined plan during
    the initial 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
     scheduling coordinators (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 of Solar-B. Disputes or conflicts
    will be addressed by the SSCs.

# 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 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 the
scientific scheduling coordinators. Joint observations with other
satellites and ground-based observatories are encouraged.

# Proposal requirements

-   All proposals shall be in English.

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

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

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

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

# Role of Scientific Schedule Coordinators

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

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

-   SSCs will be authorized to select or reject proposal observations,
    and to draft the monthly observation schedules. Proposals may be
    rejected if, for example, the same observation plans are already
    proposed, the essential parts of the proposed plans overlap with a
    PhD thesis in progress, the science is not compelling, or the
    proposed observations exceed instrument capabilities or violate
    health and safety constraints..

-   Every month the SSCs will designate targets of opportunity (if any)
    and set priorities for their observation.

# Responses to solar activity and coordination with ground-based observatories 

-   Target of Opportunity campaigns can be inserted in the monthly
    planning.

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

-   Chief 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 to choose targets of opportunity, when they
    are included in the monthly plan.

# Archiving, Distribution and Analysis of Solar-B Data

# Fundamental views on Solar-B Data processing system

A)  The Solar-B telemetry data processing system uses the ISAS/JAXA
    satellite database system: 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 for ground 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 their
    successors.

# 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

In this section, we explain these data levels.

-   **Raw telemetry data**

```{=html}
<!-- -->
```
-   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/JAXA satellites database at the ISAS/SAGAMIHARA
    campus. ISAS maintain all the data of the ISAS/JAXA satellites via
    this database on line.

-   The "SDTP" protocol (ISAS original protocol) is used to retrieve the
    data from the SIRIUS database.

```{=html}
<!-- -->
```
-   **Health check data**

```{=html}
<!-- -->
```
-   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
database and 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 science data.

-   **Level-0 data**

```{=html}
<!-- -->
```
-   Reformatted raw telemetry data file.

-   The data format of Level-0 is FITS with binary table extension. The
    format of Level-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 as
> defined by each instrument. This is a single image for XRT. For SOT it
> consists of all raw images obtained for a specific SOT data product; a
> single filter image, or a set of images obtained to create a single
> Dopplergram 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 each
> wavelength are put the header of the binary table. The unit of the
> file is one raster. EIS will be use the format for Level-0 data.
>
> ![](media/image4.wmf){width="5.902083333333334in"
> height="4.428472222222222in"}

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

```{=html}
<!-- -->
```
-   **Calibration data**

```{=html}
<!-- -->
```
-   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 the revision using the homepage of Solar-B, e-mail, etc.

```{=html}
<!-- -->
```
-   **Level-1 data**

```{=html}
<!-- -->
```
-   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.

```{=html}
<!-- -->
```
-   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 by users will not be archived in the Solar-B data
    providing system.

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

```{=html}
<!-- -->
```
-   **Level-2 Data**

```{=html}
<!-- -->
```
-   Level-2 data are made from Level-1 data.

```{=html}
<!-- -->
```
-   One category of Level-2 data is the data in physical units. In the
    other word the level-2 data consist of files such as longitudinal
    magnetogram, dopplergram, vector magnetogram, filling factor, B
    vector, etc.

```{=html}
<!-- -->
```
-   The level-2 data have the headers that include the Level-1 headers
    and additional information about the derivation.

```{=html}
<!-- -->
```
-   Level-2 data are compressed by loss-less compression methods.

```{=html}
<!-- -->
```
-   Level-2 data that are standard data products made by the instrument
    teams.

```{=html}
<!-- -->
```
-   Only SOT/SP Level-2 data are provided by the Solar-B data-providing
    system.

```{=html}
<!-- -->
```
-   Additional Level-2 data volunteered by the team members and
    submitted to the archive may also be provided in the same way. For
    example, 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 data archive, html \...).

```{=html}
<!-- -->
```
-   **Level-Q data**

```{=html}
<!-- -->
```
-   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 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.

# The flowchart of the Solar-B data processing

![](media/image5.wmf)

![](media/image6.wmf)

# The Archiving System of Solar-B data

-   The master database, containing Level-0, 2[^1], Q and Calibration
    data are constructed 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 to archive and distribute space science data
    obtained via ISAS/JAXA 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.

# The Solar-B data-providing system for the other Solar-B sites in Japan, UK, US, and Norway

We will make the copies of the Solar-B database at several institutes,
for example, NAO in Japan, LMSAL, SAO, NRL, GSFC in US, MSSL/RAL in UK
and UiO in Norway. Level-0 data will be transferred via the internet
using lossless compression and multi-stream transfers to achieve an
acceptable transmission rate. We estimate a daily volume 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 display transmissions rates of 100kB/s for single ftp
streams, thereby just satisfying the average requirement. Multiple ftp
streams increase this rate proportionally and provide sufficient
headroom to maintain the Level-0 data flow.

In the Solar-B project, Level-1 data will not be 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 from Japan to US and UK. The vector
magnetograms and associated Level-2 data will be provided to the archive
by the SOT team from their home sites, since the calibration and Stokes
parameter inversions are complicated and compute-intensive.

![](media/image7.wmf)

# The Solar-B data-providing and searching system for end-users

In order to maximize the scientific returns from SOLAR-B observations, a
useful search/provide system for end-users is an essential part of the
SOLAR-B database. In particular, the system must enable users to search
the data of three instruments using a unified interface to the system.
To meet these requirements, ISAS/JAXA and NAOJ will jointly develop the
SOLAR-B mission-wide data search/provide system. The system will have
the following properties.

-   Users can search and get Level-0/2 FITS files of three instruments
    from one web interface to the system.

-   The system is built on a Relational Database (RDB) with a web GUI
    interface, implemented in JAVA and XML.

-   All search keys of the search system are selected from the FITS
    keywords of the Level-0 or 2 FITS files.

-   The users (scientists) can get the Level-0/2 FITS files selected by
    the search system.

-   The system can display the results of a search graphically.

-   The system has the interfaces for VSO, EGSO and UK AstroGrid.

-   The system is based on the DARTS system and the data search system
    for "SUZAKU" (ASTRO-EII).

-   Although the database system performs on the DARTS system of
    ISAS/JAXA, the system can be mirrored at the other SOLAR-B sites.

![](media/image8.wmf){width="6.375in" height="4.776388888888889in"}

Figure: The Architecture of Services for Users.

![](media/image9.wmf)

# Software required for Solar-B data processing

-   ISAS/JAXA 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/JAXA will provide secondary reformatters to make Level-0 data
    products for status data

-   Level-1 reformat software (calibration)

```{=html}
<!-- -->
```
-   Each instrument team provides the software for calibration.

```{=html}
<!-- -->
```
-   Level-2 software (derivation of physical quantities)

```{=html}
<!-- -->
```
-   Each instrument team provides the software for derivations.

```{=html}
<!-- -->
```
-   Level-Q reformat software (Images and movies for Quick Look)

```{=html}
<!-- -->
```
-   The instrument teams make the software

```{=html}
<!-- -->
```
-   Data-providing and searching system

-   Provided by ISAS/JAXA

```{=html}
<!-- -->
```
-   The system is on the web server system and a relational database
    system.

-   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 VSO, EGSO and UK AstroGrid

```{=html}
<!-- -->
```
-   Data analysis software

```{=html}
<!-- -->
```
-   Common parts of the data analysis software (ex. I/O of Level-0
    and 1) are made 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.

-   Each instrument team prepares the guidebook for its data analysis,
    which is similar to YAG (Yohkoh Analysis Guide).

# Acronyms

![](media/image10.wmf)

[^1]: Only vector magnetograms made from SOT/SP data