[MITgcm-support] A question on external forcing timestep

[diego bruciaferri]

Thanks Christoph!
Have a nice day, Diego

Date: Tue, 18 Oct 2011 14:25:39 +0200
From: Christoph.Voelker at awi.de
To: mitgcm-support at mitgcm.org
Subject: Re: [MITgcm-support] A question on external forcing timestep


  


    
  
  
    Hi Diego,

    

    in data.exf you can specify a separate period for every forcing
    field. I, for example use 

    

     &EXF_NML_02

     uwindstartdate1   = 00010101,

     uwindstartdate2   = 120000,

     uwindperiod       = 86400.0,

    #

     vwindstartdate1   = 00010101,

     vwindstartdate2   = 120000,

     vwindperiod       = 86400.0,

    #

     ... more lines left away

     & 

    

    to prescribe daily (period = 86400 seconds) forcing, assuming that
    my first record in the wind files starts on the first of january in
    year 0001, at 12:00 h. You should probably do something like 

    

     uwindstartdate2 = 013000,

     uwindperiod = 10800.0,

    

    Cheers, Christoph

    

    On 10/18/11 2:07 PM, diego bruciaferri wrote:
    
      
      
        Hi Mitgcmers,

        

        I use external forcing of momentum and heat fluxes every 3 hours
        (zonalWindFile, meridWindFile and surfQfile in PARM05 namelist).

        What is the parameter (if any) I have to set to make the model
        read each time step every 3 hours?

        

        Thank you in advance.

        Best regards,

        

        Diego 

      
      

      
      

      _______________________________________________
MITgcm-support mailing list
MITgcm-support at mitgcm.org
http://mitgcm.org/mailman/listinfo/mitgcm-support

    
    

    

    -- 
Christoph Voelker, Research Scientist,
Alfred Wegener Institute for Polar and Marine Research
Bremerhaven, Germany
  


_______________________________________________
MITgcm-support mailing list
MITgcm-support at mitgcm.org
http://mitgcm.org/mailman/listinfo/mitgcm-support 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20111018/17972ae2/attachment.htm>