l2gen boundary arguments not working in SeaDAS8.1

[bbbarnes]

I recently switched from SeaDAS7.5.3 to 8.1.0. My workflow (all command line OCSSW) has stayed the same, but l2gen processing times ballooned with the new version. Upon investigating, I noticed that the l2gen boundary arguments now don't seem to do anything (full granules are processed regardless of boundary constraints). Below is one example for VIIRS/SNPP, but I've seen this behavior on MODIS/A, MODIS/T, VIIRS/J1, OLCI/A (both ERR and EFR), OLCI/B (both ERR and EFR), MERIS (both RR and FRS).

I ran this same command for SeaDAS7 andSeaDAS8:
> l2gen ifile=/work/b/bbarnes4/processing/workingX/V2021005180600/V2021005180600.L1B_SNPP ofile=/work/b/bbarnes4/processing/workingX/V2021005180600/V2021005180600.L2_SNPP.nc geofile=/work/b/bbarnes4/processing/workingX/V2021005180600/V2021005180600.GEO_SNPP south=23.75 west=-83.25 north=26.25 east=-79.75 l2prod="chlor_a Rrs_vvv l2_flags Lt_vvv Lr_vvv ozone solz senz" maskcloud=0 maskland=0 ozone1=/shares/cms_optics/apps/seadas/seadas-8.1/ocssw/var/anc/2021/005/N202100500_O3_AURAOMI_24h.hdf ozone2=/shares/cms_optics/apps/seadas/seadas-8.1/ocssw/var/anc/2021/006/N202100600_O3_AURAOMI_24h.hdf ozone3=/shares/cms_optics/apps/seadas/seadas-8.1/ocssw/var/anc/2021/006/N202100600_O3_AURAOMI_24h.hdf met1=/shares/cms_optics/apps/seadas/seadas-8.1/ocssw/var/anc/2021/005/N202100518_MET_NCEPR2_6h.hdf met2=/shares/cms_optics/apps/seadas/seadas-8.1/ocssw/var/anc/2021/006/N202100600_MET_NCEPR2_6h.hdf met3=/shares/cms_optics/apps/seadas/seadas-8.1/ocssw/var/anc/2021/006/N202100600_MET_NCEPR2_6h.hdf sstfile=/shares/cms_optics/apps/seadas/seadas-8.1/ocssw/var/anc/2021/005/N2021005_SST_OIV2AV_24h.nc icefile=/shares/cms_optics/apps/seadas/seadas-8.1/ocssw/var/anc/2021/005/N202100500_SEAICE_NSIDC_24h.hdf

For the SeaDAS7 run, the scan count ends with:
Processing scan # 2168 (451 of 467) after 29 seconds
For SeaDAS8, it ends:
Processing scan # 3200 (3201 of 3232) after 813 seconds

The attributes in the resultant L2 files show that the geographic arguments (south, north, east, west) weren't used:
In SeaDAS7 processed L2.nc file attributes:
north: 26.2500
south: 23.7500
east: -79.7500
west: -83.2500
In SeaDAS8 processed L2.nc file attributes:
north: -999.0000
south: -999.0000
east: -999.0000
west: -999.0000

I see that the north, south, east, and west still appear to be valid in the SeaDAS8 l2gen arguments list. Has their usage changed? Or is there some other option I'm not setting correctly?

Thanks in advance
-brian

[OB SeaDAS - xuanyang02]

You are right that current OCSSW l2gen processes full granules regardless of boundary constraints. It's fixed and will be released for the next OCSSW tag.

[bbbarnes]

Thanks so much. Glad to hear it's fixed. Is there a set timeframe for the next OCSSW tag?

[OB SeaDAS - xuanyang02]

You can try the development tag T2021.12 for now before the next operational(V) tag comes out.

[zhigang]

Brian, you could revert it to the previous version (V2021.1), it works well. -- Zhigang
--
viewtopic.php?f=7&t=2407&sid=aaac8396f2 ... 0e97aa9b26