[RegCNET] Problems with poswt processing

[Moetasim]

Hi,
I am not exactly sure that which error you are refering me to.. 
If its this error :
ncvarid: ncid 5: Variable not found
ncdimid: ncid 5: Invalid dimension id or name
ncvarid: ncid 5: Variable not found
ncvarid: ncid 5: Variable not found
ncvarid: ncid 5: Variable not found
then just ignore it. Postproced data wont have any problem. Jason recently 
replied for such an email over RegCNET.. Postproc uses old netcdf fucntions 
and needs replacement of these functions with new ones...
And if you are refering to this error
--
*ERROR* in putdef in grbtst
---
then in case you have reached to your end date of postprocessing then ignore 
it as well. I guess that output file will be alright. But, if you are still in 
middle of postprocessing then I just advise you to re-run postproc or run it 
by slightly changing initial dates..it should disappear.. (BTW, there is no 
logic behind this).

If you are still unable to get a successful postprocessing of data then I 
would suggest you to send the complete output from the beginning 
of ./postproc.x

Moet




Quoting ДолгиÑ
 <dolgikh at meteo.kz>:

> Dear Moet, 
> thank you for previous answers, but now we have a little problem with  post
> processing. 
> We calculated the data through XRegCM and completed the process
> successfully.
> But after that we tried to average the data through the post processing
> script and recieved following errors (attached error.txt  have a look
> please).
> 
> Looking forward to hearing from you.
> Thanks in advance
> Svetlana
> 
> 
> 
>   ----- Original Message ----- 
>   From: moetasim 
>   To: ?????? 
>   Sent: Thursday, August 25, 2005 9:09 PM
>   Subject: [RegCNET]Re: Problems with RegCM3
> 
> 
>   Hi Svetlana, 
> 
>   Well its not problem from RegCM3 but due to some issue of IFC9 at some
> linux plateforms. Let me refer you to the weblink: 
> 
>  
> http://softwareforums.intel.com/ids/board/message?
board.id=11&message.id=2693&view=by_date_ascending&page=1
> 
> 
>   My suggestion is that: its better to use a previous version of IFC (IFC7 or
> IFC8) compiler instead of going for any solution written at this weblink
> until INTEL people fix it by themselves. 
> 
>   MOet 
> 
> 
> 
> 
>   > Dear Moet, 
>   > thank you for quick reply. It was very useful for us. 
>   > $1  
>   > We have run scripts in csh shell, setting ibyte=1, ntypec=60 in
> domain.param and using Makefile_IFC8 for compilation, but we still find
> error:  
>   > > IPO link: can not find "(" 
>   > > ifort: error: problem during multi-file optimization compilation (code
> 1) 
>   > > make: *** [terrain] Error 1 
>   > > ./terrain.x: line 16: ./terrain: No such file or directory 
>   > 
>   > We hope for your further help, 
>   >   
>   > Svetlana 
> 
>     > ----- Original Message ----- 
>     > From: moetasim 
>     > To: äÏÌÇÉÈ ; regcnet at lists.ictp.it 
>     > Sent: Wednesday, August 24, 2005 8:34 PM 
>     > Subject: Re: [RegCNET] Problems with RegCM3 
>     > 
>     > Hi, 
>     > > 
>     > > Could you please inform us with contact info of persons who can help
> with running of RegCM3. 
>     > ----- 
>     > 
>     > I CAN HELP! 
>     > ----- 
>     > > 
>     > > We have installed RegCM3 (downloaded from your web-site:
> http://www.ictp.trieste.it/~pubregcm/RegCM3/) and have some problems with
> starting the MODEL, particularly with Pre-Processing phase (Terrain.x for
> example). When we running the script terrain.x we have some errors: 
>     > > the system couldn't find some commands like "setenv", "ifc". 
>     > 
>     > ----- 
>     > Well, RegCM3 scripts are written for csh shell so whenever you try to
> run these in bash or anyother shell, such errors are encountered. Its
> advisable that you change to csh before running these scripts. This can be
> done by typing 'csh' in terminal. 
>     > ------ 
>     > 
>     > > 
>     > > Model installed on system: 
>     > > Operating System: Red Hat Linux 10 (Fedora Core 4) 
>     > > Intel Fortran Compiler 9 
>     > > 
>     > ----- 
>     > I guess that ibyte setting for IFC-8 and IFC-9 should be same so set
> ibyte=1  in domain.param if you have not done it already. 
>     > ------ 
>     > 
>     > > Questions: 
>     > > 1) Could you provide us some info about system configuration
> (necessary software, LINUX ver ???, Intel Fortran Compiler ver ??? or
> something more) 
>     > > 2) and what DATA was needed to be downloaded from the web site to
> successful work of the model. We are downloaded only 8 file for NNRP1
> (T,H,RH, etc) for 1997 and for SURFACE - GTOPO30_60MIN, GLCC60MIN_BATS, and
> OIIST - OISST_198112_200302, OISST_198112_200302. 
>     > ---------- 
>     > 
>     > If you have IFC/PGI compiler then normally you need not to have
> anyother special software to run RegCM3. When you have downloaded 60 min
> dataset then I hope you have made adjustments accordingly in domain.param.
> Set ntypec=60 if you have not already done so. 
>     > ------------ 
>     > > 
>     > > listing with errors in Terminal: 
>     > > 
>     > > ./terrain.x 
>     > > ./terrain.x: line 1: setenv: command not found 
>     > > rm -f *.o terrain 
>     > > ifort -tpp7 -g -cm -w -w90 -w95 -L../../Commons/env/liblinuxold
> -lnetcdf -Vaxlib -c -o terrain.o terrain.f 
>     > > ifort -tpp7 -g -cm -w -w90 -w95 -o terrain terrain.o
> -L../../Commons/env/liblinuxold -lnetcdf -Vaxlib 
>     > > IPO link: can not find "(" 
>     > > ifort: error: problem during multi-file optimization compilation
> (code 1) 
>     > > make: *** [terrain] Error 1 
>     > > ./terrain.x: line 16: ./terrain: No such file or directory 
>     > 
>     > ---- 
>     > Now come to this problem: 
>     > You have downloaded IFC-9... Remember that Makefile_IFC7 can't work
> with this compiler version. You must use Makefile_IFC8. 
>     > 
>     > ---- 
>     > 
>     > > 
>     > > we have changed "ifc" to "ifort" command, because IFC 9.0 is worked
> with this command right now to load a IFC driver. 
>     > 
>     > --------- 
>     > If even after running scripts in csh shell, setting ibyte=1, ntypec=60
> in domain.param and using Makefile_IFC8 for compilation, you still find error
> then don't hesitate to contact again. 
>     > ------ 
>     > MOet 
>     > 
>     >