[MITgcm-support] urgent question

[Martin Losch]

Riema,

I frequently make this mistake myself: The topography needs to be  
negative, that is, it does not contain "depth" (which would be a  
positive number, right?), but vertical position of the bottom z=-H.
Your temp.new has only two values, the model expect 700x2.

MDSIO etc. You should not have to modify anything in these routines.  
But this is how I look for routines. Change into your "build"  
directory and use grep:

csysm3::build> grep -i 'ine mdswritefield' *.F | grep -v -i call
mdsio_gl.F:      SUBROUTINE MDSWRITEFIELD_3D_GL(
mdsio_gl.F:      SUBROUTINE MDSWRITEFIELD_2D_GL(
mdsio_gl_slice.F:      SUBROUTINE MDSWRITEFIELD_XZ_GL(
mdsio_gl_slice.F:      SUBROUTINE MDSWRITEFIELD_YZ_GL(
mdsio_slice.F:      SUBROUTINE MDSWRITEFIELDXZ(
mdsio_slice.F:      SUBROUTINE MDSWRITEFIELDYZ(
mdsio_slice_loc.F:      SUBROUTINE MDSWRITEFIELDXZ_LOC(
mdsio_slice_loc.F:      SUBROUTINE MDSWRITEFIELDYZ_LOC(
mdsio_writefield.F:      SUBROUTINE MDSWRITEFIELD(            <<<<<<  
this is what you want
mdsio_writefield_loc.F:      SUBROUTINE MDSWRITEFIELD_LOC(
mdsio_writefield_new.F:      SUBROUTINE MDSWRITEFIELD_NEW(

I you want to write (not read or prescribe?) the barotropic tidal  
velocity field along OBW, then you should use MDSWRITEFIELDYZ in  
obcs_calc.F
But I think you want to prescribe this field at every time step. For  
that, you can either use the code that's there (with  
ALLOW_OBCS_PRESCRIBE and useOBCSprescribe, see exp4 for an example  
how to use this stuff), or use MDSREADFIELDYZ.

Martin

On 25 Dec 2006, at 06:49, Riema Rachmayani wrote:

> dear MITgcm,
>
> as Martin told me before that all input files of for mitgcm are  
> binary ieee big endian files, such as bathyfile and hydrogThetaFile  
> in internal wave verification. after i generate to binary ieee big  
> endian files, i still have zero result for the output (i thought  
> because uncorrect while read the input) and sometimes i have error  
> message :
>
> unit 9 named temp.ok lately reading direct unformatted external IO
>
> i was looking where is the statement of input/output files format  
> for example like : OPEN(dUnit,file=fn 
> (1:iLen),status='unknown',form='formatted'), specially for  
> bathyfile and hydrothetafile or others input. is there a routine  
> that show the statement?(formatt)
>
> for example in my new case, i have bathyfile in ascii file  
> (SILL.BTM) and i generate to binary ieee big endian (SILL.OK), and   
> hydrogThetaFile in ascii file (temp.new) ==> binary ieee big endian  
> (temp.ok) in matlab :
>
> load SILL.BTM;
> % write data into big endian format
> fid = fopen(SILL.OK','w','ieee-be'); % open new file in big endian  
> mode
> wrt = fwrite(fid,temp,'float32');       % write data into opened  
> file, using stream and float32 press
> fclose(fid);
>
> load temp.new;
> % write data into big endian format
> fid = fopen('temp.OK','w','ieee-be'); % open new file in big endian  
> mode
> wrt = fwrite(fid,temp,'float32');       % write data into opened  
> file, using stream and float32 press
> fclose(fid);
>
> my bathyfile in ascii file is in row data for Nx=700, Ny=1, and my  
> hidrothetafile in 2 row (2 layers) Nr=2 (you can see in bathy and  
> hydroTheta attachment file). give me some correction if i was wrong  
> to generate the file.
>
> i change nothing in internal wave verification except bathy and  
> hidrothetafile,
> anyone can help me for my case??
>
> thank you MITgcm....
>
> -rima-
>
>
>
> Send instant messages to your online friends http:// 
> uk.messenger.yahoo.com
> <SILL.BTM>
> <temp.new>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support