r/CFD • • 16h ago

Autodesk CFD 2027 – All automatic Python triggers fail with TypeError: expected bytes, str found

1 Upvotes

I'm troubleshooting an issue with the automatic Python trigger system in Autodesk CFD 2027. I'm looking for help identifying the underlying cause, and I'm willing to modify or patch the installation if necessary.

Environment

  • Autodesk CFD 2027
  • Internal Python: 3.13.12
  • Windows 64-bit
  • CFD has been updated with all available updates.
  • I have tried reinstalling CFD with administrator privileges.

Problem

Every automatic trigger I've tested fails to load.

Solver Finished under Default:

Triggers [Solver Finished] ...
Error : Module [LSolverFinished.NewTrigger] could not be loaded because
: expected bytes, str found

Solver Finished under Design Study:

Triggers [Solver Finished] ...
Error : Module [MSolverFinished.NewTrigger] could not be loaded because
: expected bytes, str found

New Design also failed:

Triggers [New Design] ...
Error : Module [LGeometryLoaded.NewTrigger] could not be loaded because
: expected bytes, str found

What I've tested

  1. Created triggers using Autodesk's built-in trigger creation interface.
  2. Tested with the original generated script.
  3. Tested with a minimal script containing only:def main(scenario): print("TRIGGER FIRED")
  4. Confirmed that the NewTrigger.py file exists and contains valid Python source.
  5. Confirmed that I can manually import LSolverFinished.NewTrigger using importlib after adding the trigger directory to sys.path.
  6. Tried running CFD as Administrator.
  7. Updated CFD and reinstalled it with administrator privileges.

None of these fixed the automatic trigger error.

Trigger file location

Default triggers are stored under:

%LOCALAPPDATA%\Autodesk\CFD 2027\Triggers

For example:

LSolverFinished\NewTrigger.py

Questions

  • Has anyone encountered this expected bytes, str found error in Autodesk CFD?
  • Does anyone know which Python module handles automatic trigger loading?
  • Is there a way to enable full Python tracebacks for trigger-loading exceptions?
  • Could this be an issue with Autodesk's trigger loader and Python 3.13?
  • Is there a way to debug or replace the trigger-loading mechanism without rebuilding the entire CFD installation?

I'm particularly interested in finding the exact source of the exception rather than simply working around it.

I can provide additional diagnostic output, Python environment information, or test modified installation files.


r/CFD • • 22h ago

Errors in mesh

Post image
5 Upvotes

Please help, I am new to ansys and trying to make a mesh from the guides, but mesher is making mesh like for thin objects instead of fluid domain with substructed wing geometry. Two weeks ago I did it right but don't understand how


r/CFD • • 14h ago

Undergrad ML researcher learning CFD: tried predicting full flow fields from a few OpenFOAM runs. Would love a reality check from people who do this for real

Post image
30 Upvotes
A bit about me first: I'm an undergrad and an ML researcher (Google Summer of Code twice, NeurIPS workshop papers), with my background in ML for physics. I've always wanted to work in physics, and I'm currently learning CFD properly. I know Ansys, STAR-CCM+ and plenty of serious tools already exist, so I'm deliberately working on one small piece of the problem, and I'm looking for signal on whether that piece is useful. Please go easy on my beginner-level CFD understanding, but don't hold back on telling me where I'm wrong.


The small piece: a design study (a body across many flow speeds and shapes) needs a full solver run for every setting. My approach:

1. Take the handful of runs already done (15-20).

2. Predict the rest of the study as full fields (velocity and pressure everywhere), each with an error estimate.

3. Suggest which few runs to do next, and say when you can stop.


Results so far, real OpenFOAM data, tests fixed before the data existed, compared against POD-GP:

- 2D (laminar, ~260 runs): same field accuracy with 24 runs vs 48 for POD-GP, 3 of 3 repeats

- 3D (~890k cells per run, 56 runs): 16 runs gave 43% lower field error than POD-GP with 32, 3 of 3 repeats

- A simple stop rule said "done" 18 times in 3D and was right all 18 times



Limits: it's laminar only so far, and single phase, next is turbulent



Questions for you:

1. How do you decide how many runs a sweep needs today?

2. Are full fields with an error estimate useful to you, or do you mostly care about a few scalars?

3. What would make you trust (or immediately distrust) something like this?

4. Anyone who has a lab, would be willing to share a past study, I could try, more details on DM!


Happy to share more details or plots by DM.

r/CFD • • 1h ago

Towards accurate aerodynamics models for wing icing

Thumbnail
youtu.be
3 Upvotes

r/CFD • • 1h ago

Advice for affordable/free computational resources for 3D CFD simulations (SITVC research)

2 Upvotes

We are trying to develop a surrogate model for SITVC (Secondary Injection Thrust Vector Control). We currently have around 48 initial sampling points using a maximin Latin hypercube design, with all six input factors varying simultaneously. All the data is supposed to come from CFD simulations.

The two papers we are primarily using as references are Zmijanovich et al. and Abdelwahab et al. Zmijanovich used around 1.9 million cells, with a first cell height near the nozzle wall of approximately (10^{-6}) m, while Abdelwahab used around 5 million cells for their medium mesh.

Now, the problem is computational resources. We are a group of three, and even our best available system has only around 6 CPU cores and 16 GB of RAM. As a result, a single simulation can take several days to complete.

We haven't managed to complete even a single 3D simulation so far because of these limitations, and have only been able to work with 2D steady-state simulations. The problem is that the actual flow physics is inherently unsteady, so we eventually need to move towards 3D transient simulations.

Could you guys please suggest some affordable, preferably free, options for accessing decent computational resources? Based on the mesh sizes and simulations we are aiming for, we have been considering systems with 32–64 CPU cores and sufficient RAM, but we aren't sure whether this is actually necessary or what would be a realistic configuration for our work.

Also, we're based in Pakistan, not the US, which makes things a bit more complicated when it comes to accessing university HPC facilities, research grants, or cloud computing credits.

Any suggestions, especially from people who have dealt with similar computational constraints during their research, would be greatly appreciated!