[MITgcm-support] Model/DIC_forcing time mismatch

Tue May 12 11:51:11 EDT 2015

Ah ok, 

So I guess in essence, seeing as I’m running my model in ‘gregorian’, I should perhaps have changed the “externForcingCycle=365 days? And the external forcing period likewise to something like 30.3333 days. I’ve effectively been drifting by five days in my external forcing fields per year of model run.

Thanks for your response.

Nick

On 12 May 2015, at 15:43, Jean-Michel Campin <jmc at ocean.mit.edu> wrote:

> Hi Nicholas,
> 
> Looking at your data & data.dic,
> I have the impression that you are restarting (nIter0) at time
> t=10*360+50 days; with DIC_forcingCycle set (by default) to
> externForcingCycle=360 days, this implies that the first record
> to be used in the DIC_perturbFile will be around the 50th (interpolated
> from 49 & 50), missing the perturbation (days 1-40) until the
> near end of the 1rst year of this run.
> 
> And regarding this:
>> Is there a way I can run the model from a pickup AND reset the model clock to zero so that I can run it as if it?s the first year?
> You can try specifying, i main parameter file "data" namelist 03:
> pickupSuff='0000087600',
> this should force to do a restart even if nIter0=0
> 
> Cheers,
> Jean-Michel
> 
>> 
> On Tue, May 12, 2015 at 10:48:23AM +0200, Nicholas Rogan wrote:
>> Hi all,
>> 
>> I?m having problems with some new forcing/input files I have included in the DIC package. I am using a 1D setup and have spun up my 500m water column for ten years to get a repeating cycle. I have then implemented my perturbations but it seems that the timing of the input files is mismatched relative to the model clock. I am starting my experiment runs from a pickup file that was created following my spin up. I have a perturbation that should be implemented on Day 1 of the new experiment. This is done with a forcing file 1x366 long, i.e. a value for each day of the year. My perturbation is in the new file from days 1-40. But this is not seen in the model run until the end of year 1, as if the timing has shifted over the ten year spin up. 
>> 
>> Is there a way I can run the model from a pickup AND reset the model clock to zero so that I can run it as if it?s the first year?
>> 
>> Alternatively, can anyone give me guidance on my error during my ten year spin up? My DIC forcing period is set to 86400 (Daily) and the model time mode is set to the gregorian calendar, so I thought it should be ok. 
>> 
>> Thanks. I?ll include my data(.dic) files below. Thanks!
>> 
>> Nick
>> 
>> # ====================
>> # | Model parameters |
>> # ====================
>> #
>> # Continuous equation parameters
>> &PARM01
>> tRef=23*20.,
>> sRef=23*35.,
>> viscA4=0.,
>> viscAh=5.E5,
>> diffKhT=0.E3,
>> diffKhS=0.E3,
>> viscAz=1.E-3,
>> diffKzT=5.E-5,
>> diffKzS=5.E-5,
>> rotationPeriod=86400.,
>> # beta=1.E-11,
>> # f0=1.e-4,
>> tAlpha=2.E-4,
>> sBeta =7.4E-4,
>> gravity=9.81,
>> gBaro=9.81,
>> rhonil=1035.,
>> rigidLid=.FALSE.,
>> implicitFreeSurface=.TRUE.,
>> eosType='JMD95Z',
>> implicitDiffusion=.TRUE.,
>> implicitViscosity=.TRUE.,
>> ivdc_kappa=0.,
>> tempAdvection   =.TRUE.,
>> saltAdvection   =.TRUE.,
>> momAdvection    =.FALSE.,
>> tempAdvScheme       = 2,
>> saltAdvScheme       = 2,
>> tempStepping        = .TRUE.,
>> saltStepping        = .TRUE.,
>> multiDimAdvection   = .TRUE.,
>> allowFreezing=.TRUE.,
>> useCDscheme=.FALSE.,
>> useSingleCpuIO = .TRUE.,
>> &
>> 
>> # Elliptic solver parameters
>> &PARM02
>> cg2dMaxIters=1000,
>> cg2dTargetResidual=1.E-13,
>> &
>> 
>> # Time stepping parameters
>> &PARM03
>> pickupStrictlyMatch = .FALSE.,
>> # startTime = 0.,
>> nIter0 = 87600,
>> # nIter0 = 0,
>> # nTimeSteps = 20, 1yr =720 (43200s = 12hrs * 360 d/yr)
>> nTimeSteps =8040,
>> deltaTmom = 900.,
>> # tauCD =     321428.,
>> deltaTtracer= 3600.,
>> deltaTClock = 3600.,
>> abEps = 0.1,
>> cAdjFreq = 0,
>> abEps = 0.1,
>> tracForcingOutAB=1,
>> # These are 1 year averages, followed by monthly 2592000
>> #    There are also 5 or 1 day : 432000 / 86400
>> pChkptFreq = 432000.,
>> #  chkptFreq = 432000.,
>> dumpFreq = 21600.,
>> #  taveFreq = 43200.,
>> #  pChkptFreq = 2592000.,
>> #  chkptFreq = 2592000.,
>> #  dumpFreq = 2592000.
>> #  taveFreq = 2592000.,
>> #  pChkptFreq = 86400.,
>> #  chkptFreq = 86400.,
>> #  dumpFreq = 86400.,
>> #  taveFreq = 86400.,
>> monitorFreq = 1.,
>> tauThetaClimRelax = 5184000.0,
>> tauSaltClimRelax = 7776000.0,
>> periodicExternalForcing=.TRUE.,
>> externForcingPeriod = 2592000.,
>> externForcingCycle = 31104000.,
>> &
>> 
>> # Gridding parameters
>> &PARM04
>> usingCartesianGrid=.TRUE.,
>> dXspacing=5000.,
>> dYspacing=5000.,
>> # usingSphericalPolarGrid=.TRUE.,
>> # delX=1*2.E0,
>> # delY=1*2.E0,
>> delZ   = 10.00, 10.00, 10.00, 10.00, 10.00, 10.00, 10.00, 10.01,
>> 10.03, 10.11, 10.32, 10.80, 11.76, 13.42, 16.04 , 19.82, 24.85,
>> 31.10, 38.42, 46.50, 55.00, 63.50, 71.58,
>> # ygOrigin=65.,
>> # xgOrigin=280.,
>> # rSphere = 6371.D3,
>> &
>> 
>> # Input datasets
>> &PARM05
>> bathyFile = 'new_bathy_1x1_500m_testpool',
>> hydrogThetaFile = 'lev_clim_temp.bin',
>> hydrogSaltFile = 'lev_clim_salt.bin',
>> zonalWindFile ='tren_taux.bin',
>> meridWindFile = 'tren_tauy.bin',
>> thetaClimFile = 'lev_monthly_temp.bin',
>> saltClimFile = 'lev_monthly_salt.bin',
>> surfQFile = 'shi_qnet.bin',
>> EmPmRFile = 'shi_empmr_year.bin',
>> the_run_name = 'vII_y',
>> &
>> 
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
>> 
>> &DIC_FORCING
>> DIC_iceFile='day_fice.bin',
>> DIC_windFile='day_tren_speed.bin',
>> DIC_silicaFile='',
>> DIC_ironFile='day_mah_somtimind_molfem2s.bin',
>> DIC_sedFile='sedsup_fivfivzer.bin',
>> DIC_hydFile='hydro_sup_molHem2s.bin',
>> #  DIC_sedFile='sedsup_sevninzer.bin',
>> DIC_perturbFile='mon1perturb.bin',
>> DIC_int1=3,
>> DIC_forcingPeriod = 86400,
>> &
>> 
>> 
>> 
>> _______________________________________________
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-support
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support