Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Q. How do I get an account on the ECMWF computer system?
Q. I can't retrieve files from the ECMWF ftp server. I get an error: ftp:bind: Address already in use.
|
Panel | ||||
---|---|---|---|---|
| ||||
Expand | | |||
|
Expand | ||
---|---|---|
| ||
A. This is because the FCM configuration files assume the use of a 'compiler wrapper' which is typically provided by MPI (e.g. OpenMPI or MPICH) installations. Make sure you have a flavour of MPI installed and you have the 'bin' directory included on your PATH environment variable. For example, on linux use 'apt-get install libopenmpi-dev' to get OpenMPI. HPC machines may require you to use a 'module' command e.g 'module load openmpi': check your local help information. |
Q. I get this error, what does it mean? "[FAIL] cpg1c.intfb.h: missing dependency (type=include)"
Expand | ||
---|---|---|
| ||
A. FCM has found an include statement: "#include cpg1c.intfb.h" in the source code but can't find the source file cpg1c.F90. Make sure the file exists or FCM is configured to look at all the sources. |
Q. How do I change where FCM builds the library archive (libmaster.a) file before the link stage?
Expand |
---|
A. FCM queries the TMPDIR environment variable. If set it uses that location, otherwise it defaults to /tmp. On HPC systems, /tmp may not be the best choice if it is in memory. |
Q. What does the $HERE variable in FCM configuration files mean?
Expand |
---|
A. The $HERE variable is a special variable that FCM interprets as the directory in which the configuration file resides. Unlike most of the other variables in the FCM configuration files, $HERE cannot be overridden by an environment variable of the same name. |
Q. How do I change the compiler used by my MPI compiler wrappers?
Expand |
---|
A. For more information on how to correctly set your environment for compiling OpenIFS, see: HowTos: How to set your user environment. It varies depending on your MPI implementation and your local environment. As an example, for OpenMPI, set the environment variables: For Intel installations there are several ways in which the compiler can be set. Normally, the mpif90 command will invoke the gfortran compiler, the mpiifort will invoke the ifort compiler and the mpifc command can be used with a specified compiler on the command line. However, this behaviour can be changed by setting environment variables which these wrapper scripts will read. For more details consult the Intel compiler documentation. Some HPC centres provide the 'module' command for loading and unloading particular compiler suites. Consult your local documentation for more details. |
Q. I get an error about missing shared object file: error while loading shared libraries: libmkl_intel_lp64.so: cannot open shared object file: No such file or directory.
Expand |
---|
A. This can arise with the Intel compiler. The MKL library is Intel's version of the LAPACK and BLAS libraries which should be supplied with the compiler. The .so file extension means this is a shared library found at runtime. In order to find this library, the environment variable LD_LIBRARY_PATH must be set correctly. You will need to find the location of this library and add the directory to the LD_LIBRARY_PATH. Normally this is done for you by a small script supplied with the Intel compiler script. Please check your support information. |
Q. I get undefined references to 'dgemm_', 'dgemv_', 'sgecon_' etc.
Expand |
---|
A. These routines come from the LAPACK and BLAS libraries. You may have one or other of these libraries missing from your .cfg config (or OIFS_LAPACK_LIB environment variable). Alternately you have specific both libraries but the compiler can't find them; check the pathnames to the libraries specified on the compile link carefully. |
Q. I get undefined references to: 'jas_stream_memopen', 'jpc_decode', 'jas_matrix_create', 'jas_image_destroy', 'jpc_decode'
Expand |
---|
A. These are references to the JASPER library and arise because the grib_api library being linked toreferred to in the OpenIFS build configuration was compiled with the Jasper library linked in, but the LD_LIBRARY_PATH environment variable does not list the directory containing the library so the compiler can't find it. Either amend the LD_LIBRARY_PATH or add the -ljasper library to your compilation options. |
Q. Should I use the same compiler to for OpenIFS, LAPACK, OpenMPI etc?
Expand |
---|
A. It's recommended that the same compiler suite is used to compile OpenIFS, your MPI installation and LAPACK. This may not always be practical but it's strongly recommended as some compilers use a different default size of LOGICAL variables which can cause crashes due to memory alignment problems in subroutine calls. |
Q. Where is the log file from compiling OpenIFS kept?
Expand |
---|
A. The log output from compiling OpenIFS can be found in the 'make' directory, then in the build directories 'opt', 'noopt' etc. The FCM software keeps the log in a hidden directory called '.fcm-make'. So if OIFS_BUILD=opt was set, the logfile for this compilation would be : make/opt/.fcm-make/log. |
Panel | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Q. What does the 'T' mean in 'T511', 'T1279' etc?
Q. How do I know the grid from from the 'T' number?
Q. What is the difference between IFS/OpenIFS model versions?
Q. What format is the model output?
Q. How do I check the model is working correctly on my system after I've installed it?
Q. What timestep should I use?
Q. OpenIFS fails with ABORT! 1 SU_MCICA:ERROR OPENING FILE MCICA
Q. OpenIFS fails with an error message from GRIB_API.
Q. OpenIFS fails (segmentation violation) when compiled with optimized compiler options ('opt' configuration) but works without any optimization ('noopt' configuration).
Q. OpenIFS fails with error: Dr.Hook has detected an invalid key-pointer/handle while leaving the routine 'RPASSF'
Q. I don't get any output from the model?
|
Panel | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||
Also see: GRIB_API Frequently Asked Questions. Q. I get an error message from GRIB_API when I run the model saying 'boot.def' not found?
Q. OpenIFS fails with an error message from GRIB_API.
Q. What are the GRIB_API environment variables and what do they mean?
Q. How can I check that GRIB_API was installed correctly / How do I find out where GRIB_API installed the definitions and sample files?
Q. How do I convert from GRIB to netCDF?
Q. When I use grib_ls on OpenIFS output, I get an error: GRIB_API_ERROR : unable to represent the step in h
|
Panel | |||||
---|---|---|---|---|---|
| |||||
|
HTML |
---|
<script type="text/javascript" src="https://software.ecmwf.int/issues/s/en_UKet2vtj/787/12/1.2.5/_/download/batch/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector/com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector.js?collectorId=5fd84ec6"></script> |
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
GRIB_API Frequently Asked Questions ECMWF Data Frequently Asked Questions. FCM User Guide (provided by UK Met Office). |