This will be fixed in the next release! Thanks for the bug report.

Best,
Matthias

Thanks for raising those issues. If you send us the modified code, we will gladly evaluate to include it the improvements in the official version and will have a look at issues 1. and 2.

Best,
Matthias

I'm trying to get a go on the basemesh-plugin in Qgis.
I'm running a "newish" Mac with a M2 chip (arm-architecture). As I got into reading regarding basemesh, I found it is not working on macOS for now.
Therefore I set up a vm, running ubuntu and install Qgis as well as basemesh.

I followed some basic examples in qgis, but when I run the quality mesh I get the following error:
The BASEmesh worker raised an error. See details for traceback and additional information.
CalledProcessError: 126 "~/QGIS/QGIS3/profiles/default/python/plugins/basemesh_v2/libs/basemesh/triangle/bin/triangle_linux_64" - q28.0.Aa "tmp/tmp6l8xpa63/triangle_2023-12-21_14-32-12.poly"

When I hit the details button, it says:

Traceback (most recent call last):
  File "/home/tim/.local/share/QGIS/QGIS3/profiles/default/python/plugins/basemesh_v2/_worker.py", line 83, in run
    value = self.target(self.feedback, *self.args, **self.kwargs)
  File "/home/tim/.local/share/QGIS/QGIS3/profiles/default/python/plugins/basemesh_v2/gui/qualmesh.py", line 351, in worker
    mesh = quality_mesh(*builder.build(), holes, regions, **kwargs)
  File "/home/tim/.local/share/QGIS/QGIS3/profiles/default/python/plugins/basemesh_v2/libs/basemesh/_meshing.py", line 124, in quality_mesh
    output = triangulate(nodes, segments or (), holes, regions,
  File "/home/tim/.local/share/QGIS/QGIS3/profiles/default/python/plugins/basemesh_v2/libs/basemesh/triangle/_triangulate.py", line 292, in triangulate
    run_triangle(input_path, triangle_cmd, redirect_stdout)
  File "/home/tim/.local/share/QGIS/QGIS3/profiles/default/python/plugins/basemesh_v2/libs/basemesh/triangle/_triangulate.py", line 226, in run_triangle
    raise subprocess.CalledProcessError(return_code, cmd)
subprocess.CalledProcessError: Command '"/home/tim/.local/share/QGIS/QGIS3/profiles/default/python/plugins/basemesh_v2/libs/basemesh/triangle/bin/triangle_linux_64" -q28.0Aa "/tmp/tmp6l8xpa63/triangle_2023-12-21_14-32-12.poly"' returned non-zero exit status 126.

So, as far as I'm able to read the informations this seems to have something to do with worker.py script. I had a look at the lines, but can't get a meaning out of it.

Does anyone has any idea what I could possibly do, or what the problem is? Is it because I'm working on an arm architecture? When I read the Error message, the last bit "triangle_linux_64" leaves me the feeling this has to do with the hardware?

Any advice is much appreciated.

Best regards Tim

some time ago I realized that the IDs of the stringdef nodes saved in the sidecar file (obtained by selecting "write to sidecar file (BASEMENT 2.8)") differ from the IDs reported in the last lines of the 2dm file. The difference is one unit:

Sidecar file
node_ids = (15 4174 4014 4008 4080 4046 3943 4112 4095 4078 4123 4120 14)

2dm file
NS 14 4173 4013 4007 4079 4045 3942 4111 4094 4077 4122 4119 -13 upstream

I do not if this can be categorized as a bug or there is a reason behind this difference.

Related to this: as a BASEMENT 2.8 user through the new BASEMENT 4.0.2 GUI, I think that it would be useful to allow for copying-pasting the list of stringdef nodes IDs directly in the "Define Scenario Parameters" section.

Best,
Sebastiano

Thanks for the idea for the workaround.
I know reran the elevation meshing witout an error, so it worked. However I'm still interested in a "proper" solution, as you might have to move meshs from one project to another (and don't want to create a new mesh everytime).

btw, I'm using BaseMesh 2.2.0 and QGIS 3.28.4 LTR

Try the "Multipart to singleparts" algorithm of the "Vector geometry" section in the QGIS processing toolbox. It should break the MultiPolygon geometry up into individual Polygon features, which should work with the v1.4.5 converter.

Best,
Leonhard

BASEmesh v1.4.6 has been released and tested on QGIS versions 3.10 through 3.26.

We are not aware of any remaining compatibility issues, please do report any encountered.

The error you are seeing is caused by Python running out of memory while trying to clean the input data. This is likely to occur with large input break line datasets, though more of a symptom of a bigger issue.

The Triangle mesh generator used by BASEmesh is quite particular about its input data, especially with regards to duplicate nodes or nodes coinciding with segments. To avoid the resulting obscure errors, BASEmesh performs very thorough (and slow) input cleanup prior to meshing. Even if Python did not run out of memory, the operation would still take an exceedingly long time.

We worked around this for building outlines in an internal build of BASEmesh by removing all input validation from the plugin and cleaning our data manually through QGIS processing workflows, including a significant amount of simplification to reduce segment count. While this worked, it is not stable and very time consuming.

We plan to add a switch that will allow users to disable the conformation step in the GUI (basemesh-v2/#66), but this must be accompanied by additional utilities to clean the input data within QGIS to be useful for users.

Best,
Leonhard

Hi, you could try to use this unrealeased version of Basemesh:
https://gitlab.ethz.ch/vaw/public/basem … ses/2.0.10
I'm currently using it and it works fine.
Best regards
Nino

Same here

i tested the "fix" by installing via the linked zip and QGIS version 3.22.7. However is still get an error.

Traceback (most recent call last):
  File "C:\Users/Gauss/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\basemesh\plugin\gui\worker.py", line 90, in run
    value = self.target(self.feedback, *self.args, **self.kwargs)
  File "C:\Users/Gauss/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\basemesh\plugin\gui\interpol.py", line 242, in worker
    interpol_mesh.save(output_path)
  File "C:\Users/Gauss/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\basemesh\core\mesh.py", line 893, in save
    with py2dm.Writer(filename, materials=num_materials) as writer:
TypeError: init() got an unexpected keyword argument 'materials'

I still cant choose the Raster via dropdowns, only in the advanced section. I used basement version 2.0 and QGIS 3.16 in the meantime working fine for me in most cases. Unless i get the other error i described here:https://forum.basement.ethz.ch/viewtopic.php?id=5445

Best Regards
Jan

A hotfix for this issue is available in the BASEmesh code repository as BASEmesh v2.0.10.

Please note that this is a release preview with limited backwards compatibility. It is therefore not available via the QGIS plugin manager and must be installed via the "Install from ZIP" function.

Best regards,
Leonhard

This is a snippet from a recently generated 2dm file:
MESH2D
NUM_MATERIALS_PER_ELEM 0
ND        0  2.604613e+06  1.190787e+06  0.000000e+00
ND        1  2.604693e+06  1.190490e+06  0.000000e+00
ND        2  2.604504e+06  1.190497e+06  0.000000e+00

Best regards,
Martin

This affects also the elevation meshing.

It is, however, a QGIS problem. Anyway, I believe the bug will be fixed asap, see here

EDIT
To the moderators: I'd call this thread "OSError: [Errno 22] Invalid argument"

Crayfish v3.5.1 and later use a newer version of pyqtgraph and are compatible with Python 3.9. However, they appear to only be available for QGIS 3.18 and higher.
If you cannot upgrade to a more recent version of QGIS, you can try creating an issue in the Crayfish source code repository and ask them to support QGIS 3.16.

Best regards
Leonhard