Conversation
…extsim into issue385_explicit Conflicts: model/finiteelement.cpp
…ing send and recv instead of isend and irecv is less efficient.
… solver, since the difference is just in the sigma term.
… called pseudo_recursive (because that's what it is). Also: In the recursive scheme cohesion scales like ice thickness squared.
…odel writes a set of output files called "flip" and exits.
…sion_factor for the P* of MEB-EP. It appears the appropriate value is something like 150 kPa - at least at 10 km. This needs a lot more testing and polishing.
…nto issue385_explicit
… different branch (issue issue413_thickening).
tdcwilliams
left a comment
There was a problem hiding this comment.
had a first pass, recommended some changes. Will need another look though. What did you mean by testing the "old setup"?
| // We need to update the mesh every time step | ||
| M_surface[cpt] = this->measure(M_elements[cpt],M_mesh,M_UM); | ||
| std::vector<double> const shapecoeff = this->shapeCoeff(M_elements[cpt]); | ||
| // TODO: Put the B0T code in a seperate function |
There was a problem hiding this comment.
might be a good idea. B0T is calculated in FETensors also (in a nicer way).
|
Hi, I guess 'old' setup is no pressure? Also what is the time step for the explicit code for a 10km mesh? |
|
I just mean to check that the implicit solver still works mostly the same in whatever setup you were using before, whatever the time step, pressure values, etc.
…Sent from my iPhone
On 15 Apr 2020, at 12:23, Timothy Williams <notifications@github.com> wrote:
Hi, I guess 'old' setup is no pressure? Also what is the time step for the explicit code for a 10km mesh?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#423 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGABRFEJQMF7KTGW2LXBRV3RMWDJJANCNFSM4MHZYZ2Q>.
|
Co-Authored-By: Timothy Williams <tdcwilliams@gmail.com>
Co-Authored-By: Timothy Williams <tdcwilliams@gmail.com>
|
@einola, I am getting some strange results using the implicit solver with this .cfg file:
|
…nto issue385_explicit
…ue if reset==true (as it should be).
…previous placement may have been problematic)
|
I've addressed all of Tim's comments now ... and made some other modifications. A first look at my test using the semi-implicit solver indicates that it still works ok. @tdcwilliams can you re-run your test? |
tdcwilliams
left a comment
There was a problem hiding this comment.
hi @einola, a few more comments this time.
Looks good code though (with the exception of calling the shape coefficients dx...).
I've launched my test of the implicit MEB so we'll see how that goes.
Co-authored-by: Timothy Williams <tdcwilliams@gmail.com>
…i (it's still the default)
…ate_sigma option instead of the reset option
tdcwilliams
left a comment
There was a problem hiding this comment.
run looks fine now - you can merge once you've applied the suggestions you want
…ebi and meb_explicit instead of mebe)
A huge merge adding the explicit solver and different ways of solving the internal stress that I've been working on.
Can you please check if the "old" setup still works the way we expect? I haven't changed the defaults.