Repository navigation
Fix examples after the merge; Viking example becomes frequency-selection FWI - #9
Merged
Merged
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
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.
Every example was run as documented after the merge into one package. The renames themselves broke nothing; these commits fix what did not run or did not match its docs.
$VARis expanded in every YAML string and an unset variable is an error (task YAMLs and--configfiles); theinittemplates run as written; LSRTM template lr; RTM checks grid vs model shape and fails when every batch fails.DepthWeightingnow defaults todepth_axis=0(depth is axis 0 in sweep models).Tested: full
tests/on a V100 (1851 passed, 2 skipped) and on CPU;mkdocs buildgives no new warnings; the Viking walkthrough end to end on a V100 (52 min inversion, misfit 0.484 -> 0.188).🤖 Generated with Claude Code