[RegCNET] Problems with RegCM3

[Долгих]

Dear Sir/Madam. 

The Kazhydromet (Republican State-owned Enterprise "Kazhydromet",Kazakhstan) intends using the RegCM3 (regional climate model) for seasonal and interannual prediction. 

Could you please inform us with contact info of persons who can help with running of RegCM3. 

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". 

Model installed on system: 
Operating System: Red Hat Linux 10 (Fedora Core 4) 
Intel Fortran Compiler 9 

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. 

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 

we have changed "ifc" to "ifort" command, because IFC 9.0 is worked with this command right now to load a IFC driver. 

Thank you in advance, 
Dr. Svetlana Dolgikh 

Scientific and Production Hydrometeorological Center of Kazhydromet 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ictp.it/pipermail/regcnet/attachments/20050824/01d495a6/attachment-0002.html>