The List of SOLAR-B”Hinode” Mission-Wide FITS Keywords
2006/12/25 Ver.1.3: Masumi Shimojo

I.

Introduction

After the launch of SOLAR-B, we will get large amounts of observational data from three
instruments SOT, XRT and EIS. In order to select one data file from the data, the databasewith the search function is the indispensable system for SOLAR-B data analysis. Especially,
we need the database system that can survey the data of three instruments from one
interface.
The database accumulates the information of the observations, and the search function of
the database selects the data based on the information. Although there are several ways foraccumulating of the information of the observations, it is easiest to get the information fromthe FITS header (PHU) of the SOLAR-B FITS files. If we use the FITS header for searching
the data of three instruments, we have to unify the definition of some FITS keywords.
The aim of this document is to list the common FITS keywords (SOLAR-B Mission-Wide
Keyword) of three instruments and unify the definition of the SOLAR-B Mission-Wide
keywords for the search function of the database. The SOLAR-B MODA WG requests all
instrument teams to include all SOLAR-B Mission-Wide FITS keywords in the FITS headerof each instrument and adapt the definition in the document to these FITS keywords.
The Mission-Wide keyword list includes only the common keywords for the search function.
Hence, we need the other FITS keywords for the data search of each instrument data. The
keywords are defined by each instrument team.

II.

Structure of SOLAR-B Mission-Wide Keywords

The SOLAR-B Mission-Wide Keywords are classified into the following parts. In the section,
we summarize the subject matters of the parts.

1Standard keywords for the FITS standard
The FITS keywords are the essential keywords for the standard FITS files. Hence,the keywords are based on the FITS standard.

2

Information of the instrument
The part indicates the information of the instrument/the satellite

3

Information of the time
The keywords indicate the date and the time of the observation. And, the keyword
in the part is also defined the time system (UTC, TAI or UT) of the SOLAR-B FITS
files.

4

Information of the coordinates
The keywords indicate the coordinates of the Image data. The FITS standard
method of the coordinate specification is adapted to the section, basically. And, thesome non-FITS standard keywords also are included

5

Information of the observation plan
The keywords present the properties of the observation. Basically, the values of
the keywords are decided by the proposer of the observation or the chief observers.
The values of the keywords are inputted to the SOLAR-B operational databaseusing the planning tool, and the reformat program gets the data for the keywords
from the operational database.

6

Information of the data quality
The keywords in the part indicate how to compress the data in MDP. And theenvironments of the satellite (SAA, HLZ) are also indicated.

7

Information of the reformat and etc.
The keywords indicate the information of the reformat. For example, the date of thereformat, the version of the reformat program and etc...

III.

The list of SOLAR-B Mission-wide Keywords

Legend:Header Keyword: Name of the Keyword

Format: Indicate the format (String, Integer....) of the value

Unit/Option: Unit of the Value / Possible Objects for the keyword

Category: Indicate the keyword from FITS standard, SSW or
Solar-B Special

Data Source: Data source(s) of the value

Sample: Example of the value of the keyword

Description: Description of the keyword

Note: Notes or the points for discussion in MODA WG

1. Standard keywords for the FITS standard

Header Keyword: SIMPLE

Format: Logical

Unit/Option: T or F

Category: FITS

Data Source: Reformatter (Fixed value)

Sample:T

Description: Indicate that the FITS file is a FITS standard file or not.

Header Keyword: BITPIXFormat: Integer

Unit/Option: 8, 16, 32, -32, -64

Category: FITS

Data Source: Reformatter (Fixed value)

Sample: 16

Description: Number of bits per pixel

Header Keyword: NAXIS

Format: Integer

Unit/Option:-

Category: FITS

Data Source: Telemetry (Image data)

Sample:2

Description: Number of data array dimensions

Note: Since the FITS file of EIS uses the binary table extension, thevalue is 2 in EIS FITS files.

Header Keyword: NAXISn

Format: Integer

Unit/Option:-

Category: FITS

Data Source: Telemetry (Image data)

Sample: 128

Description: Number of pixel (data point) in “n”-dimensions of the data array

Note: Since the FITS file of EIS uses the binary table extension, thevalues indicate the bytes of row [NAXIS1] or the number of row[NAXIS2].

2. Information of the Instrument

Header Keyword: TELESCOPFormat: String

Unit/Option:-

Category: FITS

Data Source: Reformatter (Fixed value)

Sample: SOLAR-B

Description: Name of the satellite

Header Keyword: INSTRUME

Format: String

Unit/Option: EIS, XRT, SOT/FG, SOT/SP, SOT/CT

Category: FITS

Data Source: Telemetry (Image data) or Reformatter

Sample: EIS

Description: Name of the Instrument

3. Information of the time

Header Keyword: TIMESYS

Format: String

Unit/Option: UTC

Category: FITS

Data Source: Reformatter (Fixed value)

Sample: UTC

Description: Indicates the time system of the FITS file

Note

: The time convert (TI to Time) software developed by ISAS outputs
the number of seconds from 2000/1/1 00:00:00. At 2005, theoutput of the software is consistent with UTC. If the leap second isinserted, the consistency is broken. Then, the reformat program
needs the information of the leap seconds

Header Keyword: DATE_OBS

Format: String

Unit/Option: UTC / YYYY-MM-DDThh:mm:ss.sss

Category: FITS

Data Source: Telemetry (Image data)

Sample: 2006-12-31T05:53:29.300

Description: Start time of the exposure or the raster

Note: XRT team proposed TIME_OBS for the name of the keyword.

Header Keyword: OBT_TIME

Format: Integer

