[MITgcm-support] Rebuilding pickup files from data files

[Martin Losch]

Christopher,

if you can afford to be really sloppy, you don't need any pickup  
files: you can pretend to start at niter0=0 and use T,S,U,V,Eta (but  
not W) as input files for a "hot" start:
  &PARMS05
  hydrogThetaFile = 'T.????.data',
  hydrogSaltFile = 'S.?????.data',
  uVelInitFile = 'U.????.data',
  vVelInitFile = 'V.????.data',
  pSurfInitFile = 'Eta.????.data',
  &

Again, not clean but usually works. This also avoids the tedious  
process of creating pickup files for all the packages that you used  
(if you used any, say, seaice, or cd_code).

Martin

On 25 Jan 2007, at 06:06, Christopher L. Wolfe wrote:

> Thanks Andrea.
>
> I suspect the fact that I've lost the tendencies won't make a big  
> difference in my case since I'm interested mainly in time-average  
> behavior of fairly long runs. If the detailed time-dependence is  
> different, it shouldn't matter much.
>
> I should be able to put together something that does the job (if no  
> one else has).
>
> Thanks,
> Christopher
>
> Andrea Molod wrote:
>
>> hi christopher,
>>
>>> A recent computer crashed resulted in the loss of all the pickup  
>>> files from several of my runs, but, as luck would have it, all of  
>>> the separate data files (T, U, V, etc) were saved. Does anyone  
>>> know if it's possible to rebuild the pickup files from the other  
>>> data files so that the runs may be restarted? All the files are  
>>> in the old mdsio format.
>>
>>
>> my take on the answer to your question is 'yes, sort of'. the  
>> number of fields that need to be on a pickup partly depends on  
>> what kind of run you
>> have, but the 'dump' files are indeed 'snap shots' of the model  
>> state that
>> can be written into a pickup file. what is missing, however, are the
>> pickup fields that represent 'tendencies' of the state variables.  
>> like
>> gT and gTNm1 (time tendency of theta, same at one step back).  
>> which you will have to put on the pickup file you write (zeros).  
>> the model will
>> not give you the same result you would have gotten had you continued
>> your run from the pickups. if that's ok then i think your runs are  
>> ok.
>>
>> i don't have a routine offhand to make the pickups from the dump.  
>> maybe
>> someone else has one? to see the write sequence for the pickups see
>> routines write_pickup.F or read_pickup.F in the model/src directory.
>> there will be a separate call sequence for each field.
>>
>> hope this helps.
>>
>> andrea
>> _______________________________________________
>> 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