WIP: geometry-mechanical-dpf workflow

[dipinknair]

run : https://github.com/ansys/pyansys-workflows/actions/runs/18599784905
The job is passing but we are seeing error mentioned in #109

[dipinknair]

@RobPasMue
Update: The Mechanical fails to import the geometry file.

2025-10-17 19:55:20.035381 (Thread 0x00007f3885ac6740) [STATE_ENGINE, info] -- ScopeEnd  : CTrunk::RespondToUserTransaction Private memory usage <702568.000 KB> (delta <0.000 KB>), Peak working set size <703424.000 KB>, Elapsed <0 ms>
2025-10-17 19:55:20.035417 (Thread 0x00007f3885ac6740) [STATE_ENGINE, info] -- ScopeEnd  : CTreeManager::RespondToUserTransaction Private memory usage <702568.000 KB> (delta <0.000 KB>), Peak working set size <703424.000 KB>, Elapsed <0 ms>
2025-10-17 19:55:20.492278 (Thread 0x00007f3885ac6740) [DESIGNSPACE, info] --- ScopeBegin: GeometryImport - Import from engine
terminate called after throwing an instance of 'std::bad_array_new_length'
  what():  std::bad_array_new_length

Will have to try importing the same geometry in 25R2 on Linux

[dipinknair]

Update: The pmdb file generated through 25R1 geometry workflow is not opening in 25R1 Mechanical ( both windows and linux ) but opening in later versions such as 25R2 and developer version.

[dipinknair]

@PProfizi Hi Paul, Could you please look at this error ?
https://github.com/ansys/pyansys-workflows/actions/runs/18919698712/job/54014653335

[PProfizi]

Hi @ansjhajjar I am not familiar with this error when building the DPF docker image, could you please take a look? https://github.com/ansys/pyansys-workflows/actions/runs/18919698712/job/54014653335#step:9:575

[ansjhajjar]

@PProfizi centos 7 is end of life since last year, the server might have been deleted.
It is still possible to change the mirror url, but it need to be done in a previous step
https://serverfault.com/a/1161847

[dipinknair]

@PProfizi @ansjhajjar Can I use ansys/pydpf-actions/[email protected] action here ? instead of ansys/pydpf-actions/[email protected]

[PProfizi]

@PProfizi @ansjhajjar Can I use ansys/pydpf-actions/[email protected] action here ? instead of ansys/pydpf-actions/[email protected]

@dipinknair sure, it only depends on what you want to do. If you do not care about running DPF within a Docker container then you can use the regular installation action.

[dipinknair]

@PProfizi I updated action and its installing dpf server correctly but I am running into this https://github.com/ansys/pyansys-workflows/actions/runs/18987035993/job/54235134668 . Which is similar issue I had faced when I was using Mechanical image for running dpf script. Do I need to provide any specific env variable ?

[PProfizi]

@PProfizi I updated action and its installing dpf server correctly but I am running into this https://github.com/ansys/pyansys-workflows/actions/runs/18987035993/job/54235134668 . Which is similar issue I had faced when I was using Mechanical image for running dpf script. Do I need to provide any specific env variable ?

Hi @dipinknair could you please try to fix the error for 251 first? https://github.com/ansys/pyansys-workflows/actions/runs/18987035993/job/54235134671#step:10:28
It is the same error for 242 and 251.
Let's try and solve those first.
The problem with 241 might be bad error reporting, or something unsupported for 241, but we'll know better once the script works for at least one version.

[dipinknair]

@PProfizi I am trying to fix the issue in 24R1 first. The issue with 24R2 and 25R1 is because of Mechanical which I will look into later once I fix 24R1 workflow. Below are the files from Mechanical workflow which can be used for testing locally if you need it. I will work to fix the 24R2. 25R1 workflow has some issue with geometry incompatibility.
geometry-mechanical-dpf-workflow-mechanical-dpf-outputs-24.1 (4).zip

[PProfizi]

@PProfizi I am trying to fix the issue in 24R1 first. The issue with 24R2 and 25R1 is because of Mechanical which I will look into later once I fix 24R1 workflow. Below are the files from Mechanical workflow which can be used for testing locally if you need it. I will work to fix the 24R2. 25R1 workflow has some issue with geometry incompatibility. geometry-mechanical-dpf-workflow-mechanical-dpf-outputs-24.1 (4).zip

I tried to create a dpf.Model from the rth files in transient and steady state and could not reproduce the error for 241 on Windows, even with pydpf-core 0.14.2.

[dipinknair]

@RobPasMue I checked the 24R2 workflow. The issue is with the file. .pmdb file from geometry 24R1 works with Mechanical 24R2. But not the file from 24R2 geometry. There is something issue with geometry 24R2 file. May be lets update to use only geometry 24R1 for all version ?

[RobPasMue]

Please add a comment similar to

pyansys-workflows/.github/workflows/geometry-mesh-fluent.yml

Lines 50 to 51 in 5d3fdd4

	# [24.1, 24.2, 25.1] -- HACK FOR FLUENT: 24.2 is in reality a 24.1 container, and 25.1 has issues with CAD import currently
	ansys-release: ${{ needs.is-only-docs-required.outputs.only-docs == 'true' && fromJSON('[24.1]') || fromJSON('[24.1]') }}

explaining why we are only running 24.1 container

[dipinknair]

@PProfizi I am trying to fix the issue in 24R1 first. The issue with 24R2 and 25R1 is because of Mechanical which I will look into later once I fix 24R1 workflow. Below are the files from Mechanical workflow which can be used for testing locally if you need it. I will work to fix the 24R2. 25R1 workflow has some issue with geometry incompatibility. geometry-mechanical-dpf-workflow-mechanical-dpf-outputs-24.1 (4).zip

I tried to create a dpf.Model from the rth files in transient and steady state and could not reproduce the error for 241 on Windows, even with pydpf-core 0.14.2.

@PProfizi We have fixed Mechanical workflow in all versions. This issues seems to be happening only in linux.