Computational Fluid Dynamics (CFD) workbench using OpenFOAM

[oliveroxtoby]

This was the case screan at 08:46 on 09/10/19. As ever, I have no idea what anything means but thsi is the only way of moving forward.

12in_VSA_Diffuser_Only_Rev P1_#1.PNG

Thanks again.

Michael

From this error it looks as if you simply have not run the mesh generator yet. Could this be the case? Note that if you are writing to your temporary directory, the generated mesh will be removed when you restart your computer.

[oliveroxtoby]

Files from the last run after ependency checker.

AdobeARM.log

Still getting the same Qt binding error with the follwoing at the head of the Report view, that looked the same as the one I sent you above as a pdf.

C:\Program Files\FreeCAD 0.18\bin\lib\site-packages\matplotlib\__init__.py:908: MatplotlibDeprecationWarning: The backend.qt4 rcParam was deprecated in version 2.2. In order to force the use of a specific Qt binding, either import that binding first, or set the QT_API environment variable.
mplDeprecation)

Thansk again.

Michael

This is just a deprecation warning relating to the Plot workbench. It is nothing to worry about.

[Crossleyuk]

Thanks Oliver. First of all, this is a question I was intending to raise. Are you suggesting that I dont have to use the temp Default output directory and I can make one for each case to ensure that it is not lost?

I removed the mesh from my model and created a new one with no problem. But still no success and did not get any files to report in my temp directory.

12in_VXA_Diffuser_Only _Rev P1.FCStd

(15.86 KiB) Downloaded 85 times

[Crossleyuk]

Hi Oliver,

Still exploiring. Remeshed again (cfmesh) with a larger mesh size after a reboot so empty temp folder. Same error with no files in temp folder again.

12in VSA Diffuser Only - Rev P1 cfmesh Mesh.PNG (139.03 KiB) Viewed 2009 times

12in_VXA_Diffuser_Only _Rev P1.FCStd

(100.14 KiB) Downloaded 66 times

Michael

[oliveroxtoby]

Thanks Oliver. First of all, this is a question I was intending to raise. Are you suggesting that I dont have to use the temp Default output directory and I can make one for each case to ensure that it is not lost?

Yes. You can click on the CfdAnalysis object and set the Output Path on the Properties panel the path that you want to use. This overrides the default output directory on a case by case basis (which, of course, doesn't have to be set to your temporary directory).

[oliveroxtoby]

Hi Oliver,

Still exploiring. Remeshed again (cfmesh) with a larger mesh size after a reboot so empty temp folder. Same error with no files in temp folder again.

12in VSA Diffuser Only - Rev P1 cfmesh Mesh.PNG12in_VXA_Diffuser_Only _Rev P1.FCStd

Michael

Could you confirm that when you create the mesh, a 'meshCase' directory appears in your output path (which is probably your temporary directory)? If you can't find it, use the "Edit" button in the meshing task panel to go to it. Are you able to view this mesh with paraview (again, from the meshing panel)?

[Crossleyuk]

Yes Oliver, this is the Statud text:

| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 5.x |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
/* Windows 32 and 64 bit porting by blueCAPE: http://www.bluecape.com.pt *\
| Based on Windows porting (2.0.x v4) by Symscape: http://www.symscape.com |
\*---------------------------------------------------------------------------*/
Build : 5.x-963176928289
Exec : C:/PROGRA~1/blueCFD-Core-2017/OpenFOAM-5.x/platforms/mingw_w64GccDPInt32Opt/bin/surfaceTransformPoints.exe -scale (1000 1000 1000) mesh_outside.stl mesh_outside.stl
Date : Sep 12 2019
Time : 23:12:37
Host : "VORTEX-CHAMBER"
PID : 20048
I/O : uncollated
Case : C:/Users/mcros/AppData/Local/Temp/meshCase
nProcs : 1
SigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 10)
allowSystemOperations : Allowing user-supplied system call operations[/color]

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Reading surf from "mesh_outside.stl" ...
Writing surf to "mesh_outside.stl" ...
Scaling points by (1000 1000 1000)
End[/color]

Finished loading mesh.

And I can view the mesh in Paraview.

12in VSA Diffuser Only - Rev P1 Paraview Mesh.PNG (203.94 KiB) Viewed 1980 times

The meshcase is also in my temp folder with the correct date and time.

Thanks for your support, I'm still amazed that you put up with me. I still understand very little other than, now, the mechanics of operation.

Michael

[oliveroxtoby]

Yes Oliver, this is the Statud text:

| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 5.x |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
/* Windows 32 and 64 bit porting by blueCAPE: http://www.bluecape.com.pt *\
| Based on Windows porting (2.0.x v4) by Symscape: http://www.symscape.com |
\*---------------------------------------------------------------------------*/
Build : 5.x-963176928289
Exec : C:/PROGRA~1/blueCFD-Core-2017/OpenFOAM-5.x/platforms/mingw_w64GccDPInt32Opt/bin/surfaceTransformPoints.exe -scale (1000 1000 1000) mesh_outside.stl mesh_outside.stl
Date : Sep 12 2019
Time : 23:12:37
Host : "VORTEX-CHAMBER"
PID : 20048
I/O : uncollated
Case : C:/Users/mcros/AppData/Local/Temp/meshCase
nProcs : 1
SigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 10)
allowSystemOperations : Allowing user-supplied system call operations[/color]

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Reading surf from "mesh_outside.stl" ...
Writing surf to "mesh_outside.stl" ...
Scaling points by (1000 1000 1000)
End[/color]

Finished loading mesh.

And I can view the mesh in Paraview.

12in VSA Diffuser Only - Rev P1 Paraview Mesh.PNG

The meshcase is also in my temp folder with the correct date and time.

Thanks for your support, I'm still amazed that you put up with me. I still understand very little other than, now, the mechanics of operation.

Michael

OK, so far so good. I am confused because previously you said, when running the case, there were no files in your temp directory...

Still exploiring. Remeshed again (cfmesh) with a larger mesh size after a reboot so empty temp folder. Same error with no files in temp folder again.

Could you try running once again, after double-checking that the meshCase does exist in your temp folder?

[Crossleyuk]

Okay Oliver, let me take you through it as I run the existing case after a reboot of my notebook.

1) - Took a look at my temp folder and meshCase was there
2) - Opened the model case
3) - Ran the model and wrote the case
4) - Ran Solver and immediate simulation exited with error
5) - Additional files in temp forder

I've tried to assemble the story below and hope it helps. For some reason, I got more files in temp folder this time.

09-13-19 Images - Rev P1 #3.png (508.28 KiB) Viewed 1954 times

AdobeARM.log

(5.92 KiB) Downloaded 61 times

VORTEX-CHAMBER-20190913-0954.log

(16.75 KiB) Downloaded 73 times

aria-debug-2948.log

(470 Bytes) Downloaded 75 times

StructuredQuery.log

(19.48 KiB) Downloaded 65 times

Fingers firmly crossed.

Michael

[oliveroxtoby]

Okay Oliver, let me take you through it as I run the existing case after a reboot of my notebook.

1) - Took a look at my temp folder and meshCase was there
2) - Opened the model case
3) - Ran the model and wrote the case
4) - Ran Solver and immediate simulation exited with error
5) - Additional files in temp forder

I've tried to assemble the story below and hope it helps. For some reason, I got more files in temp folder this time.

This is a *different* error than the one in your last two reports. Have you noted the following from earlier in the thread?

I was able to run the file that @crossleyuk posted if I simply change the inlet to fixed velocity of (0, 1, 0) as @thschrader did in his.

The solver is less happy with pressure boundaries at both ends, unfortunately. Possibly running transient would provide sufficient damping at the beginning of the simulation to make it work.