Unit/Option: TI clockCategory: SOLAR-B

Data Source: Telemetry (Image data)

Sample: 12345

Description: Start time of the exposure or the raster in TI counter

Header Keyword: DATE_END

Format: String

Unit/Option: UTC / YYYY-MM-DDThh:mm:ss.sss

Category: FITS

Data Source: Telemetry (Image data)

Sample: 2006-12-31T05:53:29.300

Description: End time of the exposures and the raster

Note: The keyword is only used for SOT/SP, EIS, and certain
observables of SOT/NB (e.g. magnetograms, Dopplergrams,
Stokes parameters).

Header Keyword: OBT_END

Format: Integer

Unit/Option: TI clock

Category: SOLAR-B

Data Source: Telemetry (Image data)

Sample: 12345

Description: End time of the exposures or the raster in TI counter

Note: The keyword is only used for SOT/SP , EIS, and certain
observables of SOT/NB.

4. Information of the coordinates

Header Keyword: CRPIX1 (CRPIX2 in SOT/SP)

Format: FloatUnit/Option: pixelCategory: FITS

Data Source: Reformatter

Sample: 128.5

Description: Coordinates (X) of the reference pixel in the data

Note

: 1. In SOT/SP, the X-axis is 2nd dimension of the data array. Hence,
the keyword in SOT/SP FITS files is CRPIX2.
2. Each instrument team can decide the location (CRPIX) of thereference pixel in the image. But, they should announce thelocation of the reference pixel for SOLAR-B MODA team.
3. The value is counted from 1 to N.

Header Keyword: CRPIX2 (CRPIX3 in SOT/SP)

Format: FloatUnit/Option: pixelCategory: FITS

Data Source: Reformatter

Sample: 128.5

Description: Coordinates (Y) of the reference pixel in the data

Note

: 1. In SOT/SP, the Y-axis is 3rd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CRPIX3.
2. Each instrument team can decide the location (CRPIX) of thereference pixel in the image. But, they should announce thelocation of the reference pixel for SOLAR-B MODA team.
3. The value is counted from 1 to N.

Header Keyword: CRVAL1 (CRVAL2 in SOT/SP)

Format: FloatUnit/Option: arcsec

Category: FITS

Data Source: Telemetry (Image data and AOCS data) and the calibrations
before the launch and on the orbit

Sample: 200.36

Description: Coordinates (X) of the reference pixel in heliocentric-coordinate

Note: 1. In SOT/SP, the X-axis is 2nd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CRVAL2.
2. It is very hard to determine the value of the keyword in highaccuracy just after the observations. Hence, the permission
accuracy of the values in LEVEL-0 data is ∓15 arcsec.
3. After the launch and the calibration of alignments between,

UFSS, SOT, XRT, EIS and ground-base observation, we will
improve the calculation of the value.
Header Keyword: CRVAL2 (CRVAL3 in SOT/SP)

Format: FloatUnit/Option: arcsec

Category: FITS

Data Source: Telemetry (Image data and AOCS data) and the calibrations
before the launch and on the orbit

Sample: 200.36

Description: Coordinates (Y) of the reference pixel in heliocentric-coordinate

Note: 1. In SOT/SP, the Y-axis is 3rd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CRVAL3.
2. It is very hard to determine the value of the keyword in highaccuracy just after the observations. Hence, the permission
accuracy of the values in LEVEL-0 data is ∓15 arcsec.
3. After the launch and the calibration of alignments between,
UFSS, SOT, XRT, EIS and ground-base observation, we will
improve the calculation of the value.

Header Keyword: CDELT1 (CDELT2 in SOT/SP)

Format: FloatUnit/Option: arcsec

Category: FITS

Data Source: Reformatter(Based on the calibrations before the launch and on the orbit)

Sample: 0.15

Description: Pixel size (X) of data array

Note: 1. The value is not the physical pixel size of CCD. It is the pixel
size of the data array. If the instruments have the binning
function, please take care.
2. In SOT/SP, the X-axis is 2nd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CDELT2.
3. After the launch and the calibration of alignments between,
UFSS, SOT, XRT, EIS and ground-base observation, we will
improve the calculation of the value.

Header Keyword: CDELT2 (CDELT3 in SOT/SP)

Format: FloatUnit/Option: arcsec

Category: FITS

Data Source: Reformatter(Based on the calibrations before the launch and on the orbit)

Sample: 0.15

Description: Pixel size (Y) of data array

Note: 1. The value is not the physical pixel size of CCD.

It is the pixel

size of the data array. If the instruments have the binning
function, please take care.
2. In SOT/SP, the Y-axis is 3rd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CDELT3.
3. After the launch and the calibration of alignments between,
UFSS, SOT, XRT, EIS and ground-base observation, we will
improve the calculation of the value.
Header Keyword: CUNIT1 (CUNIT2 in SOT/SP)

Format: String

Unit/Option:-

Category: FITS

Data Source: Reformatter (Fixed Value)

Sample: arcsec

Description: The unit of CRVAL1(2), CDELT1(2), XCEN, FOVX

Note

: In SOT/SP, the X-axis is 2nd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CUNIT2.

Header Keyword: CUNIT2 (CUNIT3 in SOT/SP)

Format: String

Unit/Option:-

Category: FITS

Data Source: Reformatter (Fixed Value)

Sample: arcsec

Description: The unit of CRVAL2(3), CDELT2(3), YCEN, FOVY

Note

: In SOT/SP, the Y-axis is 3rd dimension of the data array.

Hence, the keyword in SOT/SP FITS files is CUNIT3.
Header Keyword: CTYPE1 (CTYPE2 in SOT/SP)

Format: String

Unit/Option:-

Category: FITS

Data Source: Reformatter (Fixed Value)

Sample: Solar-X

Description: Label of axis 1(2)Note

: In SOT/SP, the X-axis is 2nd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CTYPE2.

Header Keyword: CTYPE2 (CTYPE3 in SOT/SP)

Format: String

Unit/Option:-

Category: FITS

Data Source: Reformatter (Fixed Value)

Sample: Solar-Y

Description: Label of axis 2(3)Note

: In SOT/SP, the Y-axis is 3rd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CTYPE3.

Header Keyword: SAT_ROTFormat: FloatUnit/Option: degreeCategory: SOLAR-B

Data Source: Telemetry : HK2_ATT_Z
APID[HEX]: 428
Word[DEC]: 281
Number of bits[DEC]:24[Convart the telemetry to “degree”]
θz = 180/223 x X(X: Telemetry [DEC])

Sample: 0.12

Description: 1.The deference between the north of Sun and the Y-axis of thesatellite.
2. It is very hard to determine the value of the keyword in highaccuracy just after the observations. Hence, the permission
accuracy of the values in LEVEL-0 data is ∓15 arcsec.
Header Keyword: INST_ROT

Format: FloatUnit/Option: degreeCategory: SOLAR-B

Data Source: Reformatter(Based on the calibrations before the launch and on the orbit)

Sample: 0.0

Description: The deference between the Y-axis of the satellite and the images

Note: 1. keyword is reserved for Level-1 files (after the pointing
calibration). Hence, the value is 0.0 at Level-0 files.
2. The value is determined by the results of the alignment between
three instruments, UFSS and the ground-base observations.

Header Keyword: CROTA1

Format: FloatUnit/Option: degreeCategory: FITS

Data Source: SAT_ROT + INST_ROT

Sample: 0.12

Description: The deference between the north of Sun and the Y-axis of images

Note: 1. It is very hard to determine the value of the keyword in highaccuracy just after the observations. Hence, the permission
accuracy of the values in LEVEL-0 data is ∓15 arcsec.
2. In SOT/SP, the X-axis is 2nd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CROTA2.

Header Keyword: CROTA2

Format: FloatUnit/Option: degreeCategory: FITS

Data Source: SAT_ROT + INST_ROT

Sample: 0.12

Description: The deference between the north of Sun and the Y-axis of images

Note: 1. It is very hard to determine the value of the keyword in highaccuracy just after the observations. Hence, the permission
accuracy of the values in LEVEL-0 data is ∓15 arcsec.
2. In SOT/SP, the Y-axis is 3rd dimension of the data array.
Hence, the keyword in SOT/SP FITS files is CROTA3.

Header Keyword: XCEN

Format: FloatUnit/Option: arcsec

Category: SSW

Data Source: CRPIXn, CRVALn, CROTA

Sample: 250.34

Description: The heliocentric coordinate (X) of the center of the image.

Note: 1. It is very hard to determine the value of the keyword in highaccuracy just after the observations. Hence, the permission
accuracy of the values in LEVEL-0 data is ∓15 arcsec.
2. After the launch and the calibration of alignments between,
UFSS, SOT, XRT, EIS and ground-base observation, we will
improve the calculation of the value.

Header Keyword: YCEN

Format: FloatUnit/Option: arcsec

Category: SSW

Data Source: CRPIXn, CRVALn, CROTA

Sample: 250.34

Description: The heliocentric coordinate (Y) of the center of the image

Note: 1.It is very hard to determine the value of the keyword in highaccuracy just after the observations. Hence, the permission
accuracy of the values in LEVEL-0 data is ∓15 arcsec..
2. After the launch and the calibration of alignments between,
UFSS, SOT, XRT, EIS and ground-base observation, we will
improve the calculation of the value.

Header Keyword: FOVX

Format: FloatUnit/Option: arcsec

Category: SOLAR-B

Data Source: NAXIS1 x CDELT1(SOT/SP: NAXIS2 x CDELT2, EIS: XW x CDELT1)

Sample: 300.3

Description: The width of Field of View (X-axis)

Note: 1.In SOT/SP, the X-axis is 2nd dimension of the data array.
Hence, the value is NAXIS2 x CDELT2.
2. Since EIS uses the binary table extension and NAXIS1 indicate
the bytes of row of the binary table, the “NAXIS1 x CDELT1” isnot equal to FOVX. EIS team proposes “XW” keyword for theindicator of the number of pixel in X-axis. Then, FOV in EIS is“XW x CDELT1”.
3. It is very hard to determine the value of the keyword in highaccuracy just after the observations. Hence, the permission
accuracy of the values in LEVEL-0 data is ∓15 arcsec.
4. After the launch and the calibration of alignments between,
UFSS, SOT, XRT, EIS and ground-base observation, we will
improve the calculation of the value.

Header Keyword: FOVY

Format: FloatUnit/Option: arcsec

Category: SOLAR-B

Data Source: NAXIS2 x CDELT2(SOT/SP: NAXIS3 x CDELT3, EIS: YW x CDELT2)

Sample: 300.3

Description: The width of Field of View (Y-axis)

Note: 1.In SOT/SP, the X-axis is 3rd dimension of the data array.
Hence, the value is NAXIS3 x CDELT3.
2. Since EIS uses the binary table extension and NAXIS2 indicate
the number of row of the binary table, the “NAXIS2 x CDELT2” isnot equal to FOVY. EIS team proposes “YW” keyword for theindicator of the number of pixel in Y-axis. Then, FOVY in EIS is“YW x CDELT2”.
3. It is very hard to determine the value of the keyword in highaccuracy just after the observations. Hence, the permission
accuracy of the values in LEVEL-0 data is ∓15 arcsec.
4. After the launch and the calibration of alignments between,
UFSS, SOT, XRT, EIS and ground-base observation, we will
improve the calculation of the value.

