SeaHawk/Hawkeye L1B not a valid input mission

[daurin]

Goal: Automate processing of Hawkeye to L2 and beyond using non-default settings (e.g., output rhos_752 or turn off cloud masking) necessitating scripted command line interface L1A->L2. First attempts to process using default settings fails in both the GUI and CLI.
____________________________________
System: MacOS Ventura 13.4, SeaDAS 8.3.10, OCSSW
____________________________________
Initial Steps: Download L1A from Level 1&2 Browser. Process to L1B, either using SeaDAS GUI or command line interface. No apparent errors.
____________________________________
Problem: Opening L1B in SeaDAS GUI asks for NetCDF format (Generic vs. CF-Convention), but L1B file appears okay either way in GUI (e.g., displays Bands as expected) until trying to use GUI>SeaDAS-Toolbox>SeaDAS Processors>l2gen, when it reports that the file is not recognized as a valid mission and GUI interaction to most features is disabled:

"# PRIMARY INPUT OUTPUT FIELDS
ifile=/Users/daurin/Megalink/SeaHawk/L1B/SEAHAWK1_HAWKEYE.20230512T213239.L1B.hdf
# # WARNING!!! File /Users/daurin/Megalink/SeaHawk/L1B/SEAHAWK1_HAWKEYE.20230512T213239.L1B.hdf is not a valid input mission: Mission=null


# SUITE
suite=OC

# ANCILLARY INPUTS Default = climatology (select 'Get Ancillary' to download ancillary files)"
____________________________________
Tried: Process using command line l2gen:

Code: Select all

l2gen --ifile=/Volumes/Megalodon/SeaHawk/L1B/SEAHAWK1_HAWKEYE.20230512T213239.L1B.nc --geofile=/Volumes/Megalodon/SeaHawk/L1A/SEAHAWK1_HAWKEYE.20230512T213239.GEO --ofile=/Volumes/Megalodon/SeaHawk/L2/SEAHAWK1_HAWKEYE.20230512T213239.L2.OC.nc

Interestingly, this appears to recognize the L1B as Hawkeye, and appears to work:

"Loading default parameters from /Users/daurin/Applications/ocssw/share/common/msl12_defaults.par
Input file /Volumes/Megalodon/SeaHawk/L1B/SEAHAWK1_HAWKEYE.20230512T213239.L1B.nc is a NetCDF4 HAWKEYE L1B file.

Loading characteristics for HAWKEYE
Opening sensor information file /Users/daurin/Applications/ocssw/share/hawkeye/msl12_sensor_info.dat
Bnd Lam Fo Tau_r k_oz k_no2 t_co2 awhite aw bbw
0 412.000 173.272 3.176e-01 2.539e-04 6.042e-19 1.000e+00 0.000e+00 4.840e-03 2.953e-03
1 447.000 196.058 2.267e-01 3.553e-03 4.780e-19 1.000e+00 0.000e+00 8.042e-03 2.090e-03
2 488.000 198.810 1.585e-01 2.069e-02 2.938e-19 1.000e+00 0.000e+00 1.493e-02 1.440e-03
3 510.000 187.653 1.322e-01 4.136e-02 2.087e-19 1.000e+00 0.000e+00 3.218e-02 1.193e-03
4 556.000 183.098 9.294e-02 9.903e-02 9.124e-20 1.000e+00 0.000e+00 5.971e-02 8.316e-04
5 670.000 150.871 4.334e-02 4.454e-02 7.967e-21 1.000e+00 0.000e+00 4.417e-01 3.806e-04
6 752.000 127.079 2.728e-02 9.505e-03 1.530e-21 1.000e+00 0.000e+00 2.856e+00 2.372e-04
7 867.000 95.258 1.540e-02 2.108e-03 3.778e-23 1.000e+00 0.000e+00 4.742e+00 1.322e-04


Loading default parameters for HAWKEYE from /Users/daurin/Applications/ocssw/share/hawkeye/msl12_defaults.par
Loading parameters for suite OC from /Users/daurin/Applications/ocssw/share/hawkeye/msl12_defaults_OC.par
Loading command line parameters

Loading user parameters for HAWKEYE

Internal data compression requested at compression level: 4
Opening filter file /Users/daurin/Applications/ocssw/share/hawkeye/hawkeye_filter.dat
Setting -1 x 5 straylight filter on HILT mask

Filter Kernel
[...]
Minimum fill set to 13 pixels


Reading Thuillier_F0.dat
L1B Npix :1800 Nscans:5936
Allocated 1819832 bytes in L1 record.
Allocated 705600 bytes in L2 record.

Opening: /Volumes/Megalodon/SeaHawk/L2/SEAHAWK1_HAWKEYE.20230512T213239.L2.OC.nc


The following products will be included in /Volumes/Megalodon/SeaHawk/L2/SEAHAWK1_HAWKEYE.20230512T213239.L2.OC.nc.
0 aot_867
1 angstrom
2 Rrs_412
3 Rrs_447
4 Rrs_488
5 Rrs_510
6 Rrs_556
7 Rrs_670
8 chlor_a
9 Kd_490
10 pic
11 poc
12 l2_flags"

However, the GUI cannot open the L2 file:

L2_fail.jpg (71.4 KiB) Not viewed yet

[OB SeaDAS - knowles]

For processing HawkEye to level-2 you can use the GEO file and the L1A file as inputs to l2gen. You don't need the L1B file for processing HawkEye to level-2. This behavior of using GEO and L1A files as input to l2gen is similar to VIIRS processing. Each mission can be somewhat unique in the pre-level2 phases of processing.

[daurin]

Good to know. Thanks!