Missing Key Trios Files: Seeking Alternatives to Generate L1B Data from L1AQC

[kikkty]

Hello everyone,
I am currently processing a dataset from Trios. However, I have encountered a critical issue while advancing from the L1AQC processing stage to L1B — I am missing the following key files required for Trios. I would like to seek help from all seniors and colleagues: If these essential files are not available, are there any feasible alternative solutions or workarounds to successfully generate the L1B data?

Looking forward to your replies. Thank you very much!

[oceancolorcoder]

Hello @kikkty,

Sorry you're having trouble processing your data. Those files are the radiometric characterizations for the TriOS instruments with serial numbers 8166, 8329, and 8595. These are the three radiometers used in the sample dataset provided with the software with configuration "sample_TRIOS_NOTRACKER". They are also provided with the repository when you download it and can be found here: https://github.com/nasa/HyperCP/tree/master/Data/FidRadDB/TriOS. Is this the dataset you are trying to process, or are you trying to process your own data with different radiometers? If you are using your own radiometers and they have been characterized (e.g., at U. Tartu), the files can be downloaded from the FidRadDB via the HyperCP interface:

If not, you will need to select Non-FRM processing in that same window.

Hope this helps.

[kikkty]

Hello @oceancolorcoder
First of all, thank you so much for your previous helpful advice. The method you recommended worked perfectly—by selecting the non-FMR mode as suggested, I was able to continue with the data processing smoothly, which really saved me at that critical moment.
However, while processing the data from the L1AQC stage to L1B, I encountered a new issue: the output files are missing content related to the 6smodel and raw uncertainty. These two components are crucial for further in-depth data analysis, and their absence is currently preventing me from moving forward with subsequent work.
To help pinpoint the problem, I have attached the corresponding L1A raw files. I would greatly appreciate it if you could take a look and advise whether the issue lies in parameter configuration, the processing workflow, or file associations.
Thank you once again for your generous support. I look forward to your reply!
https://drive.google.com/file/d/1UjrSmvdJXVc9vlAs4I9O5CPx-F2ftc9J/view?usp=drive_link

[oceancolorcoder]

Good morning,
Please include the following:

1. Any error messages encountered while trying to process your data from L1AQC to L1B. A processing log can be found in HyperCP/Logs.
2. Are you able to process the provided sample datasets to L2 without error?
3. Is your conda environment set up to include the sixs_json module? The environment is built as described in the README using the environment.yml file that includes j6s (a json wrapper for the 6S model). In your terminal, type:

conda activate hypercp
conda list sixs_json

You should see the module as:

# packages in environment at /Users/daurin/miniforge3/envs/hypercp:
#
# Name                    Version                   Build  Channel
sixs_json                 1.0.0                hcac9adc_1    conda-forge

The path will be to your conda environments on your machine.