Header Keyword: TR_MODE

Format: String

Unit/Option: TR1, TR2, TR3, TR4, and FIX

Category: SOLAR-B

Data Source: Telemetry : HK2_TRAGET_ID
APID[HEX]:428
Word[DEC]:210
The position of Bits[DEC]:0-2
Number of bits[DEC]:3
HK2_TARGET_ID = 0 ⇒ FIX
HK2_TARGET_ID = 1 ⇒ TR1
HK2_TARGET_ID = 2 ⇒ TR2
HK2_TARGET_ID = 3 ⇒ TR3
HK2_TARGET_ID = 4 ⇒ TR4

Sample: TR1

Description: Indicate that the AOCS is in tracking mode (TR) or fix pointing
mode (FIX). The number after “TR” indicates the number of the
tracking curve.

Note: Telemetry of AOCS data
In order to get the heliocentric coordinate of the CCD pixel of the telescope, we need to use thetelemetries of AOCS data and telescopes. In the section, we described how to get the
heliocentric coordinate of the pixel on the CCD.
In the section, we use two coordinate systems. One is the CCD coordinate system. The otherone is the heliocentric coordinate system. Strictly speaking, the AOCS coordinate system isslightly differ from the heliocentric coordinate system. However, when we get the heliocentriccoordinate of the CCD pixel in the Level-0 reformat process, we can assume that thesecoordinate systems are same because the request of the pointing accuracy for level-0 FITS
keyword is 15 arcsec. The relationship of the heliocentric and CCD coordinate systems ispresent in Figure 1.

Y(heliocentric)≈X (AOCS coordinate)θY(CCD)X

nxCCD-YHK2_ATTYoffＡT-XHK2_ATT

X(heliocentric)nyCCD≈Y (AOCS coordinate)

Solar DiskY

X(CCD)

XoffＡT

The position of the pixel≈ The center of FOV of SOT≈ The center of FOV of CCD
The region of the CCD

Figure1: The relationship of the coordinate systems
Black: Heliocentric (AOCS) Coordinate System, Blue: CCD Coordinate System

The notations in the figure are;nxCCD: The coordinate of the CCD pixel (X-axis on CCD coordinate [unit: pixel])
nyCCD: The coordinate of the CCD pixel (Y-axis onCCD coordinate[unit: pixel])
sxCCD: The size of the CCD [unit: pixel]
syCCD: The size of the CCD [unit: pixel]
dnx: The plate-scale of CCD (X [unit: arcsec/pixel]) = “CDELT1” FITS keyword
dny: The plate-scale of CCD (Y [unit: arcsec/pixel]) = “CDELT2” FITS keyword
θ: The offset angle of the Y-axis of heliocentric coordinate system(the X-axis of AOCS coordinate system) and the Y-axis of CCD.

(= “INST_ROT” FITS keyword)
XoffAT: The offset value between the center of FOV of SOT and the center of the CCD(X-axis on the heliocentric coordinate)
YoffAT: The offset value between the center of FOV of SOT and the center of the CCD(Y-axis on the heliocentric coordinate)
XHK2_ATT: The coordinate of the FOV center of SOT on the heliocentric coordinate system (Y)(= Telemetory “HK2_ATT_X”) 1
YHK2_ATT: The coordinate of the FOV center of SOT on the heliocentric coordinate system (X)(= Telemetory “HK2_ATT_Y”)
X: The coordinate of the pixel on the heliocentric coordinate system.
Y: The coordinate of the pixel on the heliocentric coordinate system.
(The colors of the characters correspond with the color of the characters in Figure 1.)
The X and Y are written as following formulas.

syCCD
sxCCD
X = (nxCCD−)dnx cosθ + (nyCCD−)dny sinθ + XoffAT −YHK2_ ATT2
2
Y = (nyCCD −

syCCD

s
)dny cosθ − (nxCCD − xCCD)dnx sinθ + YoffAT − X HK2 _ ATT
2
2<The DC offset (XoffAT, YoffAT) between the FOV center of the SOT-BFI and that of
the other instruments (Preliminary Results 2 ) >The DC offset between SOT and XRTThe following values are the offset of the FOV center of XRT from that of SOT.
Offset E/W direction (XoffAT): -40.4 arcsec (West is positive)
Offset N/S direction (YoffAT): -23.0 arcsec (North is positive)
The DC offset between SOT and EIS 3
The following values are the offset of the FOV center of EIS from that of SOT.
EIS Mirror Configuration: CMIR=892” (mid position), FMIR=1800 (mid position)

1
2
3

Please be careful. The notations are not same as that of the previous version of the document.
see Shimizu_san’s mail “[reformat:00006] Alignment information” on 2006/12/23
The plate scale of XRT is assumed 1.025 arcsec/pix.

Offset E/W direction (XoffAT): -129.6 arcsec (West is positive)
Offset N/S direction (YoffAT): -36.3 arcsec (North is positive)<The telemetry list for the heliocentric coordinate>
The Z-axis of the AOCS coordinate system used for the attitude control is aligned with the FOV
center of SOT. And, “HK2_ATT_?” telemetries indicate the position of the Z-axis of the AOCS
coordinate system. Hence, we can get the position of the FOV center of SOT from “HK2_ATT_?”
telemetries.

