Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Latest version of the gui scripts, this is a combination of earlier iterations of the tools by github OpenRadioss contributors: hotaosa and PaulAltair

...

Linux gui Scripts tar.gz Download (8KB)

Installation and Launch

Expand
titleWindows Installation and Launch

Windows Installation and Launch

The script folder (win_scripts_mk3) should be extracted to the installation folder of OpenRadioss (same level as exec, hm_cfg_files etc), the scripts work only from this directory level currently

The initial contents of the folder appear as below, for the windows version, python is not a pre-requisite, there is an .exe version of the gui that may be used directly without a python installation, the main gui tool is ‘openradioss_run_script_for_windows_mpi_ps.exe’ and can be launched from windows explorer on double click, the python code is still included for information and the .py script may still be used if python is installed (the 'openradioss_run_script_for_windows_mpi_ps.py’ files is the main python script)

Windows Desktop Shortcut (Optional)

It is possible to create shortcut Links for the exe or python tools with the form e.g.:

Target for exe:

full_path_to\win_scripts_mk3\openradioss_run_script_for_windows_mpi_ps.exe

Target for Python:

C:\Windows\pyw.exe “full_path_to\win_scripts_mk3\openradioss_run_script_for_windows_mpi_ps.py"

Start In Folder

full_path_to\win_scripts_mk3\

You may also ‘change icon’ to the one in the included icon folder

Expand
titleLinux Installation and Launch

Linux Installation and Launch

The script folder (linux_scripts_mk3) should be extracted to the installation folder of OpenRadioss (same level as exec, hm_cfg_files etc), the scripts work only from this directory level currently

bash shell, and python with tk is a pre-requisite in linux

not all linux distros necessarily include python/tk by default, e.g. lubuntu has it, but for ubuntu-mate following is needed

Code Block
sudo apt-get install python3-tk

In linux, the content of the linux_scripts_mk3 folder is as below, the ‘openradioss_run_script_for_linux_mpi_ps.py’ file is the main gui,

in order to launch it, enter the linux_scripts_mk3 folder in a terminal window open it with python3, e.g. :

Code Block
languagebash
python3 openradioss_run_script_for_linux_mpi_ps.py

Linux Desktop Shortcut (Optional)

It is possible to create a clickable desktop/menu icon for linux:

add/create a file: ./local/share/applications/openradioss.desktop (make executable)
content of form e.g.:

Code Block
[Desktop Entry]
Type=Application
Name=OpenRadioss
Exec=bash -c "cd /home/user/OpenRadioss/linux_scripts_mk3 && /usr/bin/python3 /home/user/OpenRadioss/linux_scripts_mk3/openradioss_run_script_for_linux_mpi_ps.py"
Icon=/home/user/OpenRadioss/linux_scripts_mk3/icon/ross.png

This will add a shortcut to desktop, menus: then can be pinned to desktop also:

Script Usage (windows/linux)

The gui usage is the same in both linux and windows, the gui takes input file and a number of OMP/MPI processors (-nt, -np) as arguments, there are also options for running single precision version, and having Anim-vtk and/or TH-csv conversion performed at end of the run.

Submission gui

...

Job Input file can be Radioss format Starter (_0000.rad) Radioss format Engine (_0001.rad, _0002.rad etc.) or Dyna format .k or .key file

...

If -np is 1 then the SMP (OMP) version of OpenRadioss is run, if -np is > 1 then the SPMD (MPI) version of OpenRadioss is run

If ‘sp’ box is checked, the extended single precision version of OpenRadioss will be run (if self compiling, this version is not compiled by default, see compilation guides)

...

Note: In Windows version only: On first attempt to submit an mpi run (-np > 1) you will be prompted to locate a suitable vars.bat file on your machine, once selected, this is remembered (to reset, delete the created ‘path_to_mpi_vars.txt’ file from the install directory, or edit its contents)

...

Run Window

The job runs in a window titled with the run name, with some option buttons at the bottom:

Button Functions

Starter phase

Engine phase

Stop

stops the job at end of starter

stops the job cleanly writing restart (.rst) file(s)

Kill

stops the job at end of starter

kills the job (no restarts written)

Anim

no function

writes an Anim file at the current cycle

h3d

no function

writes/updates the h3d file at the current cycle

Close

becomes available when job is completed, and closes the run window

becomes available when job is completed, and closes the run window

Queue Window

it is possible to submit further jobs from the submission gui after the first and they will be queued for running when the currently running job completes, the queue can be checked and edited, by clicking the ‘Show Queue’ button in the submission gui.

...