Fgmax indexing #561
Merged
Fgmax indexing #561
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
…ng array has same format as topofiles, with new parameter for backward compatibility
… compatibility Also moved some import statements that seemed to give circular imports in some cases: topotools imports data imports fgmax_tools imports topotools.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add parameter
indexingto FGmaxGrid.read_output, with defaultijfor backward compatibility (but with a bug fixed in computingx,yfromX,Y.Setting
indexing='xy'results in fgmax grid arrays that are indexed the same way as topofiles,X[j,i],Y[j,i] corresponds to point x[i],y[j]
This is useful if you want to save the fgmax results in the same format as topofiles, using topotools.Topography.write().