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

Clear unnecessary fields after error indicators are computed #220

Open
ddundo opened this issue Sep 20, 2024 · 5 comments · May be fixed by #224
Open

Clear unnecessary fields after error indicators are computed #220

ddundo opened this issue Sep 20, 2024 · 5 comments · May be fixed by #224
Assignees
Labels
optimisation An opportunity to optimise performance

Comments

@ddundo
Copy link
Member

ddundo commented Sep 20, 2024

With #212, error indicators are now computed at the end of each subinterval. This allows us to get rid of forward_old and adjoint_next fields after each subinterval, since they are no longer needed.

@ddundo ddundo self-assigned this Sep 20, 2024
@ddundo ddundo added the optimisation An opportunity to optimise performance label Sep 20, 2024
@ddundo
Copy link
Member Author

ddundo commented Oct 18, 2024

Then we can also completely get rid of solutions on the enriched_mesh_seq after each subinterval, as well as the enriched mesh and function spaces, etc.

@jwallwork23
Copy link
Member

Nice!

@ddundo
Copy link
Member Author

ddundo commented Oct 20, 2024

@acse-ej321 assigning you since you said you'll do it :)

@ddundo
Copy link
Member Author

ddundo commented Oct 24, 2024

@acse-ej321 @jwallwork23 do we ever need forward_old in Hessian-based adaptations? (After each subinterval's _solve_forward, I mean)

acse-ej321 added a commit that referenced this issue Oct 24, 2024
ace after removing mesh subinterval
acse-ej321 added a commit that referenced this issue Oct 24, 2024
@jwallwork23
Copy link
Member

@acse-ej321 @jwallwork23 do we ever need forward_old in Hessian-based adaptations? (After each subinterval's _solve_forward, I mean)

Probably not in general, no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
optimisation An opportunity to optimise performance
Projects
Status: Reviewed with actions
Development

Successfully merging a pull request may close this issue.

3 participants