Skip to content

Running numgeo from command line

Using numgeo + Intel oneAPI (only required for simulations with user subroutines)

Make sure to run setvars (e.g. call "C:/Program Files (x86)/Intel/oneAPI/"setvars.bat in Windows or source /xx/intel/oneapi/setvars.sh in Linux) in the same terminal as used to execute the numgeo simulation or start the simulation directly in the oneAPI console (Windows)

The following flowchart gives an overview of typical procedures when using numgeo and how a simulation is started with numgeo.

graph TD
    A[Open terminal] --> B[Change to directory where numgeo executable <br> and input files are located];
    B --> C[Start simulation using <br>./numgeo inp=... out=... npcus=...  <br>Or using Windows: <br>numgeo inp=... out=... npcus=...];
    C --> D{Terminal reports error};
    C --> E[Simulation runs <br> Terminal may report warnings];
    D --> F[Open the .log file <br> Read error message];
    E --> G[Check progress in the <br> .sta file and .msg file];
    F --> H[Rerun];
    G --> I[You can terminate the simulation <br> anytime using CTRL+C];
    G --> J[Simulation is finished];
    G --> K[Simulation aborts];
    J --> L[Check results in ParaView <br> by opening the .pvd file];
    J --> M[Plot results contained in <br> the print output folder];
    K --> N[Open the .log file <br> Read error messages <br> Check results in ParaView];

The following commands are available for running numgeo:

  • inp=... \(\rightarrow\) specify here the name of the input file containing the models and analysis description.
  • out=... \(\rightarrow\) specify the name of the output files. If this keyword is committed, then the name of the input file will be used for the output files as well.
  • ncpus=... \(\rightarrow\) specify the number of cpus (threads) to be used for the simulation. If this keyword is omitted, the number of threads used for the simulation may vary depending on the operating system.
  • oldjob=... \(\rightarrow\) specify the name of the files of the previous simulation from which the new simulation should be started/continued.
  • no-msg \(\rightarrow\) tell numgeo not to report the convergence history in the message (msg) file.
  • no-sta \(\rightarrow\) tell numgeo not to report the convergence history in the statistic (sta) file.

Running numgeo via scripts

The following batch/shell scripts can be used to perform a simulation.

Windows

For Windows, the following script is used (first line not required for statically linked version!): 

call "C:/Program Files (x86)/Intel/oneAPI/"setvars.bat

REM ------------------------ Edit below
set MKL_NUM_THREADS=1
set OMP_NUM_THREADS=1
numgeo.exe inp=input_foundation_soil ncpus=1
Alternatively, a simulation can also be started using directly the oneAPI console and adding numgeo to the system path as is explained here.

Linux + Intel oneAPI

For Linux + Intel oneAPI, the following shell script can be used (change path to the installation location of Intel): 

#!/bin/bash

# ------------------------ 
# change xx and/or path to installation folder
source /xx/xx/intel/oneapi/setvars.sh

chmod 777 numgeo 
# ------------------------ 

# ------------------------ Edit below and start simulation with ./run.sh
export MKL_NUM_THREADS=1
export OMP_NUM_THREADS=1
./numgeo inp=input_foundation_soil ncpus=1