[Thread Prev][Thread Next][Index]

Re: [ferret_users] Got "no valid data" with eofsvd



Hi Ansley,

Could you please update the function so that it can first identify the all missing time steps, take those out, and then do the eofsvd, and after, add back the missing t steps to the tfunc t series? If so, it gains back the ability what the old function has.

Many thanks,
Tony


On Wed, Sep 25, 2013 at 3:12 PM, Ansley Manke <ansley.b.manke@xxxxxxxx> wrote:
Hi Jian,
Thank you for writing back. I had not had a chance to look at your question. The earlier version of the EOF functions (eof_space, etc) called code which allowed missing data.  The eofsvd functions work only if there is NOT missing data within the time series - that is to say, if there is data at some time at a given spatial location, then there must be data at ALL times at that location.

It sounds as if there is a bug which so that the function is not reporting back to you that missing data was found. We'll take a look at why.

Ansley


On 9/25/2013 11:30 AM, Jian Ma wrote:
Hi All,

I figured out the reason. It is because I have t step filled with missing values. While this is not any problem with the old version ferret with eof_*, it is with newer version ferret with eofsvd_*. I guess this should be reported as a bug. Currently the only solution for me may be to move the time steps and remove the missing value t steps from the data.

Tony


On Mon, Sep 23, 2013 at 5:52 PM, Jian Ma <jianma@xxxxxxxxxx> wrote:
Hi All,

I met a strange problem with eofsvd for the attached data file. It turns out to be "No valid data". Here is my commands:

yes? set d sstappcf_ma.nc 
yes? fill/l=1 sstappcf_ma
yes? let exyt=eofsvd_space(sstappcf_ma)
yes? fill/l=1 exyt

However I got good results with a data file with time coordinate dd-mm-yyyy. This file has only 1:22 in t coordinate without actual dd-mm-yyyy. Is this the reason for the problem?

Many thanks for any hint,
Tony





[Thread Prev][Thread Next][Index]
Contact Us
Dept of Commerce / NOAA / OAR / PMEL / Ferret

Privacy Policy | Disclaimer | Accessibility Statement