Forum

Hi again SeaDAS'ers :)Is there a way (or ways) to adjust the cloud flag determination in l2gen to be "more aggressive" in flagging cloudy pixels? I'm finding that we're getting contaminated data (for the purpose of our algorithm) at / near the edge of cloudy areas.In case it ma...

Sean,

Thank you for the explanation. It sounds like that granule has a bit of an "identity crisis"...

I ended up changing my scripts to ignore abnormally small L1A files.

-Andrew L.

Thank you Sean, that would make sense...

For some reason that night time granule turned up in a subscription that was supposed to be day only (id #2130) you might want to double check the selection logic.

Good morning.For some reason the commandmodis_L1B.py A2019120081000.L1A_LAC A2019120081000.GEOis not currently generating the expected A2019120081000.L1B_HKM file. It's a silent failure with no errors / warnings / etc. Any ideas as to what is going wrong?PS I also tried modis_L1B.py --hkm=A20191...

That helped a lot, thank you!

I think (but can't be sure) that the other errors are the file system getting full.

Good Morning :).I'm trying to process L1A data to L2 data in an environment where a brand new virtual machine is started for each run (and unfortunately is destroyed after the run completes, making debugging that much more ...interesting...). I'm seeing two issues that I hope you guys might ...

Thank you, Sean, for the quick response!

I'm guessing MODISA's 841-876 nm band is not one that can can benefit / use ATREM.

Good evening SeaDAS'ers :)

I'm wondering - when using l2gen, what is the difference between gas_opt=8 (noted as "H2O" in the usage message) and gas_opt=16 (noted as "use atrem (H2O)" in the usage message)?

Thank you in advance for your help!

-Andrew L.

Thank you, Tommy, for the prompt response! It looks like we're retrieving the data now.

Good morning!

I have a MODISA subscription (#2130 again) that hasn't found any data since a pass on 3/10/2019 at 20:30.

Is there an issue with MODISA data?