Telemetry Name:HK2_ATT_X
APID[HEX]:428
Word[DEC]:275
Number of Bits[DEC]:24[Convart the telemetry to “arcsec”]
XHK2_ATT = 180/223 x 60 x 60 x X(X: Telemetry [DEC])

The telemetry indicates the offset pitch angle 4 of the satellite (the AOCS coordinate system)from the center of the sun based.

Telemetry Name:HK2_ATT_Y
APID[HEX]:428
Word[DEC]:278
Number of Bits[DEC]:24[Convart the telemetry to “arcsec”]
YHK2_ATT = 180/223 x 60 x 60 x X(X: Telemetry [DEC])

The telemetry indicates the offset yaw angle 5 of the satellite (the AOCS coordinate system)from the center of the sun.

5. Information of the observation planNote:
All values of the keywords in the part are inputted to the operational database (TBD) of each
instrument by the chief observer using planning tool. The reformat software has the interface withthe database, and gets the data for the keywords from the database.

4

The picth angle is the angle around the X-axis of the satellite.

5

The yaw angle is the angle around the Y-axis of the satellite.

Header Keyword: OBSTITLE

Format: String

Unit/Option: Free style (one sentence)

Category: SOLAR-B

Data Source: Chief observer or Proposer of the observation

Sample: The temperature analysis of pre-flare site

Description: Title of the observation

Note: The value is decide by the proposer of the observation or at thedaily operation meeting. Chief observer input the value to theplanning tool based on the decision.

Header Keyword: TARGET

Format: String

Unit/Option: Active Region, Quiet Region, Coronal Hole, Flare Site

Category: SOLAR-B

Data Source: Chief observer or Proposer of the observation

Sample: Active Region

Description: Indicate the observation region, not the target phenomenon ofobservation.

Note: 1. The value is decide by the proposer of the observation or at thedaily operation meeting. Chief observer input the value to theplanning tool based on the decision.
2. “Flare Site” only used when the instruments are in FLARE modethat is triggered by the XRT-FLD function. If the instruments
observes a flare in the normal mode, “Flare Site” is not used.

Header Keyword: SCI_OBJ

Format: String

Unit/Option: (see List 1.)

Category: SOLAR-B

Data Source: Chief observer or Proposer of the observation

Sample: AR, AFS, EFL, FL

Description: Indicate the target phenomena (scientific objects) of theobservation. The value is selected from the possible objects andwe can input 5 objects from List 1.
Note: The value is decide by the proposer of the observation or at thedaily operation meeting. Chief observer input the value to theplanning tool based on the decision.

Header Keyword: OBS_DEC

Format: String

Unit/Option: A few sentences. (Free style)

Category: SOLAR-B

Data Source: Chief observer or Proposer of the observation

Sample: Filters and time resolution are optimized for Temperature Analysis.

Description: Describe the properties of the observation

Note: The value is decide by the proposer of the observation or at thedaily operation meeting. Chief observer input the value to theplanning tool based on the decision.

Header Keyword: JOIN_SB

Format: String

Unit/Option: ESX, ES, SX, EX, E, S, X

Category: SOLAR-B

Data Source: Chief observer or Proposer of the observation

Sample: ESX

Description: Indicate the joint observation of the instruments on board
SOLAR-B. If all instruments join the observation, the value is“ESX”, If SOT and EIS join the observation, the value is “ES”. If
the observation uses only XRT, the value is “X”.

Note

: 1. The value is decide by the proposer of the observation or at thedaily operation meeting. Chief observer input the value to theplanning tool based on the decision.
2. The value indicates the planned joint observation. Hence, if theobserved region of EIS is the same as that of SOT incidentally,
the value is not “ES”

Header Keyword: OBS_NUM

Format: Integer

Unit/Option:-

Category: SOLAR-B

Data Source: SOLAR-B Science Coordinator

Sample: 100

Description: All observations using SOLAR-B are numbered by the Solar-B
Science Coordinator, sequentially. The value of “OBS_NUM” is thenumber.

Note: The value is decide at the monthly/weekly operation meeting.
Chief observer input the value to the planning tool based on thedecision.

Header Keyword: JOP_ID

Format: Integer

Unit/Option:-

Category: SOLAR-B

Data Source: SOLAR-B Science Coordinator

Sample: 200

Description: The joint observations between SOLAR-B and the other
instruments (ground-base and satellites) are numbered by the
Solar-B Science Coordinator. The value of “JOP_ID” is thenumber.

Note: The value is decide at the monthly/weekly operation meeting.
Chief observer input the value to the planning tool based on thedecision.

Header Keyword: NOAA_NUM

Format: Integer

Unit/Option:-

Category: SOLAR-B

Data Source: Chief observer or Proposer of the observation

Sample: 11345

Description: The NOAA number of the active region.

Note: If the target region does not have NOAA number, the value is “-1”.

Header Keyword: OBSERVER

Format: String

Unit/Option: LAST First, M.

Category: SOLAR-B

Data Source: Chief Observer

Sample: SHIMOJO Masumi

Description: Name of the Chief Observer

Note: Chief observer input the value to the planning tool.

Header Keyword: PLANNER

Format: String

Unit/Option: LAST First, M.

Category: SOLAR-B

Data Source: Chief PlannerSample: MURPHY Edward, A.

Description: Name of the Chief Planner

Note: Chief observer input the value to the planning tool.

Header Keyword: TOHBANS

Format: String

Unit/Option: LAST First, M. & LAST First M.

Category: SOLAR-B

Data Source: Real-Time (RT) TOHBANs

Sample: NANASHINO Gonbei, HENOHENO Moheji

