Learning Forum

[Sam001]

Hi,

   I did submit some batch job and keep getting this error: "Framework Error Caught:" See pic below.

Does anyone have an idea how to resolve this? Using the Release 19.2

Thanks,

Sam 

 

[Karthik Remella]

Hello,

Apologies for the delayed response. It seems like there was an error during the meshing stage of your WB project. The error message which caught my attention was "Unable to start the meshing editor".

Quick questions to help us understand the issue better.

• What type of WB model are you running? Is this a parametric analysis?


• Are you running this in batch mode through a script?


• Did you try to run the model as a standalone / interactively on a local machine? Did the model give you any issues or did it run successfully?


• Are you seeing this error with only this model? Or are you seeing the same issue if you run any model?

Thank you.

Best,

Karthik

[Sam001]

Kirk,

      Have actually moved beyond that problem now.

1.)  Fluid flow Fluent WB Model

2.) Batch mode through a script because of the location of the cluster hardware (psc to uwm)

3.) I did that on our campus cluster and it worked perfectly fine.

4.) As of then, the error was with every model on psc. Discovered needed to add "unset SLURM_GTIDS" to the scripts.

 

Now, Faced with the error " error during safe casting of value, value changed" when reducing my mesh size, with pic shown below. Please, this is different from the warning "min size is very small".

Also, do you have an idea of how to write scripts for Fluent involving "improvement of mesh quality from 0.1% to 10% for intended numbers of iterations without the GUI" (to enable convergence).

 Thanks,

Sam

 

 

 

[Karthik Remella]

Hello Sam, 

Apologies for my delayed response. I've reached out internally to one of our experts with meshing using scripting. Unfortunately, I do not have much experience with this. You should hear from us soon here. 

Thank you for your patience.

Best Regards,

Karthik

[Karthik Remella]

Hello Sam,

You should be able to use TUI commands in Fluent.

Some commands to improve your surface mesh:

/meshing/boundary/improve/collapse-bad-faces

/boundary/improve/improve

To improve your Volume mesh:

/objects/volumetric-regions/tet/set/improve-surface-mesh?

/objects/volumetric-regions/tet/set/improve-mesh/

/mesh/tet/improve/improve-cells

You should be able to pick these TUI commands and write them out as a journal file. You should be able to run the journal file without the GUI and Fluent meshing will perform these operation. Unfortunately, we will not be able to provide you with the journal file as part of the support. The best way to look at these commands is by using the quick search panel in Fluent meshing (screenshot below).

Please note that any meshing process is using a GUI driven tool. The best way to maximize your productivity (time and effort) would be to perform your meshing operation using the GUI.

I hope this helps.

Best,

Karthik

 

 

[Sam001]

karthik,

          Have read and seen all these, the improve command you imply will only use the default setting 0.1%, I would love to increase it to 10%.

The problem I have with the GUI is that "the mesh editor does not start" with pic attached, probably due to the fragile nature of Mesh editor. The error is attached, thats why I opted for the script. Also at PSC, they also advised Script.

The start-up script for Launching Ansys Workbench is also attached.

What can be done to make 19.2 mesh editor to start, putting into consideration the distance between UWM to PSC.

Thanks,

Sam