It's hard to say.Alonso Fan wrote:Is the problem arising due to the geometry we submitted or is it a flaw in the cfd simulation?
It's hard to say.Alonso Fan wrote:Is the problem arising due to the geometry we submitted or is it a flaw in the cfd simulation?
To some extent I agree, but it's also happened with the Mantium and TalnoRacing entries, both of which look pretty clean. The TalnoRacing entry appears to come from a solid modelling package.CAEdevice wrote:I have never had similar issues this year and I have run more than 25 simulations since January. All the issues I had with occfd are related to parallel computing or to the use of the external tools. I don't want to criticize the design of other teams (consider my point of view it a suggestion), but I see from the pictures that the geometry quality is sometimes very low.
My job often consists in fem/cfd geometry preparation and I think that the ideal starting cad model would be a watertight (=solid) STEP.
Yes I use Solidworks 2014 to draw my car as 1 solid body.cdsavage wrote:The TalnoRacing entry appears to come from a solid modelling package.
As far as i know, snappyHexMesh only accepts .stl or .obj files (someone correct me if i'm wrong). The KVRC team would have to convert all of the entries back to .stl if we submitted STEP files.CAEdevice wrote:I have never had similar issues this year and I have run more than 25 simulations since January. All the issues I had with occfd are related to parallel computing or to the use of the external tools. I don't want to criticize the design of other teams (consider my point of view it a suggestion), but I see from the pictures that the geometry quality is sometimes very low.
My job often consists in fem/cfd geometry preparation and I think that the ideal starting cad model would be a watertight (=solid) STEP.
You are right.HP-Racing wrote:As far as i know, snappyHexMesh only accepts .stl or .obj files (someone correct me if i'm wrong). The KVRC team would have to convert all of the entries back to .stl if we submitted STEP files.CAEdevice wrote:I have never had similar issues this year and I have run more than 25 simulations since January. All the issues I had with occfd are related to parallel computing or to the use of the external tools. I don't want to criticize the design of other teams (consider my point of view it a suggestion), but I see from the pictures that the geometry quality is sometimes very low.
My job often consists in fem/cfd geometry preparation and I think that the ideal starting cad model would be a watertight (=solid) STEP.
But if the conversion to stl fails to produce perfect files then someone would have to repair those files too (ignoring the fact that the the surfaces for cooling, exhaust, etc... still need to be extracted which is another job which needs to be done).CAEdevice wrote:You are right, but what I mean is that no operations should be done on stl files (rule check, preprocessing, geometry repair, ...). The staff (Chris) should receive a STEP and then (very last operation) it should be converted it into stl.HP-Racing wrote:As far as i know, snappyHexMesh only accepts .stl or .obj files (someone correct me if i'm wrong). The KVRC team would have to convert all of the entries back to .stl if we submitted STEP files.CAEdevice wrote:I have never had similar issues this year and I have run more than 25 simulations since January. All the issues I had with occfd are related to parallel computing or to the use of the external tools. I don't want to criticize the design of other teams (consider my point of view it a suggestion), but I see from the pictures that the geometry quality is sometimes very low.
My job often consists in fem/cfd geometry preparation and I think that the ideal starting cad model would be a watertight (=solid) STEP.
The STEP format has been created for data exchange, STL was only the way the workstations used to communicate the final geometry to the first sterolitography machines (today we would say "3d printing").