Moving a couple processing tools to MTH5 #290
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.
When processing data from an MTH5 there are a few key objects that have been developed in
aurora
, then ported tomtpy-v2
. However, these should not be exclusive to those two packages, they could be used by all users agnostic to processing codes. Therefore, movingRunSummary
andKernelDataset
objects tomth5
is the best solution. This will close Issue simpeg/aurora#376.RunSummary
is an object that collects run information for the stations to be processed from MTH5sKernelDataset
is an object that organizes the run information into processing runs for processing from MTH5s.Create
processing
moduleMove
RunSummary
and all global variables tomth5.processing
Move
KernelDataset
and all global variables tomth5.processing
Add tests
Update tests in
aurora
Update tests in
'mtpy-v2
Add documentation