Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scope out move to Tempus #11

Closed
jtostie opened this issue Aug 18, 2016 · 7 comments
Closed

Scope out move to Tempus #11

jtostie opened this issue Aug 18, 2016 · 7 comments
Assignees

Comments

@jtostie
Copy link
Contributor

jtostie commented Aug 18, 2016

Tempus is a new time integration package in Trilinos.

@lxmota
Copy link
Contributor

lxmota commented Jan 21, 2017

@ikalash We are currently working on this. I'm reviving this so that we can track it.

@ikalash
Copy link
Collaborator

ikalash commented Jan 21, 2017

Thanks for reviving the issue, @lxmota! To give everyone a status update, I have hooked up Albany to Tempus via the Piro::TempusSolver class, which I added to the Piro package of Trilinos. There are several tests in Albany demonstrating syntax for how to call Tempus through Albany (one can see which ones by doing grep -r Tempus on the examples directory in Albany). Note that Tempus does not yet have schemes for 2nd order PDEs like LCM problems yet. @lxmota and I are working on adding these schemes.

@ikalash
Copy link
Collaborator

ikalash commented Feb 10, 2017

Today, I learned that Tempus has been granted copyright assertion. It will be moving to Trilinos on 2/14/17.

@ibaned
Copy link
Contributor

ibaned commented Feb 14, 2017

It looks like Tempus just landed in the Trilinos develop branch:

https://github.com/trilinos/Trilinos/tree/develop/packages/tempus

@ikalash
Copy link
Collaborator

ikalash commented Mar 28, 2017

To give an update towards this issue: I have added the Newmark Beta scheme (and more general HHT Alpha scheme) to Tempus and verified its convergence and properties. Attached are some results. These were generated outside of Albany and are running as Tempus tests. I am currently working on integrating the new scheme into Albany.
tempus_newmark_beta_results.pdf

lxmota added a commit that referenced this issue Apr 3, 2017
@ikalash
Copy link
Collaborator

ikalash commented Apr 25, 2017

The new Newmark Beta scheme in Tempus has been hooked up to Albany and appears to be behaving as expected on a simple problem involving the rotation of a cube. Please see commits c151484, af056a5, 42f94c8 and db462ad. An important detail to get the correct behavior was to switch from a Linear Elastic material model to a Neohookean (nonlinear) material model, as discussed during this week's Albany concall. This is because the latter material model is not implemented in a way to enable large rigid body motions / rotations. With a Linear Elastic material models, the cubes expand in a non-physical way as they rotate.

ikalash added a commit that referenced this issue Apr 25, 2017
Adding input files to run Newmark Beta scheme through Piro and
Tempus in explicit mode (beta = 0.0, gamma = 0.5).  Studies of this scheme's
performance are still underway, but results are promising.  For
single cube geometry, my "back-of-the-envelope" calculations say
that the stable time-step is dt <= 7.211e-5; scheme is stable for dt = 7e-5,
unstable for dt = 8e-5.  For larger cube geometry, my "back-of-the-envelope" calculations
say that the stable time-step is dt <= 1.89e-5; scheme is stable for dt = 1e-5,
unstable for dt = 2e-5.

Some caveats:

- The essential BCs in Albany are not implemented in a way that will be handled correctly
with an explicit time-integration scheme at the present time (see issue #13).  This problem works explicitly
b/c there are no essential BCs in the problem specification.  Do not try explicit Newmark Beta
schemes w/ essential BCs, as this will not work correctly in general.

- The explicit Newmark Beta scheme in Piro and Tempus has not been optimized to do mass-lumping
and a trivial inversion of the resulting lumped (diagonal) mass matrix.  Since inversions of
the mass matrix are happening under the hood when running explicit, please do not expect
explicit to be faster than implicit at the present time.  The optimizations involving lumping
can be done in a straightforward way, once the scheme w/o lumping is tested more thoroughly.
lxmota added a commit that referenced this issue May 4, 2017
Not hooked up as a test yet until Tempus is verified more thoroughly.
lxmota added a commit that referenced this issue May 5, 2017
…tion.

Not hooked up as a test yet until Tempus is verified more thoroughly.
lxmota added a commit that referenced this issue May 15, 2017
Tempus verification. (pair program with Irina)
lxmota added a commit that referenced this issue May 15, 2017
…tion

for Tempus (pair program with Irina).
@ikalash
Copy link
Collaborator

ikalash commented Nov 16, 2017

Tempus is being used consistently now, so closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants