Thanks! I'll give it a go laterRicME85 wrote:Try this - http://forum.freecadweb.org/viewtopic.php?t=4783
Convert STL to STEP, apparently STEP is compatible with Autodesk Sim CFD
Test ran normally, finishing within a timely manner.julien.decharentenay wrote:I updated occfd to fix the Amazon AWS issue (no other change). Patch 009 can be downloaded from http://www.khamsinvirtualracecarchallen ... .1-009.zip. The Test option should turn around in the usual ten minutes or so.julien.decharentenay wrote:@RicME85 I made a mistake and the Amazon AWS instance do not start properly - regardless of the option. I will correct the issue and send you an update. I am sincerely sorry.
If the simpleFoam is not allowed to talk to the other process (ie the exception is not accepted), then it will report an error that it is not able to talk to the other process. I added an option to use the Testing setup in parallel - this should allow you to test the parallel processing without having to seat around for 20 to 30 minutes.Alonso Fan wrote:julien.decharentenay wrote:The windows firewall prompt is because simplefoam is trying to communicate to the other simplefoam process(es). It is important to accept the communication to take place. Normally the firewall remembers this and only prompt once. This happens during simulation 1.Alonso Fan wrote:I left my pc on for an 2 hours or so and when I came back, I had a windows firewall prompt asking me if I could allow simplefoam.exe and one of the meshing tools to run. this only happened after simulation 0 and simulation 1 had been completed, and the previous solution had been mapped on to the new mesh. it's weird because occfd had no problem using simplefoam or the meshing tool before in sim0 and sim1.
If you are referring to simplefoam from the previous version (from sourceforge), it probably prompted at some point or the openmpi library was somehow already authorised.
Use this happened in simulation 1. I understand and have accepted the exception in firewall. Is this the cause of the error? Because I'm not sure for how long the firewall prompt was on screen before I saw it. My thinking is that it tried to run simplefoam.exe without firewall authorisation and therefore threw out an error?
Thanks for your help btw
I am sorry for the lost costs... My mistake... Not sure how I can make up for it...RicME85 wrote:Something odd with the results.
Also, the 3d view looks like this:
http://s12.postimg.org/w6jdk4pq4/3dview12.jpg
julien.decharentenay wrote:If the simpleFoam is not allowed to talk to the other process (ie the exception is not accepted), then it will report an error that it is not able to talk to the other process. I added an option to use the Testing setup in parallel - this should allow you to test the parallel processing without having to seat around for 20 to 30 minutes.Alonso Fan wrote:julien.decharentenay wrote:
The windows firewall prompt is because simplefoam is trying to communicate to the other simplefoam process(es). It is important to accept the communication to take place. Normally the firewall remembers this and only prompt once. This happens during simulation 1.
If you are referring to simplefoam from the previous version (from sourceforge), it probably prompted at some point or the openmpi library was somehow already authorised.
Use this happened in simulation 1. I understand and have accepted the exception in firewall. Is this the cause of the error? Because I'm not sure for how long the firewall prompt was on screen before I saw it. My thinking is that it tried to run simplefoam.exe without firewall authorisation and therefore threw out an error?
Thanks for your help btw
Don't worry about it.julien.decharentenay wrote:I am sorry for the lost costs... My mistake... Not sure how I can make up for it...RicME85 wrote:Something odd with the results.
Also, the 3d view looks like this:
http://s12.postimg.org/w6jdk4pq4/3dview12.jpg
The 3D view shows that the meshing has meshed both internal and external - which is probably associated with watertightness issues. This cause the pressure on the bodywork to be not very right.
CAEdevice reported the same problem occurring frequently for him. In his case it looked to be associated with small gaps at the joining between the intake and exhaust surfaces and the remaining of the body.
I have some of the entries that I run that show the same issues. When this happens I use netfabb to clean the mesh, and then manually separate the inlet and exhaust surfaces using MeshMixer (from memory). It usually fixes the issue.
ok, I've tried this but freecad always goes to a 'not responding' state. I have to force close it through task manager. is there another way?RicME85 wrote:Try this - http://forum.freecadweb.org/viewtopic.php?t=4783
Convert STL to STEP, apparently STEP is compatible with Autodesk Sim CFD
I've tried this process with simpler geometry and it works a treat. it seems that the geometry I originally wanted to convert from stl to step, is too complex for freecad to handle in a reasonable amount of timeAlonso Fan wrote:ok, I've tried this but freecad always goes to a 'not responding' state. I have to force close it through task manager. is there another way?RicME85 wrote:Try this - http://forum.freecadweb.org/viewtopic.php?t=4783
Convert STL to STEP, apparently STEP is compatible with Autodesk Sim CFD