You have the option to compile the OOFEM with OpenMP in order to enable multithreading option (-t #number_of_threads). In CLion preferences, add a new CMake profile with the corresponding CMake option to enable OpenMP library for multi-threading. For OOFEM you need to add the following CMake option: -DUSE_OPENMP=ON (the default is OFF) If the OpenMPContinue reading “Installing HomeBrew/OpenMP on MacOS”
Tag Archives: CLion
Running Python scripts of OOFEM inside CLion
OOFEM has some parts written in python (*.py) such as unv2oofem used for preprocessing and extractor used for postprocessing. To run these scripts first make sure you have setup the python interpreter (see here) Next simply open the python script such as /tools/unv2oofem/unv2oofem.py by openning the script and right click on the file tab andContinue reading “Running Python scripts of OOFEM inside CLion”
Correcting timeout values in CLion
If you get timeout error during debugging; this can be due to your host machine hardware limitation. You may workaround this problem by increasing the timeout values for CLion: Go to the Help | Find Action > run “Registry” command Find “cidr.debugger.timeout” “cidr.debugger.timeout.evaluate” “cidr.debugger.timeout.load” Increase values (e.g. 120,000) This may cause you machine to freezeContinue reading “Correcting timeout values in CLion”
Running oofem “*.in” files from CLion
I always keep the input (*.in) files inside “run_dir” directory inside project directory (they will not be a part of the repository). If you want to do this, you have to change running (working) directory inside run configuration. Open drop-down menu next to the green hammer icon below menu bar. Inside program arguments you canContinue reading “Running oofem “*.in” files from CLion”
CLion debug: Skip C++ standard files in GDB debugger
You need to tell GDB debugger to skip standard file by making two .gdbinit files. One is inside the project folder and is a part of oorbs repository. The other one is inside you home directory and will address the other .gdbinit file. More info:https://stackoverflow.com/questions/5676241/tell-gdb-to-skip-standard-files/42985979#42985979https://www.jetbrains.com/help/clion/configuring-debugger-options.html#gdbinit-lldbinit Add .gdbinit file in your home directory (if it didn’tContinue reading “CLion debug: Skip C++ standard files in GDB debugger”
Building OOFEM clone in CLion and configuring Python interpreter
A) Building the project CLion automatically detects CMakeLists.txt and loads the source files, the remaining process is easy: (This is for Linux, For MacOS skip this) First, install Doxygen and Python:sudo apt-get install doxygenFor the next part also install pythonsudo apt install python3-pip Below the menu from the drop-down select “oofem|Debug”. If you don’t seeContinue reading “Building OOFEM clone in CLion and configuring Python interpreter”
Cloning the Repository using CLion
Before continuing, you may want to make sure that you have the proper compilers installed so that in case you are asked to setup toolchains you can select the desired compiler. Go to the Github website and star the targeted repository:— For original OOFEM: https://github.com/oofem/oofem— For RBSM (OORBS): https://github.com/oorbs/oofem Open CLion Start a new projectContinue reading “Cloning the Repository using CLion”
Setting up the development environment: Installing CLion under Ubuntu
For our project, we chose to use CLion as a development IDE under Ubuntu. CLion provides a much more suitable environment compared to other alternatives such as Eclipse and it can be installed both on Windows or Ubuntu machines. Since compiling OOFEM under windows is not continuously supported you have to set up an UbuntuContinue reading “Setting up the development environment: Installing CLion under Ubuntu”
OORBS Notes 