User Forum of Software BASEMENT

BASEMENT
Basic Simulation Environment for computation of environmental flow and natural hazard simulation
Laboratory of Hydraulics, Hydrology and Glaciology (VAW)
ETH Zurich
Basement_Logo

You are not logged in.

#1 2026-08-13 14:45:25

maxim.sorockin
User
Registered: 2026-08-12
Posts: 1

BASEMENT v4.2.0 GUI on Linux fails with "no model definition found"

Hello,

I'm running BASEMENT v4.2.0 on Ubuntu 22.04 (GUI)

Setup:
- OS: Linux (Ubuntu), locale en_US.UTF-8 / LC_NUMERIC=ja_JP.UTF-8
- BASEMENT v4.2.0, installed binaries in /usr/bin/BMv4_*
- Test case: TestCases/1_H_CDB_Benchmark/BMv4/10k (circular dam-break benchmark)
- The same test case (same files) runs successfully on Windows with the GUI.

Steps to reproduce on Linux:
1. Open the test case folder in the BASEMENT GUI.
2. GUI correctly displays the contents of model.json.
3. Click "Write".

Result in GUI:
STDOUT : BASEMENT v4.2.0 (v4.2.0)
STDOUT : BASEHPC setup binary
STDERR : -> no model definition found
STDERR : -> ... unfortunately BASEMENT is killed!

However, running the setup binary directly from the command line in the same folder works perfectly when the model file is passed with the -f flag:

/usr/bin/BMv4_BASEHPC_setup -f model.json -o setup_test.h5

-> completes successfully, "BASEMENT successfully processed all necessary jobs!"

But running it WITHOUT -f (i.e. model.json as a positional argument) fails immediately with:

PARSE ERROR: Argument: model.json
             Couldn't find match for argument

Could you please check how the Linux build of the GUI constructs the command line for BASEHPC_setup?
It looks like a Linux-specific packaging/argument-passing bug rather than a model.json compatibility issue.

Happy to provide more logs or test further if useful.

Thanks,
Maxim

Offline

#2 2026-08-18 07:22:46

Matthias Bürgler
Developer
From: Zürich
Registered: 2019-04-04
Posts: 190

Re: BASEMENT v4.2.0 GUI on Linux fails with "no model definition found"

Dear Maxim,

I was not able to reproduce the error in the GUI on Ubuntu 22.04 with BASEMENT v4.2.0. Could you post a screenshot of the GUI with the error message?

What I find strange is that you see the STDOUT and STDERR tags in the GUI, those should not be displayed.

The BASEHPC specific executables (e.g. BMv4_BASEHPC_*) require the -f flag. Only the executables BMv4_setup, BMv4_simulation and BMv4_results require the input filenames as direct command line argumenets without any flags. Those can be used for both BASEHPC and BASEMD simulations.

Best regards,
Matthias

Offline

Board footer

Powered by FluxBB