Hi,

(by the way, a "hai" is in german a shark  :-) )

this error may have several sources. 

- One is a wrong integer type in the udunits.F90 file. This  
depends on how your udunits library has been generated. Ask your 
system administrator for details.

It happens in 

    subroutine get_cal_time(time,units,yr,mon,day,hr,min,sec)

If iret has a wrong integer type the return value is not zero 
and an error is detected.

- The other possible source is a missing lowercase in 
time_interp_external.F90
Make sure that the call of get_cal_time is like this:

call get_cal_time(tstamp(j),trim(lowercase(units) ...

I have also seen a file time_interp_external.F90 with 
call get_cal_time(tstamp(j),lowercase(trim(units)) ...
This does not work with some compilers and results in errors 
like yours. 

For a quick check I propose that you make ncdump with tau.nc. I 
guess you will have a capital "DAYS" there (or in another file) 
as time units. If you ncdump to an ASCII file, use an editor to 
change uppercase forms of physical units (only of units nothing 
else) to lowercase units and generate a new netcdf-file with 
ncgen, the model should run. The nco-tools could be used to do 
the same. 

However, the better and permanent fix should be to introduce the 
"lowercase" in time_interp_external.F90.  

Greetings and good luck,
Martin Schmidt


-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
FMS-mom4 mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fms-mom4

Reply via email to