Description: Name of the RT Tohbans

Note: Chief observer input the value to the planning tool.

6. Information of the data quality

Header Keyword: DATATYPE

Format: String

Unit/Option: SCI, ENG

Category: SOLAR-B

Data Source: Chief Observer

Sample: ENG

Description: Indicates the data for the science or for the engineering test.

Header Keyword: BITCOMPn

Format: Integaer

Unit/Option: 0-7
0: No Bit Compression
1: 16 bits unsigned to 12 bits
2: 14 bits unsigned to 12 bits
3: 16 bits signed to 12 bits
4: 14.5 bits signed to 12 bits
5: 13 bits signed to 12 bits
6: 12 bits unsigned to 12 bits
7: 14 bits unsigned to 12 bits

Category: SOLAR-B

Data Source: Telemetry (Image Header Packet, Word 48 Start bit: 1, End bit: 4)

Sample:0

Description: Indicate that the mode of Bit compression.

Note: “n” is integer. XRT and EIS uses BITCOMP1 (n=1 only). SOT
sometime uses BITCOMP1, BITCOMP2….(n=1,2, …n)

Header Keyword: IMGCOMPn

Format: Integaer

Unit/Option: 0-7

Category: SOLAR-B

Data Source: Telemetry (Image Header Packet, Word 48 Start bit: 5, End bit: 7)

Sample:30: No Image Compression
3: DPCM Compression (lossless compression)
7: DCT Compression (lossy compression):

Description: Indicate that the mode of Image compression.

Note: “n” is integer. XRT and EIS uses IMGCOMP1 (n=1 only). SOT
sometime uses IMGCOMP1, IMGCOMP2….(n=1,2,…n)

Header Keyword: BITC_VER

Format: Integer

Unit/Option:

Category: SOLAR-B

Data Source: Telemetry (Image Header Packet, Word 10 and 11:2 bytes)

Sample:1

Description: The serial number of the bit-compression table.

Note: One SOT/FG file includes some images. And the serial numbers ofcompression tables for each image sometimes are different.
Hence, SOT/FG uses “***VERn” instead of “***_VER”.
“n” is integer that indicates the image number in a SOT/FG file.

Header Keyword: DCHF_VER

Format: Integer

Unit/Option:

Category: SOLAR-B

Data Source: Telemetry (Image Header Packet, Word 12 and 13:2 bytes)

Sample:1

Description: The serial number of the Huffman–DC table for JPEG comp.

Note: One SOT/FG file includes some images. And the serial numbers ofcompression tables for each image sometimes are different.
Hence, SOT/FG uses “***VERn” instead of “***_VER”.
“n” is integer that indicates the image number in a SOT/FG file.

Header Keyword: ACHF_VER

Format: Integer

Unit/Option:

Category: SOLAR-B

Data Source: Telemetry (Image Header Packet, Word 14 and 15:2 bytes)

Sample:1

Description: The serial number of the Huffman–AC table for JPEG comp.

Note: One SOT/FG file includes some images. And the serial numbers ofcompression tables for each image sometimes are different.
Hence, SOT/FG uses “***VERn” instead of “***_VER”.
“n” is integer that indicates the image number in a SOT/FG file.

Header Keyword: QTAB_VER

Format: Integer

Unit/Option:

Category: SOLAR-B

Data Source: Telemetry (Image Header Packet, Word 16 and 17:2 bytes)

Sample:1

Description: The serial number of the Q table for JPEG comp.

Note: One SOT/FG file includes some images. And the serial numbers ofcompression tables for each image sometimes are different.
Hence, SOT/FG uses “***VERn” instead of “***_VER”.
“n” is integer that indicates the image number in a SOT/FG file.

Header Keyword: SAA

Format: String

Unit/Option: IN / OUT

Category: SOLAR-B

Data Source: ISACS-PLN: The SOE (Sequence of Events) file for SAA

Sample: OUT

Description: Indicate that the satellite in SAA or not.

Note

: At the observation planning, the chief planner calculates theenvironments (DAY/NIGHT, SAA, HLZ) of the satellite and puts theresults to ISACS-PLN and the SOLAR-B database. The value ofthe keyword is made from the result of the calculation.

Header Keyword: HLZ

Format: String

Unit/Option: IN / OUT

Category: SOLAR-B

Data Source: ISACS-PLN: The SOE (Sequence of Events) file for HLZ

Sample: OUT

Description: Indicate that the satellite in HLZ or not.

Note

: At the observation planning, the chief planner calculates theenvironments (DAY/NIGHT, SAA, HLZ) of the satellite and puts theresults to ISACS-PLN and the SOLAR-B database. The value ofthe keyword is made from the result of the calculation.

Header Keyword: FLFLG

Format: String

Unit/Option: FLR / NON

Category: SOLAR-B

Data Source: Telemetry (Image data)

Sample: NON

Description: Indicate that the instrument operated on FLARE mode triggered by
XRT-FLD function, or not.

Note

: In the other words, the instrument used the FLARE observing table
or not. Hence, if the instrument observed a flare using the normal
observing table, the value is “NON”.

7. Information of the reformat and etc.

Header Keyword: DATE

Format: String

Unit/Option: UTC / YYYY-MM-DDThh:mm:ss.sss

Category: FITS

Data Source: Reformatter

Sample: 2005-12-02T13:10:11.100

Description: Indicates when the file was made.

Note: The value is rewritten by Level-1, Level-2 Reformatter and thesoftware for data analysis.

Header Keyword: ORIGIN

Format: String

Unit/Option: JAXA/ISAS, NAOJ, MSSL, LMSAL, GSFC....

