Test for computation with topography. #1040
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Graphite Automations"Add gempy label" took an action on this PR • (05/31/25)1 label was added to this PR based on Miguel de la Varga's automation. |
Leguark
force-pushed
the
compute_at_compuation_time
branch
from
3f38a65 to
993927c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added test to start tracking down why
compute_athas high computation time. This test showcases it by comparing "normal" model computation time to topography computation time. @Deepprakash222, please add your examples here too.Checklist
or 2. verifies that outputs are as expected for given inputs (e.g. unit tests).