FEAT: save static results in NetCDF format #98
Merged
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.
Before this PR, the static results are written into stdout, and ASCII format is inconvenient for code maintainance.
NetCDF format perfectly matched the static results, since I use
-X
and-Y
to define the 2D grid instead the 1D distance array in dynamic case.ncdump -h
looks like,However, common pre-built binary NetCDF only have dynamic library, while static library is needed to build PyGRT. After much consideration, I still decide to build the static
libnetcdf.a
from source in Github Workflow. During the whole process, there are many dependency issues, directly solving with lots of jobs makes the workflow.yaml
file looks dirty. Therefore I saved the final built packages and upload them to another repo (my blog....), and the corresponding jobs become a simple downloading job. Same operations applied to FFTW.Now the static results are classical NetCDF format, and can be easily plot via GMT.