Category: FITS

Data Source: Reformatter

Sample: JAXA/ISAS

Description: Indicates where the files was made.

Note: The value is rewritten by Level-1, Level-2 Reformatter and thesoftware for data analysis. The keyword of the Level-0 is“JAXA/ISAS” since Level-0 reformat is done at JAXA/ISAS,
basically.

Header Keyword: DATA_LEVFormat: FloatUnit/Option: 0, 1, 2

Category: FITS

Data Source: Reformatter

Sample:0

Description: The level of Data.

Header Keyword: DATE_RF0

Format: String

Unit/Option: UTC / YYYY-MM-DDThh:mm:ss.sss

Category: SOLAR-B

Data Source: Reformatter

Sample: 2005-12-02T13:10:11.100

Description: Indicates when the level-0 reformat was done.

Note: The value of the keyword is the same as that of “DATE” in a
Level-0 file.

Header Keyword: ORIG_RF0

Format: String

Unit/Option: JAXA/ISAS, NAOJ, MSSL, LMSAL, GSFC....

Category: SOLAR-B

Data Source: Reformatter

Sample: JAXA/ISAS

Description: Indicates where the Level-0 reformat was done.

Note: The value of the keyword is the same as that of “ORIGIN” in a
Level-0 file.

Header Keyword: VER_RF0

Format: String

Unit/Option:-

Category: SOLAR-B

Data Source: Reformatter

Sample: SOT_Lev0_Reformatter Ver. 1.0b

Description: The version of the level-0 reformat program.

Header Keyword: DATE_RF1

Format: String

Unit/Option: UTC / YYYY-MM-DDThh:mm:ss.sss

Category: SOLAR-B

Data Source: Reformatter

Sample: 2005-12-02T13:10:11.100

Description: Indicate when the level-1 reformat was done.

Note: The keyword is reserved for Level-1 data file

Header Keyword: ORIG_RF1

Format: String

Unit/Option: JAXA/ISAS, NAOJ, MSSL, LMSAL, GSFC....

Category: SOLAR-B

Data Source: Reformatter

Sample: JAXA/ISAS

Description: Indicates where the Level-1 reformat was done.

Note: The keyword is reserved for Level-1 data file

Header Keyword: VER_RF1

Format: String

Unit/Option:-

Category: SOLAR-B

Data Source: Reformatter

Sample: SOT_Lev1_Reformatter Ver. 2.3c

Description: The version of the level-1 reformat program.

Note: The keyword is reserved for Level-1 data file

List 1: The list of possible objects for “SCI_OBJ” Keyword(The list is made based on IPA “OBJECT” keyword for SOHO.)
AFS :arch filament system
ANE :anemone
AR :active region
ARC :arcade
BP :bright point
CR :coronal rain
CH :coronal hole
COR :corona
CHR :chromosphereCS :coronal streamer
CT :coronal transient
CUS :cusp
DB :disparation brusque
DC :disk center
DFL :disappearing filament
DFX :disapppearing flux
DF :downflow
DSS : delta sunspot
ECL :eclipse
EFR :emerging flux region
EPR :eruptive prominence
EFI :erupting filament
EMB :Ellerman bomb
EVA :evaporation
EVF :Evershed flow
FAC :faculae
FC :filament channel
FLC :flux cancellation
FIL :filament
FLR :flare
FP :footpoint
FS :full sun
FT :flux tube

FL :flow
GR :granulation
JET :jet
LB :loop brightening
LE :loop evacuation
LMB :solar limb
LO :loop
LOO : loop oscillations
CME :coronal mass ejection
MBP : magnetic bright points
MFL :microflare
MS :magnetic shear
MT :Mercury transit
MW :Moreton wave
MMF :moving magnetic features
NET :network
NFL :nanoflare
NL :neutral line
PC :polar crown
PCH :polar coronal hole
PEN :sunspot penumbra
PFL :postflare loops
PHO :photosphere
PLG :plage
POR :pore
PP :polar plumePR :prominence
QS :quiet sun
RIB :two-ribbon flare
SPR :spray
SG :supergranulation
SPI :spicule
SR :surge
SS :sunspot
SSM : sunspot moat
SW :solar wind

SYN :synoptic observation
SEI : Seismology
TR :transition region
UF :upflow
UMB :sunspot umbra
UMD :umbral dots
VT :Venus transit
WAV :wave
WLF :white light flare
XBP : X-ray Bright PointChange Log
Legend:<A>: Add / <C>: Change / <D>: Delete

Ver. 0.6 : by Masumi Shimojo•

Keyword: TIMESYS<C>Unit/Option: UT, UTC, TAI, and etc. → UTC•

Keyword: DATE-OBS<C>Header Keyword: DATE-OBS → DATE_OBS•

Keyword: OBT-TIME<C>Header Keyword: OBT-TIME → OBT_TIME•

Keyword: DATE-END<C>Header Keyword: DATE-END → DATE_END•

Keyword: OBT-END<C>Header Keyword: OBT-END → OBT_END•

Keyword: SCI_OBS<C>Header Keyword: SCI_OBS → SCI_OBJ•

Keyword: OBS_ID<C>Header Keyword: OBS_ID → OBS_NUM<C>Description: The value of “OBS_ID” is the number.
→ The value of “OBS_NUM” is the number.
<D>Note:•

2. The keyword name conflicts with a SOT keyword for “Observable ID”.

Keyword: JOP_ID<C> Data Source: SOHO Science Working Group? →SOLAR-B Science Coordinator<A> Description: The joint observations between SOLAR-B and the other instruments (ground-base andsatellites) are numbered by the Solar-B Science Coordinator. The value of “JOP_ID” is the number.
<C> Note: The keyword is proposed by EIS team. I (Shimojo) can not identify who decide the JOP ID for an
observation. SOHO/SWG? SOLAR-B/SSC? Please teach me the system of JOP numbering.
→ The value is decide at the monthly/weekly operation meeting. Chief observer input the value to theplanning tool based on the decision.

•

Keyword: TOHBANS<C> Data Source : KSC TOHBANs → Real-Time (RT) TOHBANs<C> Description: Name of the KSC Tohbans →Name of the RT Tohbans•

Keyword: DATATYPE<D> Note: The keyword is used to divide the scientific data from engineering data (ex. Dark image, Flat

image, etc...). However, there is not any indicator for the purpose in the image header, now. Hence, we
propose that some serial version numbers of PROGRAM, SEQUENCE and PARAMETER in theobservation table are reserved for the engineering observation, and we use the serial number for dividing
the engineering data.
•

Keyword: BITC_VER<C> Data Source : Telemetry (Image Header Packet, Word 10 and 11:4bits)→Telemetry (Image Header Packet, Word 10 and 11:2bytes)•

Keyword: DCHF_VER<C> Data Source : Telemetry (Image Header Packet, Word 12 and 13:2bits)→Telemetry (Image Header Packet, Word 12 and 13:2bytes)•

Keyword: ACHF_VER<C> Data Source : Telemetry (Image Header Packet, Word 14 and 15:2bits)→Telemetry (Image Header Packet, Word 14 and 15:2bytes)•

Keyword: QTAB_VER<C> Data Source : Telemetry (Image Header Packet, Word 16 and 17:3bits)→Telemetry (Image Header Packet, Word 16 and 17:2bytes)•<A> keyword: NOAA_NUM[Delete the following sentence from the title page.]

Caution:This is the draft of the list of SOLAR-B Mission-Wide FITS Keywords. In the list, there are some conflicts with
the FITS keywords of each instrument. The conflicts will be discussed in SOLAR-B MODA Working Group.

[Change at “Note: Telemetry of AOCS data”]

SOLAR-B loads two UFSSs (UFSS-A and UFSS-B) for redundancy. In nominal case, the data of UFSS-A is similar tothat of UFSS-B. However, you have to use the data of the UFSS that the telemetry “HK2_UFSS-?_USE” is “USE”. Whenthe “HK2_UFSS-?_USE is “NO_USE”, there is possibility that the UFSS is broken.
↓
SOLAR-B loads two UFSSs (UFSS-A and UFSS-B) for redundancy. If you calculate the coordinate from UFSS data, you
use the coordinate data of the UFSS whose telemetry “HK2_UFSS-A(B)_USE” is “USE”. The telemetry“HK2_UFSS-A(B)_USE” indicates which of the UFSSs is used by the AOCS system and guarantees that the UFSS-A(B)operates in normal.
Although the UFSS is not broken, the data of ACU1_UFSS-A_X(Y)ANG_AS is not the same as that of
ACU1_UFSS-B_X(Y)ANG_AS, because there is misalignment between the z-axis of UFSS-A and UFSS-B. Hence, X(Y)

offsethas two values. One is the offset between the z-axis of UFSS-A and the instruments. The other one is the offset

between the z-axis of UFSS-B and the instruments. Hence, you have to use the X(Y) offset for UFSS-A when the“HK2_UFSS-A_USE” is “USE”.

Ver. 0.7 : by Masumi Shimojo•<A> keyword: COMPMOD•

Keyword: INSTRUME<C> Unit/Option: EIS, XRT, SOT/WB, SOT/NB, SOT/SP SOT/CT→

Unit/Option: EIS, XRT, SOT/FG, SOT/SP SOT/CT

Ver. 0.8 : by Masumi Shimojo[List 1: The list of possible objects for “SCI_OBJ” Keyword]•<D> FGL“filigree”•<A> MBP“magnetic bright points”

Ver. 0.9 : by Masumi Shimojo•<D> keyword: COMPMOD•<A> Keyword: BITCOMPn•<A> Keyword: IMGCOMPn•

Keyword: NOAA_NUM<A> Note•: If the target region does not have NOAA number, the value is “-1”.

Keyword: BITC_VER, DCHF_VER, ACHF_VER, QTAB_VER<A> Note: One SOT/FG file includes some images. And the serial numbers of compression tables for each
image sometimes are different. Hence, SOT/FG uses “***VERn” instead of “***_VER”. “n” is integer thatindicates the image number in a SOT/FG file.

Ver. 0.91: by Masumi Shimojo•<D> keyword: EXPTIME: I delete the keyword from the list since EIS do not use EXPTIME keyword.
(The exposure time of EIS will be kept in the binary table extension.)•<M> Telemet: HK2-UFSS-A_USE APID 440 -> APID 428, Word 221 -> 211•<M> Telemet: HK2-UFSS-B_USE APID 440 -> APID 428, Word 221 -> 211

Ver. 1.0: by Masumi Shimojo•<D> Note: Telemetries of AOCS data (There are some large bugs in the expressions).
See “Erratum of The List of SOLAR-B “Hinode” Mission-Wide keywords / Section: Note: Telemetry of AOCS
data”.

Ver. 1.2: by Masumi Shimojo<C> change the conversion formulas that described how to convert from the UFSS telemetries to the sunangles.
Ver. 1.3: by Masumi Shimojo<C> change “Note :Telemetry of AOCS data” based on Shimizu_san’s mail on 2006/12/23.