if anyone here has used STARCAT5/STARCCM+ in CATIA, what does this error mean? https://cdn.discordapp.com/attachments/400697259819270145/1438319032930668575/Screenshot_2025-11-12_at_7.06.00_PM.png?ex=6916727c&is=691520fc&hm=b44a81fb97418fd4f3b25718e402b0a8fe0f3563511eb39b29c03aa71989b759&

it comes up very randomly

made a cylinder with one end as a velocity inlet at 1m/s and the opposite end as a pressure outlet, same error

...wait Catia has a CFD application?

Starccm is if i remember from Siemens isnt it

Where is this folder located?

Just a short question: Do you really want to build a propeller to generate thrust or do you want to cool something as in computer fans?

If you really want to build this, this really is a multi-stage axial compressor. Then you definately need stator blades to reduce the vorticity entered by the rotor blades. Also the change of diameter is used to keep the axial velocity relatively constant. This is at the end kind compresor design. A propeller is kind of a "single stage" axial compressor but you don't need to remove the vorticity since it only has one stage. If you want to improve the efficiency you still should do this. An example are counter rotating propellers/fans e.g. the CFM Rise engine uses this. I think this not an easy task to start with cfd. I can only tell you that in axial compressor design you would start with mean line design methods to get an initial guess and then start to develop the actual compressor design.

Within wsl network thingy? Is that a good enough answer?

rather vague 😁 Not sure about what is going on, I was wondering if this is because you store your folder in a weird place

\\wsl.localhost\Ubuntu\home\bananaboi i store my work in $FOAM_RUN, so should be fine?

should be yes, stuff in your home dir isn't supposed to disappear

Im screaming in despair. Is manually opening paraview the only way to view the mesh? Any scripts?

You can automate paraview to output images using python

From command line without having to open it

what do you mean by manually opening paraview?

Although like, it'll still need to load your data into ram, so it'll be as slow as opening paraview if your mesh is really big

You can also use tools like PyVista to view the mesh using Python

Cool, any examples please.

I mean, for now i click paraview, run a script in it (often requires processing one case by clicking things then write a script for the others)

While i can replace that initial setup with some config in a file

hopet this helps to see the mesh!

Thanks

Guys, do I use icoUncoupledKinematicParcelFoam after I run my pimpleFoam case with all the timesteps or instead of?

anyone got a solution to this

Is mapFields -consistent still robust, if the mesh remains the same but my patch type has changed? e.g. I have an inlet but now it's closed so it's a wall, but it's the same patch on the same mesh.

I would assume that mapField overwrites the boundary entry. But you can check it by using the mapFields and then go into the 0-directory and evaluate the files. In each file the patch entries are still given. If you search for it you will see what the entry is after mapFields

Has anyone dealt with block-coupled matrix systems where simple geometries converge fine, but more complex geometries lead to oscillatory residuals? I have a system of 8 strongly and weakly coupled equations with 8 unknowns. Mesh issues have largely been resolved. With weaker coupling, the solver converges, but stronger coupling causes oscillations. Currently using deflated PCG for weakly coupled and BiCGStab for strongly coupled block systems. I’m considering switching to PCG with a reference value for a full-Neumann equation to ensure uniqueness. Looking for insights on handling oscillations in block-coupled systems, similar to implicit pressure–velocity or conjugate heat transfer problems. Anyone interested in discussion on this with some know how, I can further explain the equations etc, I do not like to dump them here as it might be overwhelming for some.