UEMS system signal 4. CPU not supported

[meteoadriatic]

Thanks Meteoadriatic for the advice.

But, you're NOT using EMS or UEMS. Instead, you build your own binaries from the standard package and write your own scripts to run the full process. I'm right??

Well, I can build all binaries from the original WRF package, but I have no idea of how to write these shell scripts. Is anybody else doing the same?

If so, could you share your scripts? I mean post them as an example in the knowhow section.

Best,

Luis

Well my scripts are currently a huge WRF system that has zillion of features, including many advanced that I'm not ready to share with public at this point.

Apart from that I don't have anything pretty basic, but, WRF has nice online tutorial that when you follow will guide you through whole process from start to the end. If you are able to go through it without problems, then you can basically copy what you do into a shell script to make it works automatically.

Online tutorial starts here:
http://www2.mmm.ucar.edu/wrf/OnLineTutorial/index.htm

[lcana]

Ok, thanks anyway.

I'm going to try to build my own binaries and write a simple script as you suggest. My big concern now is which servers to use in order to get the initial data (GFS and some updated SST information)


Luis

[meteoadriatic]

There are three options basically:
1) HTTP: http://nomads.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/
2) NOMADS grib filter: http://nomads.ncep.noaa.gov/cgi-bin/fil ... p25_1hr.pl
3) STRC ptiles

I don't use sst, no idea.

[genito]

Dear members,
Has anyone overcome this problem? I'm also facing it with EMS Release 15.99.8, WRF3.7.1 running on CentOS 6.5, Intel(R) Xeon(R) CPU X7542 @ 2.67GHz, nehalem.
Thanks in advance for any hint.

Genito

[meteoadriatic]

Hi,

There are three ways to resolve it:

1) Ask Robert Rozumalski to compile wrf binaries for your version of CPU (that should be first try).
2) Compile wrf code yourself.
3) Upgrade hardware to newer CPU generation.

I don't think there is 4th option...

[genito]

Hi,
Thanks so much for your prompt reply!
I'll go for the 1st and, if needed 2nd. Noways I can go the third. It's a 4xhexa-core recently acquired