The Ultraviolet Spectrograph on NASA’s Juno Mission

  • G. Randall Gladstone
  • Steven C. Persyn
  • John S. Eterno
  • Brandon C. Walther
  • David C. Slater
  • Michael W. Davis
  • Maarten H. Versteeg
  • Kristian B. Persson
  • Michael K. Young
  • Gregory J. Dirks
  • Anthony O. Sawka
  • Jessica Tumlinson
  • Henry Sykes
  • John Beshears
  • Cherie L. Rhoad
  • James P. Cravens
  • Gregory S. Winters
  • Robert A. Klar
  • Walter Lockhart
  • Benjamin M. Piepgrass
  • Thomas K. Greathouse
  • Bradley J. Trantham
  • Philip M. Wilcox
  • Matthew W. Jackson
  • Oswald H. W. Siegmund
  • John V. Vallerga
  • Rick Raffanti
  • Adrian Martin
  • J.-C. Gérard
  • Denis C. Grodent
  • Bertrand Bonfond
  • Benoit Marquet
  • François Denis
Open AccessArticle

DOI: 10.1007/s11214-014-0040-z

Cite this article as:
Gladstone, G.R., Persyn, S.C., Eterno, J.S. et al. Space Sci Rev (2014). doi:10.1007/s11214-014-0040-z


The ultraviolet spectrograph instrument on the Juno mission (Juno-UVS) is a long-slit imaging spectrograph designed to observe and characterize Jupiter’s far-ultraviolet (FUV) auroral emissions. These observations will be coordinated and correlated with those from Juno’s other remote sensing instruments and used to place in situ measurements made by Juno’s particles and fields instruments into a global context, relating the local data with events occurring in more distant regions of Jupiter’s magnetosphere. Juno-UVS is based on a series of imaging FUV spectrographs currently in flight—the two Alice instruments on the Rosetta and New Horizons missions, and the Lyman Alpha Mapping Project on the Lunar Reconnaissance Orbiter mission. However, Juno-UVS has several important modifications, including (1) a scan mirror (for targeting specific auroral features), (2) extensive shielding (for mitigation of electronics and data quality degradation by energetic particles), and (3) a cross delay line microchannel plate detector (for both faster photon counting and improved spatial resolution). This paper describes the science objectives, design, and initial performance of the Juno-UVS.



1 Introduction

Juno-UVS, the ultraviolet instrument on the Juno mission to Jupiter, is primarily based on the Alice instrument on the New Horizons (NH) mission to the Pluto system and on the Lyman Alpha Mapping Project (LAMP) instrument on the Lunar Reconnaissance Orbiter (LRO) mission currently in orbit around the Moon. Juno-UVS is an imaging spectrograph with a spectral range in the extreme-ultraviolet (EUV) and far-ultraviolet (FUV) of 68–210 nm. This wavelength range was chosen to cover all important UV emissions from the H2 bands and the H Lyman series produced in Jupiter’s auroras, while also including longer wavelengths sensitive to the absorption signatures of aurora-produced hydrocarbons. Juno-UVS will remotely sense Jupiter’s auroral morphology and brightness, providing context for in-situ measurements, and will map the mean energy and flux of precipitating auroral particles.

The Juno-UVS instrument was developed at SwRI and delivered to Lockheed Martin for integration onto the Juno spacecraft before launch on August 5, 2011. The instrument consists of two main assemblies: (1) a shoebox sized sensor, which includes a telescope section and a spectrograph & detector section, and (2) an electronics box housed in the spacecraft vault. Besides this changed configuration (LRO-LAMP and the Alices each consisted of a single assembly), a number of changes have been incorporated to adapt the instrument to the Juno mission. A main design driver for these differences is Jupiter’s harsh radiation environment. Another major change is the addition of a scan mirror, which allows the targeting of specific areas of interest when the spinning spacecraft is close to Jupiter. In the following sections we present the design and operation, the key changes from earlier designs, calibration results, and initial in-flight results for Juno-UVS, but we first begin with an overview of the science planned for Jupiter.

2 Scientific Objectives

Juno-UVS’s main objective is to provide context for the particles and fields instruments (i.e., JADE, JEDI, Waves, and MAG) in the investigation of Jupiter’s polar magnetosphere (Fig. 1). During the typically 6-hour near-perijove period of auroral observations, Juno-UVS will scan Jupiter’s auroral regions once per 30-s spacecraft spin to observe the morphology, brightness, and spectral characteristics of Jupiter’s far-ultraviolet (FUV) auroral emissions, which are primarily comprised of the Lyman series of H and the Lyman, Werner, and Rydberg band systems of H2. By obtaining time-tagged pixel list data (where each photon event is assigned a unique location, wavelength, and time), images and maps of the northern and southern auroral regions will be reconstructed on the ground at a resolution appropriate for the signal-to-noise ratio (SNR) of the spectral feature of interest. Near the beginning and end of the near-perijove observation period Juno-UVS will provide global snapshots of the northern and southern auroral morphology from a range of several Jovian radii. Closer to Jupiter, a scan mirror will be used to target the atmospheric region near the expected location of the Juno magnetic field line footprint (based on magnetic field models and the spacecraft orbit and spin axis). This will allow a direct comparison of the precipitating particle fluxes measured by JADE and JEDI with the FUV emissions they produce upon impacting Jupiter’s upper atmosphere, and how the particular region sampled by the spacecraft relates to the rest of the magnetosphere. Other frequent targets will be the magnetic field line footprints of the Galilean satellites (at a variety of local times and from near nadir to positions near the limb), the polar flares, and the main oval ansae (i.e., the locations where the main oval emission cross the limb). During MWR orbits (when the Juno spin and orbit planes coincide), the Juno-UVS scan mirror will be used much less, so that simultaneous FUV data will be acquired from the same auroral regions observed by the JIRAM near-IR instrument.
Fig. 1

Artist conception of Juno in orbit about Jupiter, with aurora emissions prominently displayed. While each ∼5000-km altitude perijove occurs at relatively low latitudes, many auroral observations will be taken from within one Jovian radius (RJ=71,492 km), allowing good spatial discrimination

2.1 Jupiter’s FUV Auroral Emissions

Jupiter’s auroras have been usefully studied through FUV observations on several spacecraft (e.g., Voyager, Galileo, Cassini, New Horizons) and Earth-orbiting observatories (e.g., IUE, HST), and our understanding of them has improved dramatically, over the past few decades (e.g., Broadfoot et al. 1979; Ajello et al. 2001; Pryor et al. 2005; Gladstone et al. 2007; Prangé et al. 1996; Bhardwaj and Gladstone 2000; Clarke et al. 2004). Images from HST (see Fig. 2), in particular, have provided large datasets for studying auroral morphology and its spatial and temporal variability (e.g., Clarke et al. 1998, 2009; Nichols et al. 2007, 2009a, 2009b; Vogt et al. 2011). Likewise, FUV spectroscopy has provided strong constraints on the composition and temperature of Jupiter’s upper atmosphere in the auroral regions and also on the energy and composition of the precipitating particles responsible for the aurora (e.g., Yung et al. 1982; Livengood et al. 1992; Trafton et al. 1998; Ajello et al. 2001, 2005; Gérard et al. 2003; Gustin et al. 2004, 2006). We now recognize four primary types or regions of Jovian aurora: (1) the main oval (or main emissions), driven by the breakdown of co-rotation in the plasma of the middle magnetosphere (e.g., Grodent et al. 2003a, 2004, 2008b; Radioti et al. 2008, 2009, 2010, 2011), (2) highly-variable polar emissions that are likely associated with reconnection regions near the dayside magnetopause or the flanks of the magnetotail (e.g., Pallier and Prangé 2001; Waite et al. 2001; Pryor et al. 2001, 2005; Gérard et al. 2003; Grodent et al. 2003b; Bonfond et al. 2011), (3) the emissions associated with the magnetic footprints of the Galilean satellites (e.g., Bonfond et al. 2009, 2012; Grodent et al. 2009; Wannawichian et al. 2010), and (4) the sub-auroral emissions equatorward of the main oval, including blobs attributed to plasma injections (e.g., Mauk et al. 2002; Bonfond et al. 2012) and diffuse emissions attributed to pitch angle diffusion of energetic electrons (e.g., Radioti et al. 2009).
Fig. 2

Hubble Space Telescope image of Jupiter’s northern FUV auroral emissions (Clarke et al. 2002). The three main auroral types are shown: (1) main oval, (2) polar emission, and (3) Galilean satellite magnetic field footprints. The brighter regions are several hundred kiloRayleighs (kR) or more

Juno-UVS will provide new constraints on Jupiter’s auroral emissions, not only regarding nightside morphology and spectroscopy (only observable by spacecraft), but also of crucial vertical structure—on certain orbits Juno-UVS will view the aurora at the limb from a distance of ∼30,000 km, allowing a vertical resolution of ∼30 km. In addition, high resolution Juno-UVS observations of the shape of the auroral oval with local time (with the help of magnetometer data) can address the need for a localized magnetic anomaly (e.g., Grodent et al. 2008a). In particular, Juno-UVS observations will provide color ratios for the components of the Jovian aurora for a variety of local times and viewing geometries (cf., Grodent et al. 1997; Gladstone et al. 2007). Examples of simulated Juno-UVS auroral-region targeting and further details on Juno auroral science are provided in Bagenal et al. (2014).

2.2 Upper Atmosphere Structure and Composition

Jupiter’s upper atmosphere is currently poorly constrained, with the best available data from the Galileo probe which sampled the low-latitude regions (Seiff et al. 1998). Photochemical models have likewise concentrated on the low-latitudes (e.g., Gladstone et al. 1996; Moses et al. 2005), where the complexities of auroral region ion-neutral chemistry can be avoided (even though the auroral energy input globally dominates the actinic solar energy input, with ∼100 TW continuously deposited into Jupiter’s polar region atmosphere, e.g., Bhardwaj and Gladstone 2000). A few modeling studies of the chemistry and energetics in Jupiter’s auroral regions exist (e.g., Perry et al. 1999; Wong et al. 2000, 2003; Melin et al. 2006), but more are needed.

Jupiter’s upper atmosphere composition may be determined using Juno-UVS data in two different ways. In the auroral regions, the H2 Lyman band emissions typically originate somewhat below the homopause, and contain the absorption signature of overlying CH4 (giving rise to the color ratio) and even C2H2 and possibly other hydrocarbons (e.g., Dols et al. 2000). Also, in sunlit regions, the signal from reflected light at longer FUV wavelengths will show the absorption signatures of hydrocarbons, NH3, and possibly aerosols (e.g., Gladstone and Yung 1983). Finally, Juno-UVS observations each perijove (near sunset, at low-latitudes) are ideally suited to target airglow emissions, including ion recombination emissions similar to Earth’s tropical arcs, which could constrain Jupiter’s ionosphere structure and composition. Further details on Juno atmosphere science is provided in Ingersoll et al. (2014). Because of their intrinsic faintness (and the low duty cycle possible with the spinning Juno spacecraft), scientifically useful observations of Io Plasma Torus emissions or Galilean satellite emissions are unlikely.

3 Instrument Description

3.1 Overview

Juno-UVS is a photon-counting imaging spectrograph, based on the Lunar Reconnaissance Orbiter Lyman Alpha Mapping Project (LRO-LAMP), New Horizons-Alice (NH-Alice), and Rosetta Alice (R-Alice) instrument designs (Stern et al. 1998, 2008; Slater et al. 2001, 2005, 2008; Gladstone et al. 2010). Important changes from the earlier instruments include (1) a scan mirror (for targeting specific auroral features), (2) extensive shielding (for mitigation of electronics and data quality degradation by energetic particles), and (3) a cross delay line (XDL) microchannel plate (MCP) detector (for both faster photon counting and improved spatial resolution). In this section we provide a description of the instrument, highlighting these differences with previous designs.

Juno-UVS consists of two separate sections: a dedicated telescope/spectrograph assembly and a vault electronics box (see Fig. 3). The telescope/spectrograph assembly contains a telescope that feeds a 15 cm Rowland circle spectrograph with a spectral bandpass of 68–210 nm. The telescope has an input aperture 4×4 cm2 and uses an off-axis parabolic (OAP) primary mirror. A flat scan mirror situated at the front end of the telescope (used to look at up to ±30°perpendicular to the Juno spin plane) directs incoming light to the primary. The light is then focused onto the spectrograph entrance slit, which has three contiguous segments with fields-of-view (FOV) of 0.2×2.5, 0.025×2, and 0.2×2.5 projected onto the sky. This “dog bone” shaped slit’s long axis is parallel to the spacecraft spin axis. Light entering the slit is dispersed by a toroidal diffraction grating which focuses the UV bandpass onto a curved microchannel plate (MCP) cross delay line (XDL) detector with a solar blind, UV-sensitive CsI photocathode. Tantalum plates contiguously surround the detector and detector electronics assembly to shield the detector from general particle radiation and high-energy electrons in particular. The detector electronics are located behind the detector.
Fig. 3

Drawings of the Juno-UVS sensor (top left) and electronics box (top right), and pre-ship photographs of the sensor (bottom left) and electronics box (bottom right). Key sub-assemblies are indicated in the sensor drawing, and also show the operation of the scan mirror. The sensor photograph has the entrance baffle red tag cover in place for contamination control during spacecraft integration

The vault electronics box (Ebox) is located in the Juno spacecraft vault. Inside are two redundant high-voltage power supplies (HVPS), two redundant low-voltage power supplies (LVPS), the command and data handling (C&DH) electronics, heater/actuator activation electronics, scan mirror electronics, and event processing electronics.

The overall function of the instrument is under the control of the C&DH electronics, which consists of an 8-bit 8051 equivalent micro-controller, 32 Kbytes of PROM, 128 Kbytes of EEPROM, 128 Kbytes of SRAM, EEPROM and SRAM EDAC, and system timing functions. The C&DH accepts commands from the spacecraft and provides engineering telemetry while performing the following functions: (a) controlling the gain of the detector by adjusting the voltage that the HVPS provides to the MCP stack in the detector; (b) monitoring the detector MCP strip current, HVPS output voltage, and detector count rate so that it can “safe” the instrument upon an anomalous condition; (c) controlling the background radiation sensitivity of the XDL detector by adjusting the upper and lower level discriminator inputs to ensure that signals below and above certain levels are not processed; (d) controlling the optics heaters and the instrument aperture door; (e) controlling the one-time actuators such as the detector vacuum door and the front aperture fail-safe door (if needed), the instrument door launch latch mechanisms; and (f) controlling the scan mirror mechanisms.

The detector electronics receive detected event pulses from the detector and provide a digital indication of the spatial location, spectral location, and pulse height of each event being processed to the C&DH. Event processing electronics receive valid individual events and process them into a pixel list (a time ordered record of detected events). Special periodic data markers, called time hacks, are inserted in the pixel list to provide a fixed time reference for the events. Pixel lists are accumulated continuously in a “ping-pong” memory with the data in one memory bank being transmitted to the spacecraft over the science telemetry channel while the other memory is used to continue data acquisition and store detector events and time hacks. The last pixel list data are transmitted to the spacecraft upon a command to stop data acquisition.

3.2 Opto-Mechanical Design Overview

The scan mirror, OAP mirror, and diffraction grating are each constructed from monolithic pieces of aluminum, coated with electroless nickel and polished using low-scatter polishing techniques. The aluminum optics, in conjunction with the aluminum housing, form an athermal optical design. The scan mirror, OAP mirror, and diffraction grating are also each overcoated with sputtered Al/MgF2 for optimum reflectivity within the Juno-UVS spectral bandpass. Besides using low-scatter optics, additional control of internal stray light is achieved using internal baffle vanes within both the telescope and spectrograph sections of the housing, a holographic diffraction grating with low scatter and near-zero line ghost problems, and an internal housing with alodyned aluminum surfaces (Jelinsky and Jelinsky 1987; Moldosanov et al. 1998). In addition, a zero order light trap has a black anodized Al coating with very low surface reflectance at EUV/FUV wavelengths. Figure 4 shows a labeled opto-mechanical schematic of the interior of the Juno-UVS instrument, with light rays illustrating the optical path.
Fig. 4

An opto-mechanical schematic of the Juno-UVS sensor showing light rays traced through the main aperture door, reflecting from the OAP primary, passing through a focus at the slit, diffracted off the toroidal grating, and imaged onto the XDL MCP detector

3.3 Detector and Detector Electronics

The Juno-UVS detector configuration includes an XDL microchannel plate (MCP) detector scheme housed in a vacuum enclosure with a one-time opening door containing a UV-grade fused-silica window (for limited UV throughput during testing). The door was spring loaded for opening with a wax-pellet-type push actuator. The vacuum enclosure has a vacuum pump port and a small, highly polished region which functions as a zero-order reflector (directing zero-order light from the instrument grating into the zero-order trap on the side of the instrument housing). The vacuum enclosure also utilizes four female connectors for the anode signals, and two high-voltage (HV) connectors for the MCP and anode gap voltages.

The detector’s MCP configuration uses a Z-stack that is cylindrically curved to match the 150-mm Rowland circle diameter to optimize spectral and spatial focus across the Juno-UVS bandpass. The detector electronics provide two stimulation pixels that can be turned on to check data throughput and acquisition modes without the need to apply high voltage to the MCP stack or to have light on the detector. The MCP pulse-height information is output as 5 bits, which, together with the 11 bits of spectral and 8 bits of spatial information, results in the 3-byte output for every photon. The input surface of the Z-stack is coated with an opaque photocathode of CsI (Siegmund 2000).

A repeller grid above the curved MCP Z-stack enhances the detective quantum efficiency (DQE). Each of the three nested MCPs has a cylindrical 7.5-cm radius of curvature matching the instrument’s Rowland circle radius (i.e., 15.0 cm diameter). The approximate resistance per MCP plate is ∼130 MΩ. The MCP format is 4.6 cm wide in the spectral axis by 3.0 cm height in the spatial axis with 12-μm diameter pores and a length-to-diameter (L/D) ratio of 80:1 per plate. The XDL anode is a rectangular format of 4.4 cm×3.0 cm. The combination anode array and MCP sizes gives an active array format of 3.5 cm×1.8 cm necessary to capture the entire 68–210 nm instrument bandpass. The pixel readout format is 2048 pixels (spectral dimension) ×256 pixels (spatial dimension). The active area is 3.5 cm×1.8 cm, with ∼1500 spectral pixels and ∼230 spatial pixels. The XDL anode uses two orthogonal serpentine conductive strips for encoding an event’s X-position and Y-position. Each event (i.e., a cloud of electrons exiting the MCP) is collected in equal amounts by the two strips, Charge is collected at each end of each strip, and the difference in arrival time at each end of a given strip is used to determine the event position (e.g., Siegmund et al. 1999).

The detector electronics are composed of a separate electronics package mounted directly behind the detector vacuum enclosure within the sensor housing. Power to the detector electronics is supplied by the Juno-UVS low voltage power supply (LVPS) and command-and-data handling electronics (C&DH), both located in the electronics box (Ebox) in the spacecraft vault (several meters of cable away from the Juno-UVS sensor housing). The detector electronics are composed of five boards: (1) the amplifier board with two fast amps for the X direction (spectral dimension) and two fast amps for the Y direction (spatial dimension) and two charge amps for total event charge; (2 & 3) a time amplitude converter (TAC) board for each axis, X and Y, that encodes 2048 pixels in the X-axis and 256 pixels in the Y-axis by event arrival time differences; (4) the digital board (DIG) that provides the control signals and interface logic, and (5) a delay line board to delay the End signals. The detector electronics also generate a 5-bit analog sum signal for each detected photon event that can be used for generating a pulse-height distribution (PHD) via ground test or flight analysis software. Pixel list data (i.e., a list of pixel x, y addresses) is sent from the detector electronics to the C&DH electronics for further processing. A commandable stimulation pulse generator is also included that provides two stim pixels at two locations in the array; these are useful in checking data throughput without HV and in correcting for temperature effects on the wavelength scale.

A UV photon impinging on the photocathode generates a charge that is amplified by the microchannel plate Z-stack. The amplified charge cloud leaves the back end of the microchannel plate and is accelerated across the MCP-anode gap, impinging on the anode and generating pulses that propagate in both the +X and −X directions and +Y and −Y directions along separate integral delay lines to the detector electronics. The detector electronics then output the X and Y pixel locations to the C&DH based on the time delay between the two opposing pulses in each axis.

The detector electronics require input DC voltages of ±7.3 V and +5.0 V. The detector MCP high voltage is raised to a room temperature operational voltage of about −4.2 kV. The gap between the MCP output and the anode array requires a voltage drop of approximately −600 V. Both the MCP and the anode gap voltages are supplied by the instrument’s two redundant high voltage power supplies (HVPS) located in the Ebox. The overall detector gain is ∼2E7 (±25 %). At an expected average count rate of 2000 count/s, the amount of charge pulled from the MCP as a function of time is ∼0.2 Coulomb/year.

3.4 Instrument Electrical Design

The Juno-UVS instrument support electronics are largely single-string, but include redundant features for certain important functions. These electronics include redundant low-voltage power supplies (LVPS) and actuator electronics, the single-string command and data handling (C&DH) electronics, the redundant optics decontamination heater system, and the redundant detector high-voltage power supplies (HVPS). All of these sub-systems are controlled by an Intel 8051 processor implemented in a radiation-hardened FPGA with 32 kB of fuse programmable PROM, 128 kB of EEPROM, 32 kB of SRAM, and 128 kB of acquisition memory. A detailed block diagram of these electronics is shown in Fig. 5.
Fig. 5

Detailed block diagram of Juno-UVS

3.5 Operations & Data Collection Modes

In the following subsections we present a detailed description of how Juno-UVS is operated, how science and housekeeping (HK) telemetry is produced, and how the instrument is commanded (including a separate account of how science data is acquired).

3.5.1 Instrument Startup and Operational States

Upon power-on or software reset, the software starts and performs a code check. Instrument power may be applied either to instrument power bus A or bus B. A code check determines which code will be started, either PROM or one of the four EEPROM pages. If no problems are detected in the code check of the PROM, execution always initially starts in PROM. If problems are detected, one of four EEPROM pages will be used as backup. After nominal startup, execution can also be directed to one of four EEPROM pages, to allow for flight software patches. After completion of this code check and clearing of the memory, the various software modules are initialized. This basic software initialization includes:
  1. 1.

    Enter safe state (deactivate any actuator operation)

  2. 2.

    Pre-set the parameter table with hard coded (nominal operational) values

  3. 3.

    Initialize parameter table (with majority-vote-based values from EEPROM)

  4. 4.

    Initialize sequence table (with majority-vote-based values from EEPROM)

  5. 5.

    Set the discriminator to its default value (based on parameter table)

  6. 6.

    Start the aperture closing operation (if enabled based on parameter file)

  7. 7.

    Determine the active command interface and initiate telemetry on the active side


After this initialization completes (in 3–4 seconds), the nominal operations of the instrument start and the software is ready to receive telecommands. The side selection is made either when a correct common interface protocol (CIP) message is received, or when 3 consecutive Time Sync Pulses (TSPs) are received at about the expected rate of 0.5 Hz. Then telemetry for the active side is enabled and the instrument starts sending housekeeping packets. If after 180 seconds no side selection decision has been made, the instrument will start generating telemetry on the side specified by a configuration parameter. The selected side does not change until the instrument is power cycled.

Initially, the instrument clock begins counting from 1,000,000, incrementing every TSP by two counts. Whenever the first correct time synchronization message is received this counter is updated with the time value received from the spacecraft. If no TSPs are received, the instrument clock is updated based on the internal oscillator.

As indicated in Fig. 6, the Juno-UVS instrument can be in one of five states (including powered off) at any time. Four of these states are actually ‘operational’ states. Following power up or after a reset, the instrument will always enter the safe state. In the safe state, the instrument will always be idle; the HVPS, heaters and actuators will all be deactivated (except for a possible initial aperture door closing).
Fig. 6

Operational states diagram for Juno-UVS, showing the 5 instrument states and how they are connected. The 3 upper states (detector electronics off) are accessible with low-voltage alone, while the 2 lower states (detector electronics on) require high-voltage as well

Changes between states can be either the result of received telecommands or performed autonomously by the instrument due to an unmasked safety trigger or a timed completion of an acquisition. The current state of the instrument is always reported in the housekeeping telemetry.

3.5.2 Telemetry Generation

Each operation cycle (nominally every 2 seconds), the Juno-UVS instrument generates a telemetry Internet Protocol/User Datagram Protocol (IP/UDP) formatted transaction. This transaction will at a minimum include a housekeeping (HK) packet and a ‘safe-me’ packet. Housekeeping packets are generated at a configurable periodic interval (nominally 5 cycles or 10 seconds). In between these housekeeping packets, the same telemetry format (and contents) will be generated; but the HK packet will be labeled as a no operation (NOOP) packet so that the spacecraft discards these packets (this allows Juno-UVS to pass a spacecraft aliveness test every 2 seconds, even at reduced HK rates). ‘Safe Me’ packets are normally deactivated by likewise disguising them as NOOP packets. Memory dump packets are generated whenever a memory dump has explicitly been requested by telecommand. Although after power-up the software will immediately start generating telemetry transactions, these transactions will initially not be sent to the spacecraft, as the telemetry buffers are not enabled. A buffer will nominally only be enabled once a side selection decision has been made, and will remain enabled until Juno-UVS is powered off.

Telemetry generation is a two-step process. After being triggered by the occurrence of a Time Sync Pulse (TSP) event, the Tm task starts gathering data from all the different sources within the system to fill the defined telemetry packet, and it is labeled as a HK or dummy NOOP packet, depending on the selected HK rate. Then a ‘Safe Me’ packet is added and nominally labeled as NOOP unless a safing condition exists. A memory dump packet may be generated, if requested, and if a generated memory-dump data set is available. The gathering of housekeeping data occurs at a high priority, so that HK data provides a detailed time-correlated status of the instrument. After gathering all the data, the final IP/UDP protocol headers are generated by adding information such as length, the housekeeping packet, and checksums.

The actual transfer of the frame to the spacecraft is handed over to a lower priority task. This transfer can run at a lower priority as long as the transfer is completed well before the period expires. This transfer task moves the data to the Tm Universal Asynchronous Receiver-Transmitter (UART). The transmit UART includes a 32-byte FIFO buffer that is used to speed up Tm generation without too much processor activity. The processor activity is limited by waiting until FIFO almost empty status is reported in the Interrupt Service Routine (ISR). At that point, up to 20 bytes are copied into the UART buffer, without a need to perform separate checks on the intermediate buffer status (this allows for faster copying).

Included in the housekeeping telemetry is status reporting concerning received telecommands. Any command sent to the instrument will increment either the accepted or rejected command counter. This is also true for the ‘Confirm Critical’ command, even though this is only a partial command. An ‘executed command counter’ will be incremented only when a command completes execution without problems. These incrementing counters allow for the loss of a single Tm packet without a total loss of information. Also reported in the telemetry is the last detected error code. However, the Tm module simply reports the last received error code in the telemetry packet; so if multiple errors are detected in a given second, only the last (most recent one) will be reported. The most recent detected error will continue to be reported.

The configurable housekeeping telemetry rate allows for the adjustment of HK telemetry volume, based on the specific needs for an operational activity. The nominal housekeeping rate is one packet per 10 seconds. In this case, the packet contains all information that is needed for nominal operation use, including a vector of up to 101 samples of the instrument count rate determined at a 0.1 s rate. A higher rate may be selected when a faster response is desired; for instance, during ground testing or when troubleshooting problems. A lower rate may also be selected, for instance, when performing decontamination operations where only slowly-varying processes need to be monitored. This HK configurability can reduce the generated telemetry volume considerably (see Table 1).
Table 1

Example HK generation rates


Max (troubleshooting, power up)

Nominal (nominal operations & science)

Low (decontamination)

Very Low (special)

HK sub-sample rate





TM rate

1360 bits/s

272 bits/s

11.3 bytes/s

5.7 bits/s

HK volume

612.0 kbytes/hour

122.4 kbytes/hour

5.1 kbytes/hour

2.6 kbytes/hour

Relative TM volume

500 %

100 %

4 %

2 %

3.5.3 Telecommanding

Juno-UVS operations are commanded using a set of 30 separate telecommands. Telecommand processing handles the redundant telecommand channels and includes error detection and recovery. Nominally, the spacecraft may send up to two telecommand transactions to the instrument every 2 s cycle. These are formatted as separate Internet Protocol/User Datagram Protocol (IP/UDP) Packets, and include (among other items) time and nadir messages.

The acceptance and completion status of the command execution is reported in the housekeeping data. The instrument verifies incoming telecommands before they can be executed; this basic verification includes a format and checksum check of the telecommand. As mentioned, Juno-UVS has two redundant telecommand interfaces, but after power-up, the active interface will be determined and operations from that point on will only use that single interface.

In addition to the command verification mechanism, the instrument implements two additional mechanisms to protect the instrument from anomalous telecommands. Some commands are only allowed when the instrument is in a specific state. In addition to this, a number of commands have been declared ‘critical’. For Juno-UVS, this means that within a nominal 30-second timeout period, a specific confirmation command has to be received before the actual (critical) command execution starts. During most of the in-flight operations, this timeout is short compared with the light travel time to the spacecraft, meaning that the confirmation already has to be issued before confirmation of the acceptance of the command has been received on the ground. Still, this mechanism provides protection against accidental execution of commands.

The set of telecommands can be divided into three categories:

General operations—These allow for the complete basic operational commanding of the instrument. This includes setting and storing of parameters and starting and stopping of the science acquisitions. This set of seven commands allows for the full science operations of the instrument.

Manual operations—Additional capabilities needed during commissioning and instrument verification are provided by 15 additional telecommands that allow for extended command options. Some of these commands may be used for science operations depending on the situation.

Memory functions—Software code management and maintenance and additional debugging functions are provided by three general-purpose memory functions that allow for verification, load, and dump of memory blocks.

Whenever Juno-UVS detects errors while accepting or executing commands, an error will be reported in the generated telemetry packet. This includes an identifier for the telecommand (if available) and a general error code. The error code continues to be reported in the telemetry data until another error is detected or the instrument is reset. This simple form of error reporting is limited to reporting a single error per HK cycle (i.e., at most once per 2 s). An additional mechanism implementing a small error log is available for more extensive problem investigation. The command code for any successful command is also reported in the telemetry data, so the telemetry registration can be used to reconstruct the received telecommands. Note that the parameters of a telecommand are not included in this reporting.

3.5.4 Acquisition Commanding

The basic science data acquisition function of Juno-UVS is handled by a start acquisition telecommand which has a number of parameters defining basic acquisition operations, with several settings defined by configuration parameters. At power-up the parameter list is initialized with values from non-volatile instrument memory. Once these general instrument configuration parameters have been set, these parameters are expected to need little change; and this mechanism results in simple acquisition command which only requires parameters that change frequently.

Once the acquisition start has been commanded, the instrument goes through an acquisition startup sequence, possibly including HV ramp up and aperture door commanding. The actual acquisition startup will start on the Juno synchronization signal (next TSP synchronization pulse), so the exact time of acquisition start is known and can be planned for.

Whether the aperture door is opened for a specific acquisition depends on the operational procedures. Periodically, the instrument will be commanded to acquire ‘dark’ acquisitions with the aperture door closed. For normal science acquisitions, the aperture door has to be open; this could either mean that the door is left open all the time or only commanded open for the specific acquisitions. At the end of an acquisition, the aperture door and the high voltage will be left at the latest commanded level.

For acquisitions, a science data frame will be generated whenever the acquisition memory is full of data (i.e., full of photon and/or time hack events). The time it takes for this memory to fill depends on the selected time hack rate, the brightness of the observed object (number of photons detected), the background event rate (primarily from penetrating energetic electrons at Jupiter), and the selected masking parameters. When an acquisition memory buffer is full, the acquisition will immediately continue in the next memory buffer while the filled buffer is transferred to the spacecraft. As this ‘buffer full’ event is related to the number of detected events, it is not synchronized to the instrument time sync. The transfer of a filled buffer to the spacecraft will be completed in about 0.4 seconds, so in nominal operations (if the photon and/or background count rates aren’t too high) the buffer will be available for acquisition before the second buffer is filled. With the fixed buffer size and science data transfer rate, Juno-UVS can sustain a maximum transfer rate of 83,000 events/s to the spacecraft.

Nominally, the acquisition operation will continue until the instrument is explicitly commanded to ‘stop acquisition.’ In addition, a timeout mechanism is implemented that will terminate an acquisition mode when a predefined timeout period has expired; this mechanism may also be used to command acquisitions of a predetermined duration. When the acquisition is terminated, the data already in the acquisition buffer is sent to the spacecraft. Still a complete 32 k-event science frame is used even though it may only be partially filled. The used part in the pixel list frame can be recognized as the data consists of all ‘zero’ events which will normally not occur in the data (and will also be reported in the housekeeping packet). To command the ‘stop acquisition’ either the ‘enter safe state’ or ‘enter checkout state’ telecommand can be used. Both commands have the same effect, in that the acquisition is terminated. The ‘enter safe state’ will, in addition to terminating the acquisition, also deactivate the HVPS and close the aperture door.

For test purposes, an additional command parameter is available that allows for the selection of one out of five deterministic test patterns. The whole acquisition process proceeds just like a nominal acquisition, but initially the acquisition buffers are filled with the deterministic pattern. Since there are no actual data or time hacks involved, the acquisition buffer will not fill, so there are no hardware trigger moments in which the data is sent to the spacecraft. As a replacement, the software implements an exposure timer that controls the time at which the frame is actually sent (selectable from 0.1 s to 25 s). The timeout period for this timer may even be varied during an acquisition to simulate a case where data generation rate varies over time.

3.6 Changes from Previous LAMP and Alice Instruments

Table 2 compares the key similarities and differences of Juno-UVS and its predecessors.
Table 2

R-Alice, NH-Alice, LAMP, and Juno-UVS Comparison







3.0 kg

4.4 kg

6.1 kg

21.6 kg


4.0 W

4.4 W

4.5 W

9.8 W


41×20×12 cm3

46×16×12 cm3

55×16×12 cm3

44×24×22 cm3+13×6×9 cm3 (Ebox)

Spectral Bandpass

70–205 nm

52–187 nm

57–196 nm

68–210 nm

Input Channels

Airglow Only

Airglow & Solar Occultation Channel

Airglow & Pinhole

Airglow Only

Entrance Slit FOV





OAP Mirror & Grating Specs

Identical Specifications (except for optical coating) OAP: f/3, 120-mm focal length; Grating: 1600 grooves mm−1, 150-mm radius of curvature

Optical Coating





MCP Detector





Detector Photocathodes

KBr (70–120 nm) CsI (123–205 nm)

KBr (52–118.1 nm) CsI (125.1–187 nm)

CsI (57–196 nm)

CsI (68–210 nm)

Lyα Gap (i.e., bare MCP)

3 nm

7 nm

No Gap

No Gap

Detector Door Actuator

Dimple Motor

Wax Pellet

Wax Pellet

Wax Pellet

Pulse Height Distribution Bins

16 (per frame)

64 (per frame)

64 (per frame)

17 (per event)


1 (non-redundant)

2 (redundant)

2 (redundant)

2 (redundant)

4 Calibration

After it was assembled and through with environmental testing, just prior to delivery to Lockheed Martin for integration on the Juno spacecraft, Juno-UVS underwent a series of tests to characterize its radiometric performance. Specifically, the Juno-UVS flight instrument was tested in SwRI’s vacuum radiometric calibration chamber in order to determine the best pre-launch values for: (1) dark count rate; (2) PSF and wavelength calibration; (3) off-axis light scatter, and (4) effective area. Note that some of these attributes (e.g., effective area) can be measured much more accurately in flight (through stellar calibration), while other important calibration data (e.g., flat field measurements) are obtained only after launch. Table 3 shows a summary of the results for each of the ground radiometric tests performed, along with the performance requirement. As shown in this table, all the specified radiometric requirements measured during the vacuum radiometric tests were met. Figure 7 shows Juno-UVS in the test chamber just before starting radiometric calibration (during 2010 October 12–17). The results of these ground calibrations are described in the following subsections.
Fig. 7

Juno-UVS just prior to undergoing testing in SwRI’s vacuum radiometric calibration facility

Table 3

Vacuum radiometric test results summary


Required Performance

Measured performance

Dark Count Rate

≤10 counts/second (total array)

<2 counts/second (on ground)

Point Spread Function

<0.6 nm (spectral, point-source, on-axis)

<0.6 nm (spectral, on-axis)

<2.0 nm (spectral, filled slit)

<1.1 nm (spectral, off-axis)

<1° (spatial)

0.07°–0.17° (spatial)

Wavelength Bandpass

78.0–172.0 nm (minimum coverage)

67.5–210.0 nm

Spectral Plate Scale

<0.095 nm per spectral pixel

0.1020 nm±0.0004 nm

Spatial Plate Scale

<0.043° per spatial pixel


Off-Axis Light Scatter

PSTa<10−5 at θoff>7

PST<7×10−6 at θoff>7



Effective Area


Effective Area

Absolute Effective Area

78–80 nm

>0.002 cm2

92.6 nm

0.0026±0.0003 cm2

100–110 nm

>0.002 cm2

106.7 nm

0.0042±0.0003 cm2

119–130 nm

>0.2 cm2

121.6 nm

0.54±0.08 cm2

130–140 nm

>0.1 cm2

130.0 nm

0.4±0.1 cm2

160–172 nm

>0.02 cm2

140.0 nm

0.18±0.09 cm2


168.5 nm

0.017±0.004 cm2

aPST=Point Source Transmittance, defined as irradiance at the focal plane divided by the input irradiance

4.1 Dark Count Rate

The Juno-UVS detector dark count rate was measured during ground calibration via a set of exposures that totaled 14.5 hours of accumulated exposure time. These datasets allowed us to examine both the temporal and spatial distribution of the dark noise and measure its rate. The time hack interval for the dark exposures was 0.512 s. The average dark count rate over the total 14.5-hour exposure interval varied between 1.5 and 2.0 counts/s (i.e., 0.18–0.26 counts cm−2 s−1) with Poissonian counting statistics (σ∼0.28 counts/s averaged over 25-s bins). This rate is well below the specified dark rate value of <1 count cm−2 s−1. Figure 8 shows a pre-launch spectral image of a dark exposure. Event pileup occurs at the left and right edges of the array, a characteristic of the XDL detector/electronics. This pileup results in a “warm” area in the lower right corner of the image that accumulates 5–10 counts/pixel over 14.5 hours, or ∼2E–4 counts/pixel/s. The two stim pixels are also visible at the lower left and upper right image edges.
Fig. 8

Pre-launch background count test exposure, showing a dark rate of ∼2 counts/s. This figure also shows how the raw Juno-UVS data appear when histogrammed in wavelength (x axis, ∼1500 active pixels) versus slit position (y axis, ∼230 active pixels). Event pileup occurs at the left and right edges of the detector, but the response over most of the active area is very uniform. The stim pulse locations are also seen, at the lower left and upper right

4.2 Spatial/Spectral Resolution

The spectral and spatial PSFs were measured at 0.5° intervals along the length of the slit and at specific wavelengths across the Juno-UVS bandpass using argon gas in a hollow-cathode UV light source. Point source pixel observations were acquired and converted via software into an image for each slit location beginning at the center of the slit (spatial offset of 0°) and at offset angles of ±0.5°, ±1.0°, ±1.5°, ±2.0°, ±2.5°, and ±3.0° with respect to slit center. For each exposure, the image row with the maximum number of counts was used to fit a series of Gaussians for each identified emission line in the spectral axis. In the spatial axis each column was fit with a Gaussian to determine the spatial PSF. The measured values varied between 0.4 and 1.1 nm, which satisfied the Juno-UVS specification of <2.0 nm FWHM, and less than 0.6 nm for on-axis observations.

The larger number and smaller size of the spatial pixels of the XDL detector versus the double-delay-line (DDL) detector used on previous instruments allows for proper sampling of the spatial PSF, as a point source is now imaged over multiple detector rows. The spatial resolution at the slit center well exceeds the specification of 1° at all wavelengths. The best resolution is found near 90 nm, which matches the theoretical astigmatic point of the Juno-UVS optical design.

4.3 Wavelength Calibration

The images taken to determine the airglow PSF values (using the Ar lamp) were also used to determine the wavelength calibration at room temperature (+22°C). Four principal argon emission lines at 91.9781, 93.2054, 104.822, and 106.666 nm, two aluminum emission lines at 153.945 and 167.079 nm, the Lyα and Lyβ hydrogen emissions at 121.567 and 102.572 nm, the oxygen emission line at 130.22 nm, the nitrogen emission line at 149.26 nm, and the two bright neon emission lines at 73.5896 and 191.608 nm were used at slit center. The spectral plate scale and linear offset were determined with a simple linear fit to these data: /dx=0.1020±0.0004 nm/pixel; offset (slit center)=31.73±0.43 nm. The linear fit is good—the χ2 statistic for the fit is 6.15 with a linear correlation coefficient of 0.9998. The standard deviation of the wavelength residual between the linear fit and the sixteen absolute emission line wavelengths is ±0.636 nm.

The total wavelength bandpass across the detector active area was computed with the above-measured plate scale and offset values. The active area starts at spectral pixel 300 and ends at pixel 1800. This area corresponds to a total wavelength bandpass of 67.5–210.0 nm, easily satisfying the minimal bandpass requirement of 78–172 nm.

The wavelength offset varies slightly with the temperature of the detector electronics at a measured rate of ∼0.6 pixels/°C (i.e., wavelengths shift to the blue at a rate of ∼0.061 nm/°C; the plate scale variation with temperature is negligible and can be ignored). Care must thus be taken to apply the proper offset according to the detector electronics temperature for a given observation. This temperature dependence was measured/calibrated during detector subsystem and instrument thermal vacuum testing. The wavelength offset also varies with the (x,y)-location of the point source image within the slit due to both instrument pointing and to slit curvature aberrations. Additional wavelength calibration will be determined on orbit using standard UV stars.

4.4 Scattered Light Characteristics

The off-axis light scattering characteristics were measured in both the horizontal and vertical axes of Juno-UVS. Exposures using a collimated input source and a hollow-cathode lamp gas mixture of H/He were acquired at angular input angles that varied between −12° and +12° with respect to the boresight axis in the horizontal plane (perpendicular to the slit length with the vertical axis fixed at the center of the slit), and the vertical plane (parallel to the slit length with the horizontal axis fixed at the center of the slit). The acquired images were analyzed to determine the point source transmittance (PST) as a function of incident input angle to the Juno-UVS boresight. The PST is defined as follows:
$$\mathit{PST} = \frac{E_{\mathit{FP}}}{E_{\mathit{input}}} $$
where EFP is the irradiance at the focal plane; and Einput is the input irradiance at the entrance aperture of the instrument. This expression can be written in terms of the measured off-axis angle count rate to the on-axis count rate ratio (Roff/R0); the effective area averaged over the Juno-UVS bandpass (〈Aeff〉); the focal plane active area (AFP); the average in-band quantum efficiency of the CsI detector photocathode (〈QE〉); and the ratio of the input beam area (Abeam) to the geometric area (Ag) of the entrance aperture (since the input beam underfills the entrance aperture). Using these parameters, the above equation for PST becomes
$$\mathit{PST} = \biggl( \frac{ \langle A_{\mathit{eff}} \rangle}{A_{\mathit{FP}} \langle \mathit{QE} \rangle} \biggr) \biggl( \frac{A_{\mathit{beam}}}{A_{g}} \biggr) \biggl( \frac{R_{\mathit{off}}}{R_{0}} \biggr). $$

The average effective area and quantum efficiency values used to compute the PST were measured during instrument radiometric and detector vendor tests (〈Aeff〉=0.54 cm2; 〈QE〉=0.25; Abeam/Ag=0.05; AFP=7.5 cm2). With these input values, we estimate a PST of 0.014 at an off-axis angle of 0° (i.e., on-axis along the boresight with Roff/R0=1). The requirement of PST<10−5 at off-axis angles >7° was met in both axes.

4.5 Effective Area

The effective area was measured across the Juno-UVS bandpass at discrete wavelengths using emission lines from neon, argon, and a hydrogen/helium gas mix covering a wavelength range of 73.6–191.6 nm. Exposures were made with the calibration chamber’s monochromator set to the specific measurement wavelength. The monochromator output slit was set to provide a detector output count rate that did not show any saturation effects in the pulse-height distribution (since too high a local flux on the MCP stack causes a local gain drop evident in the pulse-height data). Background exposures were also taken for each illuminated exposure to allow for dark subtraction.

The beam flux was measured for each effective area measurement using a NIST-calibrated silicon (Si) photodiode. In most cases, the beam flux had to be increased in intensity to allow enough flux for a measurement with the photodiode. However, this increased level flux was too high for a measurement with Juno-UVS causing local MCP saturation. An Amptek channeltron was used to measure the ratio of the beam fluxes at both the low- and high-intensity levels to provide a correction factor to the flux measured by the NIST photodiode.

The equation used to compute Aeff is
$$A_{\mathit{eff}} = \frac{A_{g} R(\lambda )}{\varPhi (\lambda )}, $$
where Ag is the geometric area of the Juno-UVS entrance aperture (16 cm2); R(λ) is the detector count rate (corrected for detector dead time and background); and Φ(λ) is the input flux to the instrument based on the NIST photodiode measurements.
Key to meeting the Juno-UVS sensitivity requirements is the choice of optical coatings for the grating, OAP mirror, and scan mirror. In the early mission planning stages, a SiC coating was planned, in order to provide good throughput at EUV wavelengths, where there are useful H2 emissions diagnostic of temperature and column density. Later, however, it was determined that the Juno-UVS wavelength resolution would not be high enough to make use of these features. Simulations indicated that MgF2-coated optics would result in a count rate 3× larger than SiC-coated optics, for the same aurora. Thus, because of the low duty cycle available for observations with the spinning Juno spacecraft, the MgF2 optics were selected for flight, despite their lower sensitivity at wavelengths <115 nm. Figure 9 shows the current best estimate of the Juno-UVS effective area, as determined by in-flight observations of selected UV-bright stars, and in comparison with requirements and ground measurements. Further in-flight observations, such as lunar observations during Earth flyby, will be used to improve the measured effective area at EUV wavelengths. As shown in Fig. 9 (and Table 3) the effective area requirements were met with significant margin between 110 and 165 nm. Figure 10 shows the estimated response of Juno-UVS (using the in-flight effective area determination) to a modestly-bright 100-kR aurora (note that auroras of MR brightness are frequently observed with HST, e.g., Clarke et al. 2004) and to reflected sunlight. While there is overlap between the two sources, their contributions are expected to be easily separable.
Fig. 9

Preliminary Juno-UVS effective area results from high-voltage checkout (HVCO) commissioning in December 2011 (±1σ region in red), compared with model expectation (black), ground calibration with resonance lamps at specific wavelengths (blue), and the mission requirements (green). The HVCO results are based on International Ultraviolet Explorer (IUE) observations of several UV-bright stars which are used as flux standards
Fig. 10

Estimated response of Juno-UVS to (a) 100-kR Jupiter aurora of H2 and H emissions (green) and (b) reflected sunlight (orange) filling a solid angle of 1.2E−5 steradians (appropriate for 0.2×0.2 pixels). The model spectra are smoothed to the estimated filled-slit spectral resolution of 1.1 nm. Integrated over the Juno-UVS bandpass, with an exposure time of 16.7 ms (appropriate for the time it takes Juno to spin 0.2° at 2 RPM), a total count rate of 141.2 counts/spin/0.2° pixel is expected for a 100-kR aurora, while 144.5 counts/spin/0.2° pixel is expected for reflected sunlight, with the two sources largely separated by wavelength

4.6 Commissioning

During commissioning, yearly cruise calibrations, and at the apojoves of each Jupiter orbit, standard UV-bright stars will be observed to determine and monitor the effective area of Juno-UVS. These stellar sources will also be observed at various positions along the slit to provide accurate slit dimensions, vignetting information, and row-to-row variations in detector sensitivity. Filled-slit line shapes are acquired by looking at the interplanetary Lyα signal (e.g., Pryor et al. 2008). Juno-UVS “first-light” observations occurred during high-voltage checkout (HVCO), and are presented in Fig. 11. Also during high-voltage checkout, the optimal high voltage and discriminator settings are found, by inspection of a matrix of test observations and pulse height distributions (PHDs). The pulse height is obtained for every event, which makes monitoring PHDs much easier than in heritage versions of the Juno-UVS instrument.
Fig. 11

“First-light” image, comprised of data from the first five spins of the spacecraft after Juno-UVS reached operational detector voltage. The slit with its “dog-bone” shape is clearly visible in the bright interplanetary Lyα spectral line at 121 nm. Stars that briefly swept through the slit (due to the spin rate, a star is only in the narrow part of the slit for 8 ms/spin) have continuum spectra and appear as horizontal stripes

Another important part of our in-flight calibration activities is to determine the digital dead time, which can decrease the measured signal at very large count rates. Ground tests by the detector provider indicate a digital dead time of 1.2 μs (i.e., corresponding to a 10 % lower measured count rate for an input count rate ∼92,600 counts/s; for comparison, the brightest UV star we will observe, β Cru, is expected to have an input count rate of ∼1E6 counts/s). Initial results suggest that the ground dead time determination is accurate.

Finally, stellar observations are planned for use at Jupiter to measure exactly where Juno-UVS is pointing, for any scan mirror position (the commanded scan mirror location is not determined on board by the instrument). By centroiding the stellar detections when the instrument is pointing away from Jupiter, we expect to locate photons to better than 0.05° on the sky (the resolution of the narrow part of the slit). Figure 12 shows a “half-sky” map, in galactic coordinates, using data obtained during HVCO in which the scan mirror was stepped from −30° to +30° from the Juno spin plane.
Fig. 12

Juno-UVS “half-sky” map showing the integrated starlight acquired during HVCO (for wavelengths >125 nm) in a Mollweide projection with galactic coordinates. The Large and Small Magellanic Clouds are evident in the lower right quadrant

5 Data Products

Juno-UVS data products, as delivered to NASA’s Planetary Data System (PDS) for distribution to the public and archival purposes, include (1) Engineering Data Record (EDR) files (which contain minimally-processed Juno-UVS science and housekeeping (HK) telemetry files after they have been retrieved by the primary Juno-UVS SOC pipeline computer), (2) Reduced Data Record (RDR) files (which contain Juno-UVS data which have had the best available calibrations applied to bring them to physically useful units), and (3) high level data products (such as spectral images and maps) as they become available. A Juno-UVS SOC pipeline “executive” program executes once per day to detect the newly delivered data files. After cataloging the received files, the “executive” program initiates execution of the Juno-UVS SOC data processing pipeline. The first element of the pipeline (nicknamed “Lima”) is responsible for converting the raw data files into EDR data products (CODMAC Level 2). These products represent the lowest processing level of the Juno-UVS data and are delivered to the Planetary Data System (PDS) for archiving through the Juno Science Operations Center (JSOC). No calibrations are applied to the science data at this stage. Raw telemetry values are converted to engineering units where applicable; however, both raw and converted values are included in the EDR data product. Multiple versions of the output EDR products will be made available if software bugs affecting the output data are uncovered and corrected. In the event of an error whose correction alters released data, the data will be reprocessed by the revised software and then delivered to the PDS. The second element of the pipeline (nicknamed “Mike”) calibrates and spatially locates the data contained in the EDR data products, resulting in the RDR data products (CODMAC Level 3). As with the EDR files, the RDR files are delivered to the Planetary Data System (PDS) for archiving through the JSOC.

5.1 EDR Data Product Details

The sources of the data contained in the Juno-UVS EDR data product are files containing (1) the Juno-UVS instrument low-speed housekeeping telemetry and (2) the Juno-UVS science data. These data are processed when both science and housekeeping files are present; if one is present without the other then a partial product will be created and that file will be flagged for later reprocessing. The data are grouped for specific observation events, and a formal description of the PDS-delivered data is provided in the associated EDR Software Interface Specification (SIS) document. The Juno-UVS EDR data product combines these files into a single FITS formatted file containing the following extensions:

Spectral vs. Spatial Image: This is a reconstructed histogram generated from the pixel list data in the science data file. Photon acquisition events are binned according to their spectral and spatial components. This summary image is used as a “quick-look” check on data quality. [Extension 0=primary FITS header and data unit (HDU)]

Spatial vs. Time Image: This is similar to the first dataset, but data are binned based on spatial and temporal parameters. The time dimension of the image covers 360° on the sky, and is split into 5 panels of 72° each. A new histogram is started each time the scan mirror position changes, as determined from the housekeeping data. This summary image is used as a “quick-look” check on data quality. [Extension 1]

Frame List: This dataset contains a list of the generated frame acquisitions. The list includes, for each frame, the instrument frame sequence number, start and stop times, tag bytes, quality factor and other instrument state information. The frame acquisition times and instrument state data contained in this list are used to cross-reference with the pixel list mode data for purposes of selecting data and checking timing consistency. [Extension 2]

Scan Mirror Data: This dataset contains a listing of all start and stop times when the scan mirror was at a fixed position. These data are taken from the housekeeping packets, so are limited to the HK rate selected for the given observations. [Extension 3]

Raw Frame Data: This dataset contains all the raw data from the science data file, except for the file header. [Extension 4]

Analog Count Rate: This dataset contains a sequence of time ordered photon count rates read from the housekeeping data packets. At nominal HK rates (down to 0.1 Hz), this results in a 0.1-s sampling of the unmasked analog count rate. [Extension 5]

Digital Count Rate: Similar to the previous dataset, this contains the count rate as determined from the raw science data, as limited by masking and discriminator settings. These data are shown as counts/second. [Extension 6]

Pulse Height Distribution (Lyman Alpha): This is the first of three histograms where the bins are arranged as pulse height vs. time. One histogram will be created per spin. This histogram contains photons whose spectra are recorded on detector columns numbered between 850 and 930 (i.e., Lyα photons). [Extension 7]

Pulse Height Distribution (Stellar): This is the second of three histograms where the bins are arranged as pulse height vs. time. One histogram will be created per spin. This histogram contains photons whose spectra are recorded on detector columns numbered between 931 and 1770 (i.e., photons at wavelengths longer than Lyα). [Extension 8]

Pulse Height Distribution (Stim): This is the last of three histograms where the bins are arranged as pulse height vs. time. One histogram will be created per spin. This histogram contains photons whose spectra are recorded on detector columns numbered between 0–149 and 1950–2047 (i.e., the stim pulse regions). [Extension 9]

Housekeeping Data: This dataset contains the complete housekeeping dataset, both in raw format and, where applicable, in calibrated engineering units. HK data are included here to assist with joint instrument and data quality trending analyses (foreseen and unforeseen). [Extension 10]

Parameter List: This table records the known values of the instrument parameter table, as reported in the housekeeping data. [Extension 11]

The primary data of the Juno-UVS EDR product files are the raw data frames in Extension 4 of the FITS files. These data frames contain a series of time-tagged UV photon detection events. The histogram image in the primary FITS header and data unit (HDU) are simply these photon events histogrammed into the 2048 spectral by 256 spatial bins. These histograms are included up front since most FITS viewers expect image data in the primary HDU and because they can give at a glance an indication of the data quality and an average spectrum.

5.2 RDR Data Product Details

The source of the data contained in the Juno-UVS Pipeline RDR data products are the Juno-UVS EDR data products, as described above. The next step (nicknamed “Mike”) in the Juno-UVS data processing pipeline adds pointing and calibration information to the EDR data, but maintains the FITS structure. The resulting RDR data product contains the following extensions:

Calibrated Spectral Image: This is a reconstructed histogram generated from the pixel list data in the EDR data product but with instrumental calibrations applied. This summary image is used as a “quick-look” check on data quality. [Extension 0=primary FITS header and data unit (HDU)]

Acquisition List: This dataset contains a list of the generated frame acquisitions as determined from the housekeeping data file. The list includes, for each frame, the instrument frame sequence number, start and stop times, mode type, aperture door and other instrument state information. These data are simply copied as is from the EDR data product. The frame acquisition times and instrument state data contained in this list are used to cross-reference with the pixel list mode data in Extension 2 for purposes of selecting data and checking timing consistency. [Extension 1]

Calibrated Pixel List Mode Data: This dataset contains a calibrated version of the complete pixel list science dataset from the EDR data product, plus propagated estimated errors introduced by the separate calibration steps, plus ancillary spatial location and pointing information that is needed on a per-photon-event basis. These are the primary science data for use in making maps and other pixel list derived science products. [Extension 2]

Ancillary Data: This dataset contains ancillary spatial location and pointing information that varies smoothly and slowly over the Juno orbit. Also included in this extension are other slowly varying instrument-related quantities, such as the detector locations of the fiducial “stim” pixels, a measure of the background dark signal, and data quality flags. Entries in this table are typically separated by 30 s intervals instead of on a per-photon basis in order to reduce data volume and computation time. [Extension 3]

Calibrated Analog Count Rate: This dataset contains a high-resolution sequence of UV photon count rates as read from the housekeeping data, with corrections for detector dead-time applied. [Extension 4]

Calibrated Digital Count Rate: This dataset contains a high-resolution sequence of UV photon count rates computed from the calibrated pixel list data for each acquisition (nominally the whole orbit), with corrections for detector dead-time applied. [Extension 5]

Pulse Height Distribution (Lyman Alpha): This is the first of three histograms where the bins are arranged as pulse height vs. time. These data are simply copied as is from the corresponding EDR data product. This histogram contains photons whose spectra are recorded on detector columns numbered between 850 and 930 (i.e., Lyα photons). [Extension 6]

Pulse Height Distribution (Stellar): This is the second of three histograms where the bins are arranged as pulse height vs. time. These data are simply copied as is from the corresponding EDR data product. This histogram contains photons whose spectra are recorded on detector columns numbered between 931 and 1770 (i.e., photons at wavelengths longer than Lyα). [Extension 7]

Pulse Height Distribution (Stim): This is the last of three histograms where the bins are arranged as pulse height vs. time. These data are simply copied as is from the corresponding EDR data product. This histogram contains “photons” whose “spectra” are recorded on detector columns numbered between 0–149 and 1950–2047 (i.e., the stim pulse regions). [Extension 8]

Housekeeping Data: This dataset contains the complete housekeeping dataset, both in raw format and, where applicable, in calibrated engineering units. These data are mostly copied as is from the EDR data product. HK data are included here to assist with joint instrument and data quality trending analyses (foreseen and unforeseen). [Extension 9]

Wavelength Lookup Image: This dataset contains a 2048×256 image whose floating-point pixel values are the wavelengths corresponding to the pixel locations on the detector. This wavelength calibration image is provided to be used with Extension 0 for quick-look checks, but not for scientific analysis. Its file-averaged wavelength solution makes it generally unsuitable to be used with pixel list data. [Extension 10]

5.3 Higher Level Product Details

The details of the higher level data products, such as spectral images, brightness maps, color ratio maps, etc. are currently undefined, but are envisioned as simple FITS format files with extensions for image, error, and data quality. Table 4 presents a summary of all the planned data products, and an estimate of their data volume.
Table 4

Juno-UVS data products






Estimated Size (MB)

Engineering Level Data

Instrument value science data (“raw stream” pixel list) + instrument housekeeping data


Instrument data files + engineering calibration data

FITS (science + housekeeping), binary (memory dumps)

60 per orbit

Science Level Data

Calibrated value science data(tabulated pixel list) + ancillary data


Engineering Level data+ science calibration data


1200 per orbit

Brightness Images

N & S images of UV brightness at selected wavelengths & epochs + statistical errors, data quality


Science Level data


150 per orbit

Brightness Maps

N & S polar maps of UV brightness at selected wavelengths & epochs + statistical errors, data quality


Science Level data


300 per orbit

Color Ratio Maps

N & S polar maps of UV color ratio + statistical and systematic errors and data quality


Science Level data


50 per orbit

Precipitating Electron Energy & Flux Maps

N & S polar maps of estimated mean energy and flux of auroral electrons + statistical and systematic errors and data quality


Science Level data + models


50 per orbit

6 Summary

The Juno mission has begun its 5-year flight to Jupiter, and Juno-UVS has undergone low-voltage and high-voltage checkouts (and initial instrument compatibility checks), and is found to be in excellent health. Yearly in-flight calibration observations of hot UV stars are planned for Juno-UVS during the mission to further characterize its in-flight performance. It is expected that the data gathered this instrument will provide an excellent resource for improving our understanding of Jupiter’s amazing auroras.


We wish to thank the entire Juno-UVS engineering, science, and support teams at SwRI (especially David Cronk, Joe Esquivel, Jim Foster and Roy Graham), Sensor Sciences, and the Université de Liège. We also thank the Juno project, especially Phil Morton, Mark Boyles, Maurine Miller (and the rest of the payload team) at JPL, John Ricks at LM for shepherding Juno-UVS through ATLO, and Bill McAlpine at JPL for radiation modeling support. Juno-UVS was funded under contracts NAS703001TONMO710962 and NNM06AA75C to NASA, whose support we gratefully acknowledge. This paper is dedicated to the memory of our dear friend and colleague, Dave Slater.

Copyright information

© The Author(s) 2014

Open Access This article is distributed under the terms of the Creative Commons Attribution License which permits any use, distribution, and reproduction in any medium, provided the original author(s) and the source are credited.

Authors and Affiliations

  • G. Randall Gladstone
    • 1
  • Steven C. Persyn
    • 1
  • John S. Eterno
    • 1
  • Brandon C. Walther
    • 1
  • David C. Slater
    • 1
  • Michael W. Davis
    • 1
  • Maarten H. Versteeg
    • 1
  • Kristian B. Persson
    • 1
  • Michael K. Young
    • 1
  • Gregory J. Dirks
    • 1
  • Anthony O. Sawka
    • 1
  • Jessica Tumlinson
    • 1
  • Henry Sykes
    • 1
  • John Beshears
    • 1
  • Cherie L. Rhoad
    • 1
  • James P. Cravens
    • 1
  • Gregory S. Winters
    • 1
  • Robert A. Klar
    • 1
  • Walter Lockhart
    • 1
  • Benjamin M. Piepgrass
    • 1
  • Thomas K. Greathouse
    • 1
  • Bradley J. Trantham
    • 1
  • Philip M. Wilcox
    • 1
  • Matthew W. Jackson
    • 1
  • Oswald H. W. Siegmund
    • 2
  • John V. Vallerga
    • 2
  • Rick Raffanti
    • 2
  • Adrian Martin
    • 2
  • J.-C. Gérard
    • 3
  • Denis C. Grodent
    • 3
  • Bertrand Bonfond
    • 3
  • Benoit Marquet
    • 4
  • François Denis
    • 4
  1. 1.Southwest Research InstituteSan AntonioUSA
  2. 2.Sensor SciencesPleasant HillUSA
  3. 3.Laboratoire de Physique Atmosphérique et PlanétaireUniversité de LiègeLiègeBelgium
  4. 4.Centre Spatial de LiègeLiègeBelgium