Earthdata Forum

In past month, I can use SeaDAS 8.1/OCSSW and HawkEye L1A files as input to create
Geolocation files (via geolocate_hawkeye).

Then used L1brsgen to further produce good looking browse files.

Now found no good looking browse files been processed anymore from recent L1A files
since Oct 25th (see attached pictures).

Several tests shown:
Now using 20211024 L1A files can still produce good browse files.
But using 20211025 L1A files (or newer) can't create good browse files.

Something changed in SeaHawk L1A files after Oct 25th ?

Thanks for help !

Found problems due to unmatched output filename:

input: SEAHAWK1_HAWKEYE.20211025T142126.L1A.nc
Geo: SEAHAWK1_HAWKEYE.20211025T142125.GEO.nc (SeaDAS gave default filename from geolocate_hawkeye)

execution exception: java.io.IOException: l1brsgen failed with exit code 1.
Check log for more details.
-E- Error opening GEO file "/home/test/SEAHAWK1_HAWKEYE.20211025T142126.GEO.nc": No such file or directory
Loading default parameters from /home/wang/ocssw/share/common/msl12_defaults.par
Loading default parameters from /home/wang/ocssw/share/common/l1brsgen_defaults.par
Input file /home/test/SEAHAWK1_HAWKEYE.20211025T142126.L1A.nc is HAWKEYE L1A file.
. . . . . .

After renamed output geofile from "142125" to "142126", the l1brsgen program completed.

Thanks for reporting the bug, we just fixed it. It'll be in the next operational tag of OCSSW.