Documentation (SIS)
- Page 2 Table 1-1. Recommend adding DSN SIS documents (TRK-2-34, TRK-2-24, TRK-2-25)
- Are the antenna phase center locations avaiable (Table 2-4)?
- Was the transponder delay measured or have a requirement (Section 2.1.3.1)?
- 2.3.2 The skyfreq files are not a standard DSN product and thus aren't documented in the radio science documentation bundle. Some description of how they are produced would be helpful. Similary, TRK-2-34 files as delivered by the DSN are not really PDS compliant as the radio science documentation bundle points out. I recommend a statement for pre-processing before archival stating the records were sorted by data type to improve PDS4 labeling. These are all stated below in Section 3 but a breif statement here would be helpful, or at least refer the reader to Section 3.
- 2.3.2.1 Calibrated Data product generation. this seems like a leftover section from a template since there are no calibrated data products. Remove?
- 2.3.3 Data flow. This section is empty, is it intended to be removed or have some content?
- 3.2.2 Small Forces. Text states there is a SIS provided in the documentation bundle, but it is missing. The collection refers to OREX SFF SIS. This SIS does not mention Lucy in it, and that SIS has multiple formats depending on the spacecraft. The data labels themselves specify that the format is the same as ORX and the labels appear to properly describe the data. However, the Lucy files have 31 columns yet the ORX SFF SIS specifies 47 columns and ORX data have 47 columns. This should be explained somehow.

data_dinkinesh_ion
- data content and labels look good
- coverage Sept 2023 to Oct 2023. There are TNF files in the month of November. Is it possible to add the November 2023 ION calibration file?
- each file covers one month duration per DSN standard delivery
- there are multiple files that cover the same months, but with updated data. I don't see a strong reason to have archived multiple versions of the same coverage window, only the latest ones should be archived. Leaving all versions in would lead to confusion. If data providers want to archive multiple of the same data coverage window I would recommend adding a statement into the SIS to only use the latest delivery date file.

data_dinkinesh_sff
- data files look good, see documentation comments about secondary document in document collection (SFF SIS)

data_dinkinesh_skyfreq
- labels contain internal reference to small forces. i think this is an oversight and actually belongs in the SFF labels.
        <Internal_Reference>
            <lid_reference>urn:nasa:pds:orex.radioscience:document:naf018</lid_reference>
            <reference_type>data_to_document</reference_type>
            <comment>
                Although this document does not explicitly pertain to Lucy, its content is still applicable.
                Until a new version of this document is created for Lucy, this reference will have to suffice.
            </comment>
        </Internal_Reference>
- label <description> makes reference to a SOURCE_PRODUCT_ID but I can't find that anywhere else in the label. the description also makes reference to S-band which Lucy is not capable of. Can the description be updated?
- column DISTANCE doesn't seem correct (2.26 km?)
- column DIFFERENTIAL DOPPLER states that if invalid it will be -999.999999 yet the value is actually zero in the files

data_dinkinesh_trk234
- Data coverage is Sept 2, 2023 to Nov 6, 2023
- I confirmed the data file is properly sorted
- Data file labels also appear correct