Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move the "extras" data to be in their own profile netCDF file #18

Merged
merged 3 commits into from
Apr 26, 2022

Conversation

kwilcox
Copy link
Member

@kwilcox kwilcox commented Apr 25, 2022

This assumes that the "extras" data occurs before or after a profile
and for now I think that is OK. This reduces the complexity of the
code quite a bit. We just make the "extras" data look like a profile
dataset, optionally setting the depths to zero if there are no depths
to capture the data as surface measurements.

This also changes some of the extras configuration kwarg names so we
can control the creation of the ASCII pseudogram and the inclustion
of that data into the netCDF profile files, and the image creation.

This assumes that the "extras" data occurs before or after a profile
and for now I think that is OK. This reduces the complexity of the
code quite a bit. We just make the "extras" data look like a profile
dataset, optionally setting the depths to zero if there are no depths
to capture the data as surface measurements.

This also changes some of the extras configuration kwarg names so we
can control the creation of the ASCII pseudogram and the inclustion
of that data into the netCDF profile files, and the image creation.
@jr3cermak jr3cermak mentioned this pull request Apr 25, 2022
6 tasks
@kwilcox kwilcox merged commit f32d479 into master Apr 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant