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

Support different timescales #1542

Closed
bangerth opened this issue May 9, 2017 · 5 comments
Closed

Support different timescales #1542

bangerth opened this issue May 9, 2017 · 5 comments
Assignees

Comments

@bangerth
Copy link
Contributor

bangerth commented May 9, 2017

There is currently no way to accurately solve dynamics faster than the viscous time step. Cases where this would be useful are (i) fast reactions between compositional fields, (ii) rapid decay of quantities (that are not necessarily coupled) such as elastic stresses in a viscoelastic model, (iii) elasticity forces in a viscoelastic model.

Between @tjhei , @jdannberg , @cedrict , @naliboff , and @bangerth, we discussed how best to address these. A useful approach would be to implement something like a Strang-style operator splitting that allows treating fast dynamics and viscous (Stokes-style) transport separately. The advantage of these approaches would be that one can do the fast dynamics as an ODE for each node point separately, using just an ODE solver that could even use an adaptive time stepping method. (Could we get that from Trilinos, for example?)

That would also be a useful topic for an ASPECT 3 or 4 paper.

@tjhei
Copy link
Member

tjhei commented May 14, 2017

@jdannberg is working on it.

@gassmoeller
Copy link
Member

As far as I know this has been addressed by #1825. We can improve that further by using better ODE solvers (like Sundials), but that would be a separate issue. Can this issue be closed?

@jdannberg
Copy link
Contributor

As far as I am concerned, this has been addressed (and we have #1867 for the technical improvements). But I don't know if @bangerth had something else in mind for the elasticity problems he mentions.

@gassmoeller
Copy link
Member

I think we also thought of using the elastic strains of the last timestep, or using fields for them. Both approaches are now possible, so I will close this for now. Feel free to reopen if something is not addressed yet.

@bangerth
Copy link
Contributor Author

No, this was it. Thanks for closing!

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

No branches or pull requests

4 participants