urn:nasa:pds:jno-jad-fitted-tofsp:data:moments_protons_10min 0.1 1.24.0.0 Product_Observational 2025 These are numerical moments of the JADE-I Species 3 data product, assuming the whole plasma distribution is within the JADE-I energy range - which is not always true. Numerical moments are throwing numbers at some equations and getting a value out, however just because we can does not mean we should, or that the results should be trusted. Please look at the raw (Level 2 or Level 3) JADE data to see if it is appropriate to calculate moments for your time range of interest. e.g. is the whole distribution within JADE-I's Energy range (if not, V is bad, and so is T), or, is there any signal in the data or is it just background plus noise? Robert J. Wilson 0000-0001-9276-2368 1 Laboratory for Atmospheric and Space Physics https://ror.org/01fcjzv38 2025-12-11 0.1 This is the first version for PDS Peer Review. 2016-06-24T08:24:41.444Z 2021-07-31T23:47:24.021Z Science Derived Particles Ions Plasma Juno Mission urn:nasa:pds:context:investigation:mission.juno data_to_investigation Juno Host urn:nasa:pds:context:instrument_host:spacecraft.jno is_instrument_host Jovian Auroral Distributions Experiment Instrument urn:nasa:pds:context:instrument:jade.jno is_instrument Jupiter Planet urn:nasa:pds:context:target:planet.jupiter data_to_target Ions Density Ions Velocity Ions Temperature Ions Thermal Pressure 10.1016/j.icarus.2024.116006 Wilson, R.J. (2024), Jovian current disk crossings as observed by Juno JADE-I, Icarus, 413, 116006 This paper investigates jovian current disk properties utilizing two complementary Juno JADE-I data sets. We set out to extract plasma parameters for multiple ion species: H+, S+, S+++, O++ and O+ or S++. The JADE-I Time-of-Flight (TOF) sensor has little directional information yet can separate out ion species by mass per charge, however O+ and S++ have the same mass to charge so are represented by a single average ion of equivalent mass per charge. The JADE-I SPECIES data set has coarse mass per charge information yet is directional. By utilizing both data sets we can extract densities, velocities and temperatures using forward model techniques and assuming a Maxwellian distribution. However, it became apparent that the proton distributions were inadequately represented by a single Maxwellian distribution, being far too broad in energy and/or having multiple distributions, such that numerical moments were used to derive proton properties. The forward model technique was used on the remaining heavy ions, with a singular distribution for each ion species but a shared velocity. Both Maxwellian and Kappa distributions were investigated to see how well they represented the data. While a high energy tail can be readily observed in the TOF data set, the signal was low, and it was difficult to identify the same tail in the SPECIES data set. After investigation, it was found that assuming Kappa distributions had little benefit over assuming Maxwellian distributions, therefore the main forward model analysis was carried out assuming 4 co-moving Maxwellian distributed heavy ion species. The main study was for Juno orbits 5 to 34, where the trajectories had full current disk crossings outside of 20 jovian radii. Comparing the velocities of the heavy ion fits to the protons numerical moments gave good agreement, endorsing both analysis techniques. Radial profiles of plasma parameters of the current disk are provided, that highlight how the O+ and S++ ions are the dominant ion species with relative ion composition fixed over these radial distances. If the heavy ions were to be treated as an average single ion species, they would have a mass to charge of 15.1 amu/q for the radial range 23–63 jovian radii. MOMENTS_PROTONS_10MIN.CSV 2025-12-08 67479873 a409c73c1f838ee06bf4451c63724de9

0 423 PDS DSV 1

423 PDS DSV 1 236770 Carriage-Return Line-Feed Comma 26 0 UTC 1 ASCII_Date_Time_DOY_UTC UTC UTC timestamp at center (not start) of record. Format is yyyy-dddTHH:MM:SS.sssZ where yyyy = year, ddd = day of year, HH = hour, MM = minute, SS.sss = decimal seconds to millisecond resolution. Note: Duration of record can be found in seconds from ACCUMULATION_TIME. This record really covers the period starting at UTC - ACCUMULATION_TIME/2 (inclusive) and ending at UTC + ACCUMULATION_TIME/2. 0001-001T00:00:00.000Z ACCUMULATION_TIME 2 ASCII_Integer %3d s Accumulation Time. Number of spacecraft clock ticks (assume seconds) over which the data in this product was collected. -1 600 30 PACKET_MODE 3 ASCII_Integer %1d Packet Mode, describes type of data telemetry. 1 = LRS / Low Rate Science 2 = HRS / High Rate Science 3 = DRS / DeRived Science from LRS and/or HRS 9 = Unknown 9 3 3 SOURCE_BACKGROUND 4 ASCII_Integer %1d Source of Background values that have been removed from the DATA object. 0 = None: No background has been removed 1 = Background anode (electron sensors only) 2 = Background anode (JADE-I only) 3 = Derived from Background anode : Method 1: Background coefficients are time independent. See file in CALIB directory of Level 3 files for description. 4 = Derived from Background anode : Method 2: Background coefficients are per orbit. See file in CALIB directory of Level 3 files for description. 9 = Unknown. 9 4 4 FILE_VERSION 5 ASCII_Integer %1d The version number of the file this record came from. e.g., if you loaded file JAD_L30_LRS_ION_ANY_CNT_2016240_V04.DAT then FILE_VERSION = 4. 0 4 4 N_CC 6 ASCII_Real %8.5f 1/(cm^3) Proton Number density in units of 1/cm^3. -9.99999 99.99999 0.00001 N_SIGMA_CC 7 ASCII_Real %8.5f 1/(cm^3) Proton Number density uncertainty in units of 1/cm^3. -9.99999 99.99999 0.00001 V_JSSRTP_KMPS_R 8 ASCII_Real %10.3f km/s Proton Velocity R component in the JSSRTP frame, in km/s. -99999.999 4000.000 -4000.000 V_JSSRTP_KMPS_T 9 ASCII_Real %10.3f km/s Proton Velocity T component in the JSSRTP frame, in km/s. -99999.999 4000.000 -4000.000 V_JSSRTP_KMPS_P 10 ASCII_Real %10.3f km/s Proton Velocity P component in the JSSRTP frame, in km/s. -99999.999 4000.000 -4000.000 V_JSSRTP_SIGMA_KMPS_R 11 ASCII_Real %10.3f km/s Proton Velocity R component uncertainty in the JSSRTP frame, in km/s. -99999.999 990000.000 0.010 V_JSSRTP_SIGMA_KMPS_T 12 ASCII_Real %10.3f km/s Proton Velocity T component uncertainty in the JSSRTP frame, in km/s. -99999.999 990000.000 0.010 V_JSSRTP_SIGMA_KMPS_P 13 ASCII_Real %10.3f km/s Proton Velocity P component uncertainty in the JSSRTP frame, in km/s. -99999.999 990000.000 0.010 PRESSURE_PA 14 ASCII_Real %14.7E Pa Proton Isotropic pressure in units of Pascals. -9.9999999E+04 1.0000000E-08 1.0000000E-20 PRESSURE_SIGMA_PA 15 ASCII_Real %14.7E Pa Proton Isotropic pressure uncertainty in units of Pascals. -9.9999999E+04 1.0000000E-08 1.0000000E-20 TEMP_EV 16 ASCII_Real %10.3f eV Proton Isotropic temperature in units of eV. -99999.999 999999.999 0.001 TEMP_SIGMA_EV 17 ASCII_Real %10.3f eV Proton Isotropic temperature uncertainty in units of eV. -99999.999 999999.999 0.001 ISSUES_0 18 ASCII_Integer %10d Issues or potential issues in this data record. These are issues that can be identified within the JADE packet of data itself without any external information. e.g. timing issues due to the MAG time stutter, or any voltage pulsing, would not be included as there are no indicators to them within this JADE packet. [For a more comprehensive list of potential issues from internal and external sources please see the Level 3 data.] Level 2 issues of this JADE packet are flagged by individual bits, and several may be hit. If no issues are flagged then this 4-byte unsigned integer is zero. A value of 4294967295 is the MISSING_CONSTANT and means that the issue status is currently unknown. All bits at 0 implies all is okay as seen by this packet. If a bit is set to 1 then that bit is flagged, otherwise it is set to zero and unflagged. The bits are set as followed, grouped in to seriousness: Not very serious issues for doing science: Bit 0 = UTC time is predicted, yet to be finalized. Bit 1 = Position/Orientation values predicted, yet to be finalized. Level 3 (and above) data only. Bit 2 = TABLES_VERSION object was altered on the ground to accurately reflect a commanded parameter update outside the initial per-orbit commands JADE is returning. [If changed, the original downlinked TABLES_VERSION value can be found by cross- referencing the PARAM_TABLE_VER object in the JAD_L20_HSK_ALL_SHK files. Note here the PARAM_TABLE_VER value is given as a unsigned integer of Hex Major-Middle-Minor, such that a value of 770 decimal is in hex 0x302, meaning Table Version 3.02 ] Bit 3 = FSW_VERSION 4.00 LRS/CAL Ion Species bug fixed on the ground by adjusting TIMESTAMP_WHOLE, TIMESTAMP_SUB, and ACCUMULATION_TIME based on cross-referencing JADE commanding. Bit 4 = LRS/CAL Ion Species record with unobserved look directions (views) populated using views from neighboring record. See Bit 12 for uncorrected/unpopulated description. (Only possible if ACCUMULATION_TIME = 30.) Bit 5 = TIMESTAMP_WHOLE/SUB adjusted on the ground to mitigate any Juno time stutter effects. [Other TIMESTAMPs are susceptible to the onboard time stutter too, but only the JADE packet TIMESTAMP_WHOLE/SUB is tracked here.] Bit 6 = Currently unused. Bit 7 = Warning, a leap second occurs during the accumulation period. Data slightly different than expected, but can be used for science with a little extra coding: Bit 8 = ACCUM_TRUNCATION object flagged. Bit 9 = Electron (HRS/LRS/CAL) MAG objects are not tracked, are either zeros or MISSING_CONSTANT. [LRS and CAL did not have MAG objects prior to FSW_VERSION 4.10, therefore those MAG objects here are set to MISSING_CONSTANT when FSW_VERSION < 4.10.] Bit 10 = TIMESTAMP_WHOLE/SUB affected by a Juno onboard time stutter, JADE reported timestamp is likely 1 whole tick too large. [Other TIMESTAMPs are susceptible to the onboard time stutter too, but only the JADE packet TIMESTAMP_WHOLE/SUB is tracked here.] Bit 11 = Currently unused. Bit 12 = LRS/CAL Ion Species record potentially has unobserved look directions (spin phase sectors or views) present in the data, meaning the record may not contain data for a full 4pi steradians field-of-view. Unobserved look directions have zero counts per view (or counts per second) in the data, although an observed look direction may also have zero counts if no ions were measured. Therefore there is a potential confusion over zero measured counts or simply unmeasured. e.g. if the spin period is 30.7 seconds, then not all of the 78 spin phase sectors will be sampled in 30 seconds. (Unobserved views are only possible if ACCUMULATION_TIME <= 30.) See the JADE SIS for more information. Bit 13 = At least one anode is blanked. See SIS document for further information. Bit 14 = FSW_VERSION 4.00 LRS/CAL Ion Species bug warning: Not fixed as yet - when fixed it will become bit 3 of ISSUES instead. Level 2 data only when FSW_VERSION = 4.00, ACCUMULTION_TIME object is MISSING_CONSTANT. Also, TIMESTAMP_WHOLE:TIMESTAMP_SUB is the end of the packet rather than the usual start, see TIMESTAMP_WHOLE object for more details. [Only affects data from 2015-089 to 2015-115.] Bit 15 = Electron Anodes Reversed. Level 2 data only when FSW_VERSION < 4.10 and only electron packets. Electron anodes are reversed in order and need to be remapped, however electron Spin Phase data (LRS data) cannot be remapped. See the SIS document for more information about this. [Affects all electron data 2011 to 2015-115.] Data very different than expected, may not be suitable for science - use with extreme caution. Bit 16 = Data is not from flight instrument on Juno, see FLIGHT_OR_STL object. Bit 17 = MCP_NOT_AT_COMMANDED object flagged. Electron HRS/CAL/HVE packets use all three electron sensors and therefore have three MCP_NOT_AT_COMMANDED values per packet. Setting this flag means at least one of those three mcps is not at its commanded value. Bit 18 = Data includes some JADE-E300 sensor data. (Only flagged for HRS, LRS, CAL and HVE data.) E300 has a high voltage power supply issue and reported energy steps may be incorrect. If E300 is off but still reported in the data product, it may be zeros of fill values. Bit 19 = Ion packet abruptly truncated. This packet should not be used. It had an ACCUMULATION_TIME = 1, ACCUM_TRUNCATION = 1 and the DATA object is all zeros, with a timestamp that matches an earlier valid packet that was not truncated and has non-zero DATA. e.g. TOF and LOG example in level 2 data at TIMESTAMP_WHOLE of 495879710 (UTC 2015-261). Bit 20 = MCP Dipping Triggered, in one or more sensors. If the sensor measures excessive counts, it temporarily lowers the MCP voltage to reduce the number of counts and protect the sensor. The MCP_NOT_AT_COMMANDED object is also flagged (Bit 17 in ISSUES) since the MCP is no longer at the commanded voltage. For HRS/CAL/HVE electrons (datasets where multiple sensors are on) it is possible that one sensor has been dipped, but the others are not and still providing good data. (First MCP dip was HRS electrons, 2017-350.) Bit 21 = MCP Dipped sensors DATA set to fill values. If MCP dipping has triggered (Bit 20 of ISSUES) then: DATA and BACKGROUND objects (and their *_SIGMAs) have been replaced with MISSING_CONSTANT values. (Never used for Level 2 data, which has the counts as measured in the dipped state.) In addition, Bit 17 of the ISSUES object (i.e. MCP_NOT_AT_COMMANDED object = 1) is set to zero, and, if it exists, the MCP_NOT_AT_COMMANDED object itself is changed (from 1) to be 0 for the offending sensor(s). If the DATA object contains data from multiple sensors (HRS/CAL/HVE electrons) then only the elements of the DATA object for the dipped sensor are set to MISSING_CONSTANT (as identified by the MCP_NOT_AT_COMMANDED value for each sensor (prior to setting them to 0)). [See Bit 22 for a similar flag.] Bit 22 = 1 or more ELC sensor DATA set to fill values. Affects only electron HRS/CAL/HVE products (i.e. products that use multiple sensors), and generally only when starting that mode. When switching to HRS/CAL/HVE from LRS, one JADE-E sensor is already on, and the other(s) have to turn on, then it takes some time for that sensor to reach the commanded voltage. For a given record, MCP_NOT_AT_COMMANDED = 0 for one sensor but is still = 1 for others. That is one sensor is taking valid science but the other(s) are not there yet and for those sensors: DATA and BACKGROUND objects (and their *_SIGMAs) have been replaced with MISSING_CONSTANT values. (Never used for Level 2 data, which has the counts as measured in the dipped state.) In addition, Bit 17 of the ISSUES object (i.e. MCP_NOT_AT_COMMANDED object = 1) is set to zero, and, if it exists, the MCP_NOT_AT_COMMANDED object itself is changed (from 1) to be 0 for the offending sensor(s). Only the elements of the DATA object for the original MCP_NOT_AT_COMMANDED = 1 sensor(s) (prior to setting them to 0) are set to MISSING_CONSTANT. [Bits 21 and 22 are essentially the same feature caused by an mcp voltage not being at the commanded value, but the reason why this is the case is different. The treatment is identical for both Bit 21 and Bit 22.] Bit 23 = Currently unused. Bit 24 = Currently unused. Bit 25 = Currently unused. Bit 26 = Currently unused. Bit 27 = Currently unused. Bit 28 = Currently unused. Bit 29 = Currently unused. Bit 30 = Currently unused. Bit 31 = Reserved for MISSING_CONSTANT use. Each bit has a decimal value of 2^{bit number}, and the Issues flag is the sum of 2^{flagged bit numbers}. For instance, if this ISSUES flag = 131329, then in binary that value is 00000000000000100000000100000001 showing bits 17, 8 and 0 are flagged. [If a currently unused bit is set, please check the latest LBL file for this product that you can find to see if it now has a definition.] 4294967295 2147483647 0 ISSUES_1 19 ASCII_Integer %10d See Description for ISSUES_0. 4294967295 2147483647 0 SC_POS_R 20 ASCII_Real %7.3f Jupiter Radii Juno radial distance at time UTC, from Jupiter, in units of Jupiter Radii (Rj). (1 Rj = 71492.0 km) -99.999 130.000 0.000 SC_POS_LAT 21 ASCII_Real %7.3f deg Juno Latitude at time UTC, in both the IAU_JUPITER and JUNO_JSS frames, in units of degrees. (0 = Equatorial) (JUNO_JSS is a despun version of IAU_JUPITER, hence they have identical latitudes.) -99.999 90.000 -90.000 SC_POS_LOCAL_TIME 22 ASCII_Real %6.3f hr Junos (jovian) Local Time at time UTC, in units of hours. 00 = Midnight 06 = Dawn 12 = Noon 18 = Dusk -9.999 24.000 0.000 SC_POS_SYSIII_ELONG 23 ASCII_Real %7.3f deg Junos (jovian) SYSIII (East) Longitude at time UTC, in units of degrees. -99.999 360.000 0.000 EV_PER_Q_RANGE_0 24 ASCII_Real %9.3f eV Energy Range of sensor(s) (eV/q) from lower to upper is given by EV_PER_Q_RANGE_0 to EV_PER_Q_RANGE_1. Each JADE sensor has its own energy range, and these do vary over time, with occasional significant changes of energy tables. This object is to give context to the moments, in particular, what energy range were moments calculated over. -9999.000 50000.000 0.000 EV_PER_Q_RANGE_1 25 ASCII_Real %9.3f eV See Description for EV_PER_Q_RANGE_0. -9999.000 50000.000 0.000 Quality Flag 26 ASCII_Integer %2d "Good" Quality Flag. 0 = Not a Good result 1 = Probably a Good result -1 = Unknown = MISSING_CONSTANT -1 1 0