Open GoogleCodeExporter opened 9 years ago
Original comment by t.kozi...@gmail.com
on 5 Jul 2011 at 1:06
File attached above is not correct (doesn't pick up the boundary conditions),
and may not have been the analysis which generated the above error.
I suggest you park this issue for the moment, if I can reproduce it I'll add a
comment/upload correct files.
Original comment by steve.br...@atkinsglobal.com
on 5 Jul 2011 at 1:22
Would be good to have the file so to catch the reason for this bug (must be
ill-conditioned contact detection).
On the other hand, from the error message I can see that I can do something
about this sort of situation, rather than just stop the simulation. I could
simply ignore contact points that generate this sort of issue. That's another
way to "solve" this:)
Let's keep this open for now.
Original comment by t.kozi...@gmail.com
on 5 Jul 2011 at 1:30
Original issue reported on code.google.com by
steve.br...@atkinsglobal.com
on 20 Jun 2011 at 3:23Attachments: