Software Interface Specification . - PDS Imaging Node
JunoSoftware Interface SpecificationJunoCam Standard Data ProductsM. CaplingerMalin Space Science Systems, Inc.Approved by:Candy Hansen, JunoCam Team LeaderLeslie Lipkaman, MSSS JunoCam Archiving LeadDave Gell, JSOC ManagerWilliam Kurth, Juno ArchivistSue Lavoie, PDS Imaging NodeVersion 1.3, August 2016(formatted August 31, 2016)
Change LogDATE11/14/13SECTIONS CHANGEDDESCRIPTION OF CHANGESREVISIONInitial Release, Version 1.012/08/14Signature Page, Change Log, 1.4.4, 2.1,4.1, 4.2, 4.3, 4.3.2, Appendix A, B, C07/31/15Acronyms and Abbreviations, 1.1, 1.2,1.3, 1.4, 2.3, 2.4, 4.1, 4.2, 4.3, 4.3.1.3,Appendix A, B, C08/31/164.2, Appendix DSignature Page: addedChange Log: added1.4.4: section removed from V1.0,section numbers shifted2.1: added section on InstrumentOverview4.1: updated DATA SET IDs4.2: updated generic LBL file4.3: updated keywords4.3.2: expanded sectionAppendix A, B, C: added newappendicesAcronyms and Abbreviations: added1.1: updated acronyms1.2 : updated acronym1.3: added numbers for reference1.4: section removed from V1.1,section numbers shifted2.3: updated acronyms2.4: updated acronym4.1: updated section with peer reviewinputs, updated acronyms4.2: changed section title, updatedwith peer review inputs4.3: replaced generic LBL file with areal LBL file4.4: section has been moved to tableformat in Appendix A4.3.1.3: added section with peerreview inputsAppendix A: new appendix (section4.3 from V1.1)Appendix B: new appendix with peerreview inputsAppendix C: updated appendix withpeer review inputs (originallyAppendix A in V1.1)4.2: modified the PICNO structure toinclude 5 characters for the imageindexAppendix D: removed the Global MapSIS listing and files from theCATALOG, DATA, and DOCUMENTdirectories as this has not yet beenpeer reviewed and therefore will notbe included in the volumei1.11.21.3
Contents1. INTRODUCTION . 41.1. PURPOSE . 41.2 SCOPE . 41.3 APPLICABLE DOCUMENTS . 41.4. FUNCTIONAL DESCRIPTION. 41.4.1. Data Content Summary . 41.4.2. Source and Transfer Method . 41.4.3. Recipients and Utilization . 51.5. ASSUMPTIONS AND CONSTRAINTS . 52. ENVIRONMENT . 52.1. INSTRUMENT OVERVIEW . 52.2. HARDWARE CHARACTERISTICS AND LIMITATIONS . 52.2.1. Special Equipment and Device Interfaces . 52.2.2. Special Setup Requirements . 52.3. FAILURE PROTECTION, DETECTION, AND RECOVERY . 62.4. END-OF-FILE CONVENTIONS . 63. ACCESS . 63.1. ACCESS TOOLS . 63.2. INPUT/OUTPUT PROTOCOLS . 63.3. TIMING AND SEQUENCING CHARACTERISTICS. 64. DATA PRODUCT OVERVIEW . 64.1 DATA PROCESSING LEVELS . 64.2. FILE NAMING CONVENTION . 74.3. STRUCTURE AND ORGANIZATION . 84.4. SUBSTRUCTURE DEFINITION AND FORMAT . 94.3.1. Data Description Details . 94.3.1.1. Filter order . 94.3.1.2. Geometry . 104.3.1.3. RDR processing flow . 104.3.2. Data loss considerations . 104.4. DATA VOLUME, SIZE, AND FREQUENCY ESTIMATES .115. PDS ARCHIVE VOLUME . 115.1 ARCHIVE STRUCTURE .116. APPENDICES . 12APPENDIX A – JUNOCAM KEYWORDS, DEFINITIONS, AND VALID VALUES & ENTRIES .12APPENDIX B – FILTER COMBINATIONS .23APPENDIX C – JUNOCAM COMPANDING TABLES .23APPENDIX D – ARCHIVE VOLUME STRUCTURE .30ii
Acronyms and KCharged Coupled DeviceCSSDS File Delivery ProtocolCommittee on Data Management and ComputationConsultative Committee for Space Data SystemsDeep Space NetworkExperiment Data RecordEarth FlybyInterface Control DocumentIdentificationInstrument Operations TeamJunoCamJet Propulsion LaboratoryJuno Science Operations CenterLinear inverseMission Operations FacilityNot applicableNational Aeronautics and Space AdministrationPlanetary Data SystemReduced Data RecordStandard Format Data UnitSoftware Interface SpecificationSpacecraft, Planet, Instrument, C-matrix Events kernelsSquare rootTo be determinedUnknowniii
1. Introduction1.1. PurposeThis document describes the format of the JunoCam Experiment Data Record (EDR) and ReducedData Record (RDR) Planetary Data System (PDS) Data Products.1.2 ScopeThe format and content specifications in this Software Interface Specification (SIS) apply to allphases of the project for which this product is available.1.3 Applicable DocumentsThis SIS is consistent with the following PDS documents:1. Planetary Data System Standards Reference, Version 3.8, JPL D-7669, Part 2, February 27,2009.2. Planetary Science Data Dictionary Document, JPL D-7116, Rev. F, October 20, 2008.Additionally, this SIS makes reference to the following documents for technical and backgroundinformation:3. JUNO Science Operations Center (JSOC) JSOC-IOT Interface Control Document, 12029.02JSOC IOT ICD-01, Rev 4 Chg 0, October 2013.4. Software Interface Specification JunoCam Global/Regional Map Image Standard DataProduct, M. Caplinger, Version 1.0, November 14, 2013.5. Juno Project Mission Plan, Revision B, JPL D-35556, 29 March 2011.1.4. Functional Description1.4.1. Data Content SummaryEach JunoCam standard data product is a single image contained in one file, in the raw imageformat as produced by the instrument. The EDR product has been depacketized, decompressedand reformatted with standard labels, but is otherwise "raw"; that is, as received from theinstrument. The RDR product is similar, but has been corrected for instrument signature andconverted to scaled radiance.1.4.2. Source and Transfer MethodJunoCam products are produced by the junomakepds' program from the format internally usedat the JunoCam Mission Operations Facility (MOF). This program reads a raw JunoCam imagefile, extracts various information from its headers, creates an image product (.IMG) with aformatted detached PDS label (.LBL).4
This data format is potentially used in three contexts: on the JunoCam web site, after archivingfrom the PDS, and as delivered to JSOC [Ref 3].1.4.3. Recipients and UtilizationThese products will be available to JunoCam team members, the Juno science community, theplanetary science community, and any other interested parties. In general, there is noproprietary period for JunoCam data.These products will be used for engineering support, direct science analysis, and/or theconstruction of other science products.1.5. Assumptions and ConstraintsNote that image products contain decompressed image data. The images are not corrected forthe effects of spacecraft motion or imaging geometry. Although there is enough information inthe header to do some processing, for more sophisticated processing ancillary files will berequired. These ancillary files are not described in this document. Examples of ancillary files arecalibration files, viewing geometry files (e.g., SPICE kernels), image index tables, etc.2. Environment2.1. Instrument OverviewJunoCam is a framing camera with a 1600x1200 pixel interline transfer CCD (Kodak KAI-2020M)with 7.4-micron square pixels illuminated by a single all-refractive 58-degree lens. A color filterarray with four different bandpasses (visible red/green/blue and narrowband methaneabsorption at about 890 nm) is directly bonded to the CCD. A typical image consists of one tofour "framelets", each 1648 pixels wide and 128 pixels high, in each of these bandpasses. Theframelets can be optionally summed by 2x in both directions to improve their signal-to-noiseratio. Either Huffman (lossless) or Integer Cosine Transform (lossy) image data compression canbe applied by software running in the spacecraft computer.2.2. Hardware Characteristics and Limitations2.2.1. Special Equipment and Device InterfacesInterfaces to access either CD-ROM volumes or electronic file transfer are described elsewhere;for example, see the PDS Standards Reference [Ref 1].2.2.2. Special Setup RequirementsNo special setup requirements are needed.5
2.3. Failure Protection, Detection, and RecoveryRaw instrument telemetry will be archived by the Jet Propulsion Laboratory (JPL) on a to bedetermined (TBD) archival medium. These archives and depacketized compressed image datawill be archived at the JunoCam MOF.2.4. End-of-File ConventionsEnd-of-file labeling shall comply with Standard Format Data Unit (SFDU) standards; specifically,fixed-size records are used. The header explicitly contains the record offset of each sub-elementof the dataset, and the size of each sub-element can be computed from information in the header.3. Access3.1. Access ToolsExisting PDS image display programs can display these files.3.2. Input/Output ProtocolsNone identified.3.3. Timing and Sequencing CharacteristicsNone.4. Data Product Overview4.1 Data Processing LevelsThis documentation recognizes both the National Aeronautics and Space Administration (NASA)data processing scheme and the “Committee on Data Management and Computation” (CODMAC)data level numbering system. The JunoCam instrument EDRs are “NASA Level 0" (CODMAC –Edited Level 2), while JunoCam instrument RDRs are “NASA Level 1A” (CODMAC – CalibratedLevel 3). The following table presents a breakdown of the CODMAC and NASA data processinglevels.6
NASACODMACDescriptionPacket dataRaw - Level 1Telemetry data stream as received at the ground station, withscience and engineering data embedded.Level 0Edited - Level 2Instrument science data (e.g., raw voltages, counts) at fullresolution, time ordered, with duplicates and transmission errorsremoved.Level 1ACalibrated - Level 3Level 0 data that have been located in space and may have beentransformed (e.g., calibrated, rearranged) in a reversible mannerand packaged with needed ancillary and auxiliary data (e.g.,radiances with the calibration equations applied).Level 1BResampled - Level 4Irreversibly transformed (e.g., resampled, remapped, calibrated)values of the instrument measurements (e.g., radiances, magneticfield strength).Level 1CDerived - Level 5Level 1A or 1B data that have been resampled and mapped ontouniform space-time grids. The data are calibrated (i.e.,radiometrically corrected) and may have additional correctionsapplied (e.g., terrain correction).Level 2Derived - Level 5Geophysical parameters, generally derived from Level 1 data, andlocated in space and time commensurate with instrument location,pointing, and sampling.Level 3Derived - Level 5Geophysical parameters mapped onto uniform space-time grids.JunoCam’s DATA SET IDs for EDRs and RDRs contain references to both the CODMAC and NASAdata processing levels. See Appendix A for more information.4.2. File Naming ConventionEach product will have a file name of the form " id .IMG", where the ID is not to exceed 36characters. The ID will start with an alphabetic character and will consist of only alphanumericcharacters. Each file name will be unique across all JunoCam data product files.File names will be of the form:JNCT YYYYDDD OOFNNNNN VXX.ZZZJNC: JunoCamT: product type (E for EDR, R for RDR, and M for map product)YYYY: year at the start of image acquisitionDDD: day-of-year at the start of image acquisitionOO: orbit number (or 00 for all cruise products)F: filter combination specifier for the image (see Appendix B)NNNNN: image index within that mission phaseV: versionXX: version number starting with "01"ZZZ: file extension (can be IMG, LBL)7
4.3. Structure and OrganizationAll JunoCam images must be a multiple of 16 pixels in both width and height. Images are brokenup into sub-images (also called fragments), and each fragment is transmitted separately. Rawand predictively compressed images are reconstructed by concatenating all of their imagefragments and then processing; transform compressed images are processed a fragment at atime.A JunoCam data product consists of one image with decompression applied. For each image file,a header (or label in PDS terminology) identifies various properties of the image and contains afile offset to the data portion of the image. In addition, each image product has two parts: thedata product itself with the extension of “IMG” and a detached label with an extension of “LBL”.The following is a sample LBL for a JunoCam product from cruise:PDS VERSION ID PDS3/* FILE CHARACTERISTICS */RECORD TYPERECORD BYTESFILE RECORDS FIXED LENGTH 1648 5120/* POINTERS TO DATA OBJECTS */ IMAGE "JNCE 2013337 00R111 V01.IMG"/* IDENTIFICATION DATA ELEMENTS */FILE NAMESPACECRAFT NAMEMISSION PHASE NAMETARGET NAMEINSTRUMENT IDINSTRUMENT HOST NAMEINSTRUMENT NAMEPRODUCER IDDATA SET IDSTANDARD DATA PRODUCT IDPRODUCT CREATION TIMEPRODUCT VERSION IDPRODUCT IDSOURCE PRODUCT IDSTART TIMEIMAGE TIMESTOP TIMESPACECRAFT CLOCK START COUNTSPACECRAFT CLOCK STOP COUNT "JNCE 2013337 00R111 V01.IMG"JUNO"QUIET CRUISE"SPACE"JNC""JUNO""JUNO EPO CAMERA"JUNO JUNOCAM 5-07-13T20:16:14"1.0""JNCE 2013337 00R111 02.313"439304361:143""N/A"/* DESCRIPTIVE DATA ELEMENTS */ORBIT NUMBERSOFTWARE NAMEPROCESSING LEVEL IDFOCAL PLANE TEMPERATUREINTERFRAME DELAY "N/A""JUNOMAKEPDS.PY 0.4""2"264.1 K 0.741 s 8
SUB SPACECRAFT LATITUDESUB SPACECRAFT LONGITUDESPACECRAFT ALTITUDESOLAR DISTANCESAMPLE BIT MODE IDEXPOSURE DURATIONJNO:TDI STAGES COUNTSAMPLING FACTORFILTER NAMECOMPRESSION TYPERATIONALE DESC 0.00000.00000.0 km 2.0186e 08 km "SQROOT"512.000000 ms 801('RED')"INTEGER COSINE TRANSFORM""Cruise imaging" IMAGE51201648UNSIGNED 3fe7"IMAGE/* DATA OBJECT DEFINITIONS */OBJECTLINESLINE SAMPLESSAMPLE TYPELINE PREFIX BYTESLINE SUFFIX BYTESSAMPLE BITSSAMPLE BIT MASKMD5 CHECKSUMEND OBJECTEND4.4. Substructure Definition and FormatFor JunoCam label file (.LBL) keyword definitions and valid values, see Appendix A.4.3.1. Data Description Details4.3.1.1. Filter orderEach JunoCam frame acquired has 128/summing factor lines of image data per selected filter.The image defined by this document is ordered as follows: ----------------------------- frame 1, band 1 ----------------------------- frame 1, band 2 -----------.--------------- frame 1, band N ----------------------------- frame 2, band 1 ----------------------------- frame 2, band 2 -----------.--------------- frame 2, band N -----------.--------------- frame M, band 1 ----------------------------- frame M, band 2 -----------.--------------- frame M, band N ----------------------------- 9
This orders each frame by acquisition time and is the same order as the data produced
Data Record (RDR) Planetary Data System (PDS) Data Products. 1.2 Scope The format and content specifications in this Software Interface Specification (SIS) apply to all phases of the project for which this product is available. 1.3 Applicable Documents This SIS is consistent with the following PDS documents: 1.
DPDS3-PB-200017 - PDS ISOGEN Reference Guide, Vol. 1 DPDS3-PB-200022 - PDS Piping Component Data Reference Guide DPDS3-PB-200023 - PDS Project Setup Technical Reference DPDS3-PB-200025 - PDS Stress Analysis Interface (PD_Stress) User's Guide
This bulletin contains the PDS procedures which apply specifically to 2021 model year Camry and Camry Hybrid vehicles. A universal PDS Check Sheet that contains PDS steps that apply to all 2021 model year Toyota vehicles has been developed. To properly perform a complete PDS,
A PDS 'node' is a logical branch or sub-branch in the PDS hierarchy. A node starts with its node name, followed by ':' and contains (optional) sub-nodes and attributes, surrounded by '{'and'}'. A PDS 'attribute' is the end of a PDS hierarchy branch and corresponds to a firmware parameter.
experts should have PDS administration knowledge and be able to work with the Reference Data Manager. Both should read and understand this guide before configuring the PDS interface. Using SmartPlant Materials with PDS makes the creation of new pipe classes and modification of existing pipe classes more efficient, easier, and faster.
that is tailored to suit your personal circumstances. You should also read the PDS before making any decision about whether to acquire units in the Fund. The investment offered in the PDS and Additional information to the PDS is available only to persons receiving the PDS (electron
This is a Supplementary Product Disclosure Statement (‘SPDS’) for the Top 200 Product Disclosure Statement dated 7 April 2008 (‘PDS’). This SPDS must be read in conjunction with the PDS. The Issuer of the PDS and SPDS is Navigator Australia Limited ABN 45 006 302 987 AFSL 236466. Terms defined in t
1. Medical imaging coordinate naming 2. X-ray medical imaging Projected X-ray imaging Computed tomography (CT) with X-rays 3. Nuclear medical imaging 4. Magnetic resonance imaging (MRI) 5. (Ultrasound imaging covered in previous lecture) Slide 3: Medical imaging coordinates The anatomical terms of location Superior / inferior, left .
AGMA American Gear Manufacturers Association AIA American Institute of Architects. AISI American Iron and Steel Institute ANSI American National Standards Institute, Inc. AREA American Railway Engineering Association ASCE American Society of Civil Engineers ASME American Society of Mechanical Engineers ASTM American Society for Testing and .
