![]() I then started the FLUENT Fault-tolerant workflow, which showed me the steps to follow. I decided to press forward and work with what I had at that point and see if the new Fault-tolerant Meshing workflow will hold up against this CAD. Having spent about 15 minutes fixing many problem areas, I was still far away from a typical watertight geometry. The first step was using trusty old SpaceClaim to fix the obvious issues. ![]() A good example of these issues can be seen below at the fork and headset. ![]() overlap, duplicate surfaces, holes and surface complexity. It had the typical issues of a surface CAD model, i.e. The model is that of a bicycle frame and wheels. When I first looked at the CAD, I was sceptical. One, that I dare say, I used and loved, Gambit 2.3. But when approached by a prospect with a surface CAD model, I was keen to jump on it and see if this old dog could be taught a new trick or two. I’ve seen the marketing and demo material from ANSYS over the last year on the new FLUENT Experience and, as in all demos, it looks very impressive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |