ENH/SEAEXP: allow dropna for very large raw payload files #117
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.
We had a bunch of sea explorer files like:
where a) many of the files had no data, and b) the AROD data was sampled way more times than it actually was outputting data.
The change here allows us to use pandas dropna (https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.dropna.html) to clean up the data set before moving to xarray, in a relatively flexible way:
So if both GPCTD and FLBBCD are NaN, the line will be ignored. This makes the data sets massively smaller, with no loss of actual collected data (I hope ;-). There is a slight loss of data synchrony, but that should be on the order of 8Hz, so should not affect data processing.