Forum

Edit the file "seadas/bin/gpt.sh" in order to configure memory allocation for running SeaDAS in comand line (GPT) mode.  The file you edited "seadas/bin/seadas.vmoptions" is used with running SeaDAS in visual (GUI) mode.

Danny

The bandMath expression  TSS = 1.7532*E^(204.26*Rrs_660)  is not doing what you think it is suppose to do.  You are confusing the caret operator "^", which is actually doing a bitwise exclusive-OR on two integers, with the a formatting style of writing "^" to repre...

Brian,In order to better help you with this and separate out the end of scan issues from nadir issues you might want to try the same file but using a region at nadir (in the  center file), say (21N 19S -71W -68E).  Let us know if you see the same type of discrepancies between your calculat...

Regarding " (a 4 x 4 grid would cover 1km x 1km, which is bigger than the footprint size)"The grid used is that of the source file not the target "reprojected" file.   When you reproject to 250m, the adjacent pixels of the source file are orders of magnitude away from t...

Basically, regarding the source file, bilinear uses a grid size of 2x2 and bicubic uses a grid size of 4x4.(see link or also available within the SeaDAS internal help): https://seadas.gsfc.nasa.gov/help/general/ResamplingMethods.htmlThe reason you are not seeing a difference between these methods is...

Tim,After sweating this one out a bit, the problem is now correctly understood and resolved!It is a java versioning problem.  At the command line type:  java -versionFor SeaDAS 7.4, you need version 1.8 of java.  Having version 1.7 or lower will give the error you saw when running gpt...

Also regarding data issues for Aqua, Terra, and VIIRS you could try:https://modaps.modaps.eosdis.nasa.gov/services/production/outages.htmlThe Land team has more detailed info on maneuvers and geolocation errors.  This page shows that there was a Drag delta-V on 2003078:https://landweb.modaps.eo...

The Aqua file in your example (A2003078171000.L2_LAC_OC.nc) has very unusual navigation.  The spacecraft was likely doing a yaw maneuver during acquisition.See attached image for the abnormal geometry bounds of this file.As a result, the latitudes and longitudes of adjacent pixels do not reliab...

This works for me, ... even the file with all NaNs (it's over land) and doing a Mosaic defining a region outside of the bounds of the file (your case 2).  I tested this on a Mac.  Can you tell us is your operating system?

Danny

The "x" in the name  "A2013237033500.L1A_LAC.x.hdf" is unfortunately fooling the modis_L1B GUI.  We will look into fixing this autonaming issue in the future.If you take a step back and look at your run of modis_GEO from the GUI you will notice that when you loaded your...