Forum

If you are talking about missing data on the outside 1/2 ish of each scan, that is a "feature" of VIIRS.  The overlapping data of the bowtie region of the scan is not transmitted from VIIRS to the ground.  If you map the data you will get complete spacial coverage.

don

your branch command is missing the 'v' It should be:
--git-branch=v7.3

By the way there is a new version of Seadas you will probably want to upgrade to 7.4

don

The correct fix for VIIRS L1A is to modify  $OCSSWROOT/run/data/viirsn/instrument_defaults.par and add the "c" like George suggested.   The new line will be: rsb_dynamic_lut_file=$OCVARROOT/viirsn/cal/OPER/VIIRS_NPP_CAL_RSB_DYNAMIC_LUT_v2.0.0.2c_obpg.ncThe new file has sligh...

That is kind of strange.  I looked through your script for environment variables that might screw things up, but it looks fine to me.

don

Find out which file with which band fails. Make sure that executing l2bin (without the script) fails.  Give me the input file and your exact command line arguments that fail and I will see what is going on.

Does l2bin fail the same way if you uncomment these lines in your script?#export OCSSWROOT=/Applications/seadas-7.4/ocssw#source ${OCSSWROOT}/OCSSW_bash.env#echo ${OCSSWROOT}This is how the GUI runs the processing programs.  I am assuming that SeaDAS 7.4 is installed in "/Applications/sead...

For processing MODIS with l2gen, ifile needs the 1KM file and you can set resolution to 500 or 250 to process at HKM or QKM.  You will also need the geolocation file.  This will process your example file at HKM:l2gen ifile=MOD021KM.A2016015.1155.006.2016015194614.hdf geofile=MOD03.A2016015...

There is no plan to make OCSSW compile natively on Windows.

We are working on having SeaDAS running on a windows box run the processing code in a linux virtual machine on that windows box.  Probably not what I would choose for a lab.

don

The bin file is probably too big.  You can put it on Dropbox and give me a link.

Just looked at the code for l3mapgen (assuming that is the program you use to make mapped files) and you are correct. The "Data Bins" global attribute is the number of pixels in the mapped file that have valid data.  I was worried the the metadata was just copied from the bin file, bu...