[Ncep.list.emc.glopara-support] parallel run on vapor

[Kate Howard]

Moorthi,

That is not at all what I suggested. The glopara account set is just a
frozen set of the parallel scripts that always matches production...it is
neither more or less superior to your set.

Kate Howard
NCEP/EMC Global Branch
GFS POC / Monsoon Desk



On Tue, Dec 20, 2011 at 12:10 PM, Shrinivas Moorthi <
shrinivas.moorthi at noaa.gov> wrote:

> Kate,
>  The correct path for parallel scripts in my directory is
> "/mtb/save/wx23sm/GFS/f2010/**trunk/para/scripts"
> Please don't make it appear that somehow associating scripts with
> "glopara" account makes them
> somewhat superior.
> Moorthi
> Kate Howard wrote:
>
>> Sim,
>>
>> I looked through the analysis dayfile and see a number of mismatches due
>> to the use of an old configuration file. Your run was pointing to older
>> versions of the exglobal_analysis script in Moorthi's directories and some
>> other scripts in my personal directories, neither of which are maintained
>> to match production.
>>
>> Daryl Kleist suggested there is a mismatch between the namelists in
>> gsiparm.anl (/stmp/mgd0sa/para/**nodrop2011062206gfsanal/**gsiparm.anl)
>> and the namelist setting in gsimod.F90 (/mtb/save/glopara/trunk/para/**
>> sorc/global_gsi.fd/gsimod.F90)**.
>>
>> If you do a diff on the current exglobal_analysis script and the one set
>> in your configuration file you will see a number of differences, several
>> having to do with the namelist, as well as other outdated files/settings:
>>
>> diff /mtb/save/wx23sm/para_scripts/**cver_1.1/scripts/exglobal_**analysis.sh.sms
>> /mtb/save/glopara/trunk/para/**scripts/exglobal_analysis.sh.**sms
>>
>> Again, I suggest trying your run again with the updated configuration
>> file and let me know if the same issue occurs.
>>
>> Thank you Daryl for helping me pin down the namelist differences.
>>
>> Kate Howard
>> NCEP/EMC Global Branch
>> GFS POC / Monsoon Desk
>>
>>
>>
>> On Tue, Dec 20, 2011 at 11:00 AM, Kate Howard <kate.howard at noaa.gov<mailto:
>> kate.howard at noaa.gov>> wrote:
>>
>>    Sim,
>>
>>    I see you are using an old configuration file. Also, the analysis
>>    step is complaining because it can't find several of the sfcf and
>>    sigf files from the previous cycle.
>>
>>    To make sure it isn't the config file please grab a copy of the
>>    newest one and try your run again:
>>
>>    /mtb/save/glopara/trunk/para/**exp/para_config_gfs
>>    /mtb/save/glopara/trunk/para/**exp/para_config_gfs_prod (matches
>>    production)
>>
>>    The older configuration file is using several older versions of
>>    pmkr and other scripts/code.
>>
>>    Do you only want 3 hrly output from the gdas runs? I suggest
>>    leaving it at one hourly output for the gdas (default in new
>>    config files).
>>
>>    Let me know if the analysis step fails again and I'll take another
>>    look.
>>
>>
>>    Kate Howard
>>    NCEP/EMC Global Branch
>>    GFS POC / Monsoon Desk
>>
>>
>>
>>    On Tue, Dec 20, 2011 at 10:34 AM, sim.aberson
>>    <sim.aberson at noaa.gov <mailto:sim.aberson at noaa.gov>> wrote:
>>
>>        I am trying to perform a parallel run on vapor.  This is the
>>        first time I am using the current version of the model system,
>>        so some things have changed since I have done this last.  I
>>        have successfully gotten through a few steps, but my anal
>>        steps are bombing.  I get
>>
>>          0:     PROGRAM GSI_ANL HAS BEGUN. COMPILED 1999232.55
>>  ORG: NP23
>>          0:     STARTING DATE-TIME  DEC 19,2011  18:48:22.813  353
>>         MON   2455915
>>          0:
>>          0:
>>         164:"gsimod.F90", line 638: 1525-001 The READ statement on
>>        the file (standard input) cannot be completed because the end
>>        of the file was reached.  The program will stop.
>>         165:"gsimod.F90", line 638: 1525-001 The READ statement on
>>        the file (standard input) cannot be completed because the end
>>        of the file was reached.  The program will stop.
>>
>>        But this doesn't exactly give me all the information I need to
>>        debug this.  Any help is appreciated.
>>
>>        My output appears in /gpfs/v/scratch/ptmp/mgd0sa/**rotdatprx.
>>         The particular dayfile with that error is
>>        nodrop2011062206gfsanal.**dayfile in that directory, and the
>>        gdasanal step likewise failed.  My config file is at
>>        /gpfs/v/mtb/save/mgd0sa/para/**prx.config.
>>
>>        Thanks,
>>        Sim
>>
>>        --         Sim Aberson         AOML/Hurricane Research Division
>>               Miami, FL
>>           "Hurricane states erect statues in my honor." -- David Sedaris
>>        ______________________________**_________________
>>        Ncep.list.emc.glopara-support mailing list
>>        Ncep.list.emc.glopara-support@**noaa.gov<Ncep.list.emc.glopara-support at noaa.gov>
>>        <mailto:Ncep.list.emc.glopara-**support at noaa.gov<Ncep.list.emc.glopara-support at noaa.gov>
>> >
>>        https://lstsrv.ncep.noaa.gov/**mailman/listinfo/ncep.list.**
>> emc.glopara-support<https://lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.emc.glopara-support>
>>
>>
>>
>> ------------------------------**------------------------------**
>> ------------
>>
>>
>> ______________________________**_________________
>> Ncep.list.emc.glopara-support mailing list
>> Ncep.list.emc.glopara-support@**noaa.gov<Ncep.list.emc.glopara-support at noaa.gov>
>> https://lstsrv.ncep.noaa.gov/**mailman/listinfo/ncep.list.**
>> emc.glopara-support<https://lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.emc.glopara-support>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lstsrv.ncep.noaa.gov/pipermail/ncep.list.emc.glopara-support/attachments/20111220/f8c799f0/attachment.html