Forum

Thanks, Sean. This is helpful. It sounds as if the choice of 490 was based on the expectation that light at (or near) that wavelength would penetrate deepest into the water. The specific choice of 490 is, in some sense, historical - that's what we picked first and even though there have been refinem...

Hi - Thanks. I've got those and have read them. They generally talk about how to estimate kd490, but not why one would want to. I am interested in finding out why that particular wavelength was selected as the standard.

Not sure I like this new interface. Can someone point me to a reference that discusses the choice of Kd490 as a standard product?

This problem was noted here:  https://landweb.modaps.eosdis.nasa.gov/cgi-bin/NRT/displayCase.cgi?esdt=MYD&caseNum=PM_MYD_20229_NRT&caseLocation=cases_data&They were planning on reconstructing the missing data from direct broadcast, but I don't know that status.  There have ...

Hi.  Thanks!  Yes, the first message does relate to the percent of accepted pixels in the box.  Both the percentage and the box size are parameters the user can adjust.  What I wasn't clear about (and probably didn't express very clearly) where the program reads the flags...

Unusual for you guys - no answer to this query yet.  Maybe it got confused with my earlier post about having trouble running mk_matchup that Sean resolved.  I'd still like an answer to this question about what triggers the cited error message.   Thanks.

Hi Sean.  Really?   I guess I'll give it a try.  I thought I'd have to use a string with the unit abbreviation for each field - not that that would be so hard...:smile:

Hi.  I've got my mk_matchup script running well now but, using the --verbose option, I am getting some exclusion messages.  One of them, "No matchup: failed MIN_VALID_SAT_PIX, required = 50. found = 40. Exclusion level = 4, Matrix row = 11", is pretty clear and relates to the...

I hope this will be the last of my posts on this subject.  I activated the --verbose optional argument for mk_matchup.py and found that the failures were due to time mismatches.  Then I went back to my R script that created the pseudo-SeaBASS files and found that in the process of converti...

Well, I spoke too soon.  All is not well.  Fixing the delimiter spelling corrected the earlier problem, and now mk_matchup runs.  But now I am getting "No valid satellite match-ups found for any lat/lon/time pairs in [SeaBASS filename]" for every single image.  Given th...