In-flight performance of pulse-processing system of the ASTRO-H/Hitomi soft x-ray spectrometer

Abstract. We summarize results of the initial in-orbit performance of the pulse shape processor (PSP) of the soft x-ray spectrometer instrument onboard ASTRO-H (Hitomi). Event formats, kind of telemetry, and the pulse-processing parameters are described, and the parameter settings in orbit are listed. The PSP was powered-on 2 days after launch, and the event threshold was lowered in orbit. The PSP worked fine in orbit, and there was neither memory error nor SpaceWire communication error until the break-up of spacecraft. Time assignment, electrical crosstalk, and the event screening criteria are studied. It is confirmed that the event processing rate at 100% central processing unit load is ∼200  c  /  s  /  array, compliant with the requirement on the PSP.

In-flight performance of pulse-processing system of the ASTRO-H/Hitomi soft x-ray spectrometer 1

Introduction
The ASTRO-H 1 (named Hitomi after launch on February 17, 2016) is the sixth Japanese x-ray astronomy satellite and was developed under international collaboration of Japan, United States, Europe, and Canada. The pulse shape processor [2][3][4] (PSP) is a digital signal-processing electronic for the microcalorimeter instrument, soft x-ray spectrometer 5 (SXS) onboard ASTRO-H. The SXS has 36 sensor pixels, which are operated at 50 mK to measure heat input of x-ray photons and realizes energy resolution of full-width at half-maximum (FWHM) < 7 eV in 0.3 to 12.0 keV. Receiving digitized waveform (14 bit, 12.5 kHz sample) from 18 channels apiece, two identical units of PSP-A and -B trigger x-ray events, assign an event grade, and perform optimal filtering to measure energy deposit on the microcalorimeter pixels. This paper describes results of the initial in-orbit performance of the PSP as well as the related technical details.

Overview of the PSP
The PSP is a digital signal processor of the SXS, and it has following functions: • To process continuously the digitized waveform from the detector system.
• To receive commands from the spacecraft.
• To output the house-keeping (HK) telemetry, the event telemetry, and the diagnostic telemetry to the spacecraft.
• To calculate noise spectra, average pulses, and templates (see Sec. 3.2) of the detector.
It is requested to the PSP to make full use of the detector performance in terms of energy resolution, event triggering and grading, time-assignments, background/crosstalk rejection, counting capability, etc. Particularly for the counting capability, processing more than 150 c/s/array of the incoming x-rays is required to the PSP. The PSP realizes these functions and requirements in combination of its hardware and the onboard software. The basic algorithm of the x-ray pulse processing in the PSP is described in a separate paper. 3 The processing algorithm of the PSP follows that of the calorimeter digital processor for the Suzaku XRS. 6,7 However, the PSP is implemented on a completely different hardware. In Fig. 1, we show a block diagram of the PSP. The analog signals from the x-ray microcalorimeter detector are amplified and digitized by the analog-to-digital signal processing unit called the x-ray amplifier box (XBOX). The digital data are transferred to the PSP via low voltage differential signal (LVDS) lines with sampling rate of 12.5 kHz. The data contain stream of the 14-bit adc_sample, which is a raw value sampled by the analog-to-digital converter (ADC) in the XBOX. From the stream of the adc_sample, the PSP calculates the 16bit derivative by applying a boxcar filter, and the derivative is used for the triggering. Both the adc_sample and the derivative are stored in a buffer memory named waveform ringbuffer (WFRB) in the PSP. The size of the WFRB is 1 MB containing 2 18 ¼ 262;144 samples (20.97152 s in 12.5 kHz) for each pixel.
The PSP has two electrically identical hardware: PSP-A and PSP-B. One PSP processes the continuous data of 18 channel (from the microcalorimeter pixels) and 1 channel (from the anticoincidence sensor) sequence units, triggers discrete pulses and noise records from the data stream. The hardware design of each PSP consists of a field-programmable gate array (FPGA) board, two central processing unit (CPU) boards, and a power supply board. These boards are developed by JAXA and Mitsubishi Heavy Industries, Ltd. The communication between the FPGA board and the CPU board uses the SpaceWire protocol, which is the standard high-speed serial communication in satellites based in part on the IEEE 1355. Table 1 shows hardware specifications of the FPGA board and the CPU board. Telemetry from the PSP is edited into Space Packets, which is the standard protocol for satellites by the Consultative Committee for Space Data Systems, and they are transferred to the satellite management unit (SMU) or the data recorder (DR) via SpaceWire. We assume all the Space Packets shall be downlinked to the ground station (Uchinoura Space Center), although we have to select and prioritize the Space Packets because the capacity of the DR is limited and shared with other mission instruments. See the next paragraph in detail. Commands are transferred from the SMU to the PSP. The PSP also relays commands to the XBOX and telemetry from the XBOX.
The list of telemetry packets from the PSP is shown in Table 2. A single Space Packet is identified by a combination of three identifier numbers, namely, application process identifier (APID), lower function object identifier (FOID) (Upper FOID is equivalent of lower 8 bit of APID.), and Attribute ID. APID ¼ 0x02∕0x05 is assigned for SMU-A/B, APID ¼ 0x40∕44∕48∕4C for PSP-A0/A1/B0/B1, and APID ¼ 0x 47∕4F for XBOX-A/B. The maximum size of a Space Packet is 1024 octets for ASTRO-H; however, it is allowed to generate a longer spacecraft monitor and control protocol (SMCP) message up to 0xFFFFFF ¼ 16;777;215 octets, which is segmented into multiple Space Packets. Lower 32-bits of the time counter of the spacecraft (L32TI) in units of 1∕64 s ¼ 15.625 ms is attached in the secondary header of each Space Packet. The time counter of the spacecraft is 38-bits long. The upper 32-bits of the time counter (U32TI) is in units of 1 s, and its origin (U32TI = 0) is the same as that of the global positioning system (GPS), 1980-01-06 00:00:00 UTC, when the spacecraft time is synchronized with the GPS. There is a 7-bit value (0x00 to 0x7F) named "Category" in the secondary header of a Space Packet, which is used as priority in recording the packet to the DR. The value of 0x7F is the lowest priority, meaning that the packet is only telemetered in real-time downlink and shall not be recorded in the DR. The HK packets of ESHK2 and SYS/USR/XBOX/STATISTIC HK are generated periodically as indicated by the column of "Period." In order to save the capacity of the DR (1.5 GB), categories of SYS/USR/XBOX HK are dynamically changed in four cycles by the PSP. We also changed the category of PULSEREC to lower priority and changed those of AVGPULSE, NOISESPC1K, TEMPLATE, WFRB DUMP, and NOISESPC8K to higher priority by sending commands to the PSP in orbit. The PSP has many parameters for the pulse-processing, and the list of major parameters is shown in Table 3.
The PSP has a function to grade (Fig. 2) pulses into highresolution primary (Hp), medium-resolution primary (Mp), medium-resolution secondary (Ms), low-resolution primary (Lp), or low-resolution secondary (Ls). The definition of each grade is listed in Table 4, in which only two values of the t p (time-interval to the previous pulse) and the t n (time-interval to the next pulse) are used. The meaning of the "primary" and the "secondary" does not relate to a distinct physical process, but they just denote there is a triggered event in a specified time-interval for t p (secondary) or not (primary). The PSP evaluates the detected pulses using the optimal filtering methods to produce an event record of 96 bits (12 octets). Contents of the event record for each microcalorimeter pixel is shown in Table 5. The template length for the optimal filtering is 1024 samples (81.92 ms) for Hp and 256 samples (20.48 ms) for Mp/Ms. The PSP has a special mode, FORCE_MIDRES_ TMPL = enabled (1:ENA) for each pixel, in which the short template is applied to Hp events for the calibration purpose. The Lp/Ls events are only calculated for LO_RES_PH without optimal filtering. Up to 80 event records are merged into a Space Packet, and it is transferred to the DR.  There are two kinds of pseudoevents, baseline (BL) and event-lost (EL). The BL pseudoevent is coupled with the telemetry type of "noise record," for which the PSP periodically collects a waveform in quiescent time (absolute value of the derivative is less than a parameter, NOISE_THRES, for an interval of NOISE_CLEAN_LEN = 2048 samples, in Table 3) and calculate the zero-level of PHA in a signed integer (−32;768 to þ32;767). The TRIG_LP, LO_RES_PHA, and DERIV_MAX correspond to the first sample of the noise record, and QUICK_ DOUBLE, SLOPE_DIFFER, RISE_TIME, TICK_SHIFT, and TIME_VERNIER become 0. The EL pseudoevent means that the PSP cannot process all of the events due mostly to high Category ranges from 0x00 to 0x7F, used as priority in the DR. The value of 0x7F is the lowest, which is only telemetered in real-time downlink and shall not be recorded in the DR. c ADR Controller, ADRC; shield cooler driver, SCD; precooler driver, PCD; Joule-Thomson cooler driver, JTD; soft x-ray imager cooler driver, SXI-CD; filter wheel electronics, FWE.
Journal of Astronomical Telescopes, Instruments, and Systems 011217-3 Jan-Mar 2018 • Vol. 4(1) Length in tick to judge slow-pulse events. Condition of (ticks from the trigger point to DERIV_MAX < SLOPE_DETECT_LEN) && (ticks from the trigger point to zero-crossing < 2 × SLOPE_DETECT_LEN) must be satisfied for normal events. A primary pulse judged as the slow-pulse is set the most significant bit (MSB) of RISE_TIME to 1 (RISE_TIME > 128). A secondary pulse judged as the slow-pulse shall be discarded, and SLOPE_DIFFER is set to 1 for the primary pulse. SLOPE_DETECT_LEN = 20 corresponds to 1.6 ms.  Contents of the event record for the anticoincidence sensor (antico) are shown in Table 6. There are BL (FLG_BASELINE = 1) and EL (FLG_EVENT_LOST = 1) pseudoevents for the antico events, too. The BL pseudoevent for the antico is generated by random sampling in 1 Hz. The EL pseudoevent for the antico is only sent when the EDB overflows in the FPGA (125 stages of FIFO read by 8 Hz, corresponding 1000 c∕s). The structure of the event record for the EL for the antico is the    Table 3. 3 In-Orbit Operation of the PSP

Operation in Orbit
In-orbit operation of the SXS is summarized in Ref. 8 Table 3) from 120 to 75, which is equivalent to ∼166 and ∼104 eV, respectively, in energy, at 2016-03-02 04:00 UTC. Figure 3 shows comparison of 5-σ thresholds determined using the WFRB DUMP telemetry. The only significant change from the ground testing to the values in orbit is PIXEL = 33. It did not ring (The adc_sample oscillates in a certain frequency.) on the ground, whereas it was ringing in orbit, similar to PIXEL = 26 and 27, for which ringing was seen on the ground. We set the antico thresholds at 25 (∼10 keV) for both PSP-A and -B from the ground testing and kept them unchanged in orbit. Both PSP-A and -B worked fine in orbit, and there was no memory error nor SpaceWire communication error until the break-up of spacecraft on 2016-03-26 UTC. Table 3 summarizes the parameter setting of the PSP in orbit. In order to protect the sensor and the adiabatic demagnetization The quick-double flag indicating that derivative increased again in the FALL state of the pulse detection in FPGA.

SLOPE_DIFFER 1
The slope-differ flag indicating that slope of the derivative is different from the average derivative (a slow-pulse is found in the residual). The slow-pulse found in the slope shall be discarded. SLOPE_DIFFER becomes always 1 for x-rays with its energy larger than ∼15 keV.

LO_RES_PH 14
The low-resolution pulse height (0 to 16,383), determined by the maximum value of the raw pulse.

DERIV_MAX 16
The maximum value of derivative. This is signed value, ranging from −32;768 to þ32;767. refrigerator (ADR) from He-leak into the vacuum shield of the SXS dewar (DWR), we set parameters of JFET_HTR_VIN_ THRES = JFET_HTR_VOUT_THRES = 10 V for the autonomous (AT) function of the SMU. In such case, thermal conduction of the junction field-effect transistor (JFET) through the He gas become larger, and the JFET heater power to keep it at 130 K becomes higher. The PSP monitors the values of the heater powers named JFET_HTR_VIN/VOUT in the XBOX HK. When they become larger than these thresholds, the PSP sets a flag in the ESHK2 telemetry. The SMU monitors this flag in the ESHK2 telemetry and sends the registered AT command, which aborts sequencers of the ADR controller (ADRC) and disables the XBOX amplifiers to prevent the permanent damage to the sensor and the ADR.

Template for Optimal Filter
The average pulses (for both the adc_sample and the derivative with a record-length of 1024 samples) and the H-and M-resolution templates (record-lengths of 1024 and 256 samples, respectively) in orbit are the same as those used in the ground testing. Inside the PSP algorithm, the M-resolution template is a cut-out of the H-resolution template, considering the difference of the record-lengths and the pretrigger lengths (PRE_ TRIG_LEN_H = 140, PRE_TRIG_LEN_M = 27 in Table 3). The H-resolution template for each pixel is calculated from the the average pulse and the noise spectrum. The PSP has functions to collect them and to calculate the templates by the onboard software. It is also possible to upload the average pulses and templates calculated by off-line from the ground station to the PSP. It is unlikely to change the x-ray pulse shape; however, the noise environment may change in orbit. On the other hand, the nonlinearity of PHA (Table 5) and the time-assignment of the events (see Sec. 3.3) are affected by the template. We therefore decided to use the same templates, which is calculated in ground, also in orbit, as far as the degradation in orbit is within the energy resolution budget. In the case of ASTRO-H/Hitomi, the energy resolution at 5.9 keV was 4.43 eV (FWHM) at the subsystem test, 4.79 eV at the spacecraft thermal vacuum test, and 4.94 eV in orbit. 9 The degradation was within the energy resolution budget so that we used the same templates throughout the operation on-ground to in-orbit.   The flight templates were taken at Tsukuba Space Center in the subsystem test of the SXS on 2015-03-10 13:04 17:10 UTC and were written to the electrically erasable programmable readonly memory (EEPROM) of PSP-A0/A1/B0/B1 on ground. At that time, the major part of the SXS was the flight-model (FM), namely the DWR, electrical harnesses, XBOX, ADRC, power supply unit, shield cooler driver (SCD), precooler driver (PCD), and Joule-Thomson cooler driver (JTD) were FM, and PSP-A/B and SXS SpaceWire Router A (SXS-SWR-A) were the engineering model. The SXS-SWR-B, filter wheel electronics (FWE), and SXS power distributer (SXS-DIST) were absent. We irradiated Mn-K α x-rays (5.9 keV) to all the microcalorimeter pixels. The x-rays were made on the secondary Mn target irradiated by an x-ray generator mounted on the DWR and came into the microcalorimeter pixels (except for the calibration pixel, PIXEL = 12) through the gate-valve of the DWR, which has an entrance window made of 300 μm of Be. The calibration isotope 55 Fe attached on the detector assembly was used for the calibration pixel. At that time, the event thresholds were set to lower values of 50 than those in-orbit (125 or 75) for most of pixels. The thresholds were 70 for PIXEL = 8, 27, and it was 200 for PIXEL = 26. The difference of the event thresholds among pixels affects the time-assignment, which is described in the next section.

Time Assignment
There are several remarks on the time-assignment of the events for both the microcalorimeter pixels and the antico. The timecoincidence among the pixels and the antico is important for rejecting non-x-ray background events, and the requirement on the PSP is that the relative timing accuracy (The "relative timing" means that it just applies to the time-coincidence between the pixels and the antico, and it does not apply to difference from the astronomical absolute time.) <80 μs. However, there exist systematic shifts in the time-assignment among the event grades (Hp, Mp/Ms, and Lp/Ls) and that between the pixels and the antico. Triggering a pulse candidate is done in the FPGA, and the way of triggering is different between the pixels and the antico. The pixel events are triggered when the calculated derivative using a boxcar filter of DERIV_HALF_ LEN_P nn = 8 ticks exceeds the PULSE_THRES_P nn in Table 3. On the other hand, the antico events are triggered when the adc_sample exceeds the (AC_PULSE_THRES + AC_ADC_SAMPLE_PEDESTAL). The time-assignment of the antico is done using the triggered time, which is stored as TRIG_LP in Table 6. The time-assignment of the microcalorimeter pixels depends on the event grades. With regard to Hp, the adc_sample is cross-correlated with the H-resolution template within the range of −8 (= MIN_SHIFT_ BACKWARD) < TICK_SHIFT < + 7 (= MAX_SHIFT_ FORWARD), and the maximum is searched. When the maximum is found, the CPU conducts the parabolic fit using the three samples around the maximum and calculates TIME_ VERNIER in time-resolution of 1/16 tick ¼ 5 μs. If the maximum is not found (TICK_SHIFT = −8 or +7), TIME_ VERNIER is set to 0. The triggered time is shifted by the value of TICK_SHIFT, and it is stored as TRIG_LP in Table 5. With regard to Mp/Ms, the time-assignment is similar to Hp but for using the M-resolution template. With regard to Lp/Ls, time of the derivative maximum (derivative = DERIV_MAX) is assigned for TRIG_LP and TIME_VERNIER = 0. Therefore, time for Hp/Mp/Ms is assigned so that the obtained pulse record becomes the best match for the template, referring to the time origin of the template. The time origin of the template is the FPGA trigger time in making the average pulse in the template generation. This means that the timeassignment of Hp/Mp/Ms among pixels does not depend on the event threshold in the actual observation, but it slightly depends on that in the template generation. With regard to Lp/Ls, which use the time of DERIV_MAX, it does not depend on the event threshold, and there is a systematic delay compared with Hp/Mp/Ms. The delay was evaluated as 11.625 tick ¼ 0.93 ms on ground using the spacecraft thermal-vacuum test on 2015-06-25. Because the event threshold for PIXEL = 26 was four times higher than those for other pixels in the template generation, a delay of 1.625 tick ¼ 0.13 ms was seen in Hp/Mp/ Ms events for PIXEL = 26. There is a delay in the antico event, too, and it is slightly dependent on the antico event threshold and the energy input to the antico sensor (Si PIN). The delay was evaluated as 0.24 ms on ground, by checking a distribution of Δt = (antico time) − (pixel time) for the cosmic-ray events. Parameters of these corrections for the delays are incorporated into the calibration database (CALDB) file, ah_sxs_coefti-me_20140101v001.fits.
In addition to the relative time differences, we observed a time delay of Hp events from the expected irradiation of the modulated x-ray source (MXS), which consists of four x-ray generators for gain calibration attached to the housing of the filter wheel mechanics. The observed delay was ∼160 ms, and it is due mainly to specification of latching the spacecraft time in the FWE, namely the time of irradiation start is recorded as 1∕64 s ¼ 156.25 ms ahead. The remaining delay was evaluated as 0.445 AE 0.022 ms on ground using the spacecraft thermal-vacuum test on 2015-06-25. This delay consists of both systematic shift of time-assignment in the PSP and delay in the digital and analog circuits in the FWE/MXS, although we cannot separate them because there are no ground measurements.
We also found a very small shift of the time-assignment up to ∼20 μs depending on the DERIV_MAX or RISE_TIME, although we cannot separate their effect on the time-assignment, because there is a clear correlation between DERIV_MAX and RISE_TIME for normal events. This is due mainly to the slight distortion of the pulse shape (ratio of pulse-height to the input energy becomes lower for x-rays with higher energy) due to the microcalorimeter physics. Parameters for the time correction were evaluated with in-orbit data, especially using the Crab pulsar. The latest CALDB file takes into account the DERIV_MAX dependence and the absolute timing by comparing the SXS observation with the radio-band observation of the Crab pulsar. Figure 4 shows distributions of events in RISE_TIME, DERIV_MAX, and TICK_SHIFT plotted versus the energy of pulse invariant (EPI) in units of keV. The EPI is the best estimate of the input energy of each x-ray pulse, and its value is calculated from PHA in Table 5 with polynomials, considering pixel-to-pixel difference of nonlinear energy scale and the temporal gain drift. 10 Events plotted in this figure are obtained in the observation of G21.5-0.9 (Crab-like supernova remnant) in orbit. Because the gate-valve with an entrance window of ∼300 μm Be is closed, almost no x-rays below ∼1 keV come into the microcalorimeter pixels through the gate-valve.

Distribution of Events and Screening for X-Rays
However, there is an electron-loss continuum (flat tail at low energy side in the line-spread function) due to the escape of electrons with small energy from the HgTe absorber, and those events show similar responses to the low energy x-rays, which are photoelectrically absorbed in the microcalorimeter. Normal x-ray events distribute in the range of 40 ≲ RISE_ TIME ≲ 60 (3.2 to 4.8 ms) in the RISE_TIME versus EPI plot. The RISE_TIME becomes slightly smaller when EPI becomes larger; therefore, it is better to screen events with EPI-dependent range for RISE_TIME in order to reduce nonx-ray background events. There is an upper branch in the energy range of 9 to 12 keV, which is a pile-up of Mn-K α x-rays for the calibration pixel. There is a lower branch in 3.5 to 6 keV with Ls events, which is the Mn-K α x-rays on the slope of a previous pulse. There is a cluster of Lp events with RISE_TIME ∼20 (1.6 ms) below ∼2 keV, which is the direct hit of the Si thermistor. Most of them are also flagged as SLOPE_DIFFER. There are many events at low energy below ∼0.5 keV, and most of them are electrical crosstalks from other pixels or the antico. There are several events with longer RISE_TIME with QUICK_ DOUBLE = 1 in the wide energy range, which are pile-up events. Events with shorter RISE_TIME with SLOPE_ DIFFER = 1 in the wide energy range are probably due to electrical interference with the attitude control system, e.g., magnetic torquer or reaction wheel, and/or the power system of spacecraft, e.g., battery charge control unit, which were seen in the ground testing.
Most of the electrical crosstalk events have small EPI (< 0.1 keV) and short RISE_TIME (< 40); however, they appear to have broad tail in the RISE_TIME distribution, and EPI can have ∼0.5 keV. We can remove the electrical crosstalk events possibly better by setting a condition on the EPI versus DERIV_MAX plane and rejecting TICK_SHIFT = −8 or 7.
With regard to the TICK_SHIFT distribution, TICK_SHIFT is almost within AE1 for normal x-rays in EPI > 3 keV, although it becomes smaller below ∼2 keV. This is because the FPGA trigger point shifts forward at low energy. We note that a significant fraction of normal x-ray events above ∼12 keV is flagged as SLOPE_DIFFER = 1. This is already known on ground in the calibration of the high energy band, and it is because the pulse shape of high energy x-rays is slightly distorted from the average pulse, and the residual in the slope is judged as the slow-pulse. See description of RISE_TIME in Table 5 for definition of the slow-pulse. The dynamic range of the XBOX and the PSP is designed as ∼30 keV, and one should not apply screening condition for SLOPE_DIFFER to analyze x-rays above ≳12 keV.

CPU Load and Event Rates
Idle time of the CPU at every second, and the FPGA trigger rate at every 16 s for each pixel are contained in the STATISTIC HK (Table 2). Figure 5 shows plots of the CPU load fraction calculated from it, event rates of pixels with PSP-A0 (PIXEL = 0 to Fig. 5 Plots of the CPU load fraction, the live-time fraction, all events rate, the Hp event rates, the Mp + Ms event rates, the Lp + Ls event rates, and the antico rate in observing the Crab nebula. The gray hatches show eclipses (occultation of boresight with the Earth), and the pink hatches show the SAA. In the top panel, the actual CPU load fraction in the HK telemetry is drawin in black, and the estimated fraction is drawn in red (see Sec. 3.5). In the second to fifth panels, PSP-A0 events from PIXEL = 00 to 08 are plotted in different colors. In the bottom panel, the total event rate of the antico is drawn in black, and the event rate with PHA >30 keV is drawn in red.
Journal of Astronomical Telescopes, Instruments, and Systems 011217-11 Jan-Mar 2018 • Vol. 4(1) 8), and the A-side of the antico rate with PSP-A1, in the observation of the Crab nebula on 2016-03-25 UTC. Gray hatches show eclipses (occultation of boresight with the Earth), and pink hatches show the south Atlantic anomaly (SAA). Since the Crab nebula is moderately bright through the gate-valve, the CPU load fraction becomes almost 100% and the livetime fraction becomes lower for the central pixel (PIXEL = 0) during the on-source observation (nonhatch). The processing rate at 100% CPU load is ∼200 c∕s∕array in sum of PSP-A0/ A1/B0/B1, which is compliant with the requirement on the PSP, namely to process events >150 c∕s∕array, if we ignore the electrical crosstalk. The antico rate also increases during on-source, because a small fraction of x-rays above the antico threshold of 10 keV comes into the antico through the gap of the HgTe absorber, and/or the absorber becomes transparent to higher energy xrays. This fraction of the antico events is negligible above 30 keV; therefore, we recommend using the antico events with PHA > 75 ∼ 30 keV to reject cosmic-rays by time-coincidence with the antico events, as well as to judge the condition of the SAA. The antico rate increases dramatically at the SAA, and we set the SAA condition as the antico rate above 30 keV is larger than 3 c∕s in a sliding cell of 32-s width.
The event rates of pixels increase at the SAA, too. Figure 6 shows the pixel maps of the FPGA event rate. There is electrical crosstalk from A-side of the antico to PIXEL = 8 and 17 and from B-side of the antico to PIXEL = 26 and 35. Figure 7 shows the branching ratios of the event grades using all pixels, where the FPGA event rate was maximum, when observing the Crab nebula. The ratios match well with the theoretical expectation assuming random trigger. Figure 8 shows the pixel maps of the CPU event rate when observing the Crab nebula. Central pixels of PIXEL = 0, 17, 18, and 35 were affected by limitation of the 100% CPU load (so called the PSP-limit), and the EL pseudoevents were seen in the telemetry. These pixels are also affected by the branching ratio, and the event rate of Fig. 6 Pixel maps of the FPGA event rate in units of c/s/pixel at eclipse by the Earth, at the SAA with eclipse, in observing the Crab nebula, and at the SAA with observing the Crab nebula. In each pixel, the pixel number (P nn), the A/B-side channel (A nn or B nn), and the count rate are labeled in three lines. The left bottom pixel labeled with "P12" is the calibration pixel (PIXEL = 12). The left middle pixels labeled with "acB" and "acA" denote the antico events read by PSP-A or PSP-B.
Journal of Astronomical Telescopes, Instruments, and Systems 011217-12 Jan-Mar 2018 • Vol. 4 (1) Hp + Mp is much lower than outer pixels. The live-time fraction for outer pixels was nearly 100%, including the calibration pixel.
We evaluated what fraction of the CPU load is consumed for the event processing. We constructed a simple model for each 64-s bin, and fitted the model to the in-orbit data at the SAA on 2016-03-16 25 UTC with (CPU load) <1.0 at the peak, which we call the "small SAA." Fits results are summarized in Table 7. The e ¼ 0.06599 means that the base load is ∼6.6%. The estimated CPU load using this model is plotted in Fig. 5 with a red line at the top panel. It almost reproduces the overall shape of the actual CPU load, except for the first part around 12:00 where the event file is lacking, and time around 15:00 where noise measurements were done. The PSP-limit with this model corresponds to ∼200 c∕s∕array, which matches the actual observation.   Until the break-up of the Hitomi satellite, the SXS worked very well, which has enabled revolutionary science. The following is a summary of topics described in this paper.
• Both PSP-A and -B worked fine in orbit, and there was no memory error nor SpaceWire communication error, even with many passages of the SAA. Lists of telemetry packets, pulse-processing parameters in orbit, definition of the event records for the microcalorimeter pixels, and definition of the anticoincidence sensor are shown in Tables 2-6.
• We used the same templates for optimal filter throughout the operation on-ground to in-orbit, because degradation of the energy resolution (FWHM ¼ 4.94 eV at 5.9 keV in orbit) was within the energy resolution budget.
• There are systematic shifts in the time-assignment among the event grades (Hp, Mp/Ms, and Lp/Ls) and that between the microcalorimeter pixels and the anticoincidence sensor. They are incorporated into the CALDB file.
• Distributions of events in RISE_TIME, DERIV_MAX, and TICK_SHIFT plotted versus EPI (in units of keV) show interesting features such as pile-ups and electrical crosstalks, and they are used to determine the screening criteria for normal x-ray events rejecting the background/crosstalk events.
• The event rates and the pixel maps during observation of the Crab nebula demonstrate the counting capability of the PSP for bright objects, as well as the reconstruction of the GTI using the EL pseudoevent. The performance of PSP is confirmed in orbit, particularly for the event processing rate of ∼200 c∕s∕array.

Disclosures
The authors have no relevant financial interests in the manuscript and no other potential conflicts of interest to disclose.