Hi Paul,


> The code converges and seems to give reasonable results, but I was hoping
>> to get a second (or more!) set of eyes on this to check that it's
>> reasonable.
>>
>
> I'll try and have a quick look later this week.
>


Much appreciated, thanks!

John suggested that I put this code into my fork on github so that it's
easier for others to view and comment on. I'll take care of that shortly.



>
>
>> In particular, the convergence seems to be flaky if I increase
>> forcing_magnitude, which makes me suspect that something is wrong...
>>
>
> How much? This is not unexpected - at some point the motion is too much
> for the nonlinear solver to handle. This is why doing displacement/loading
> increments and even continuation are very common in solid mechanics. (I'm
> sure all of that is familiar to you though.)
>

Yeah, I actually implemented a simple continuation method in the code.
There are parameters in the input text file that allow you to do a sequence
of solves so that solve n gives you a good starting guess for solve n+1.
Still, the code seems a bit more unreliable than I would've expected, so I
may well have done something wrong (I haven't implemented nonlinear
elasticity before, so a "sanity check" would be most appreciated!)

David
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to