Izzy (Isabelle) Pfander

by Isabelle Pfander
2021 Unidata summer intern

I came into this summer internship with a goal of working on the Network Common Data Form (netCDF) libraries. NetCDF is a combination of software libraries and APIs describing a data model for scientific multidimensional arrays. I planned to improve the online user guide, write tutorial code, and learn about storage and efficiency.

Lauren Prox

by Lauren Prox
2020 Unidata summer intern

During the beginning of my internship, I devoted a great deal of time learning how to use Git and Github to collaborate on software development projects. After gaining this experience, I began improving documentation for a variety of Unidata remote repositories. I started with the netCDF-C repository and then moved on to the MetPy, Siphon, and Python Training remote repositories. This work was significant as it ensured that software users were able to locate resources, properly download software, and learn how to operate the software via informational materials.

Beginning with netCDF version 4.8.0, the Unidata NetCDF group has extended the netcdf-c library to provide access to cloud storage (e.g. Amazon S3) by providing a mapping from a subset of the full netCDF Enhanced (aka netCDF-4) data model to a variant of the Zarr data model that already has mappings to key-value pair cloud storage systems.

Aodhan Sweeney

by Aodhan Sweeney
2019 Unidata summer intern

This summer at Unidata I worked on expanding functionality for both the netCDF C++ library and the Python data access tool Siphon. Previously, the netCDF C++ library was lacking important functionality that was included in other netCDF libraries. Fortunately, adding this functionality is a straightforward process. I created function wrappers in the C++ library that would call previously made functions in the C library. This allows those working in a C++ framework to continue to use the netCDF libraries without sacrificing additional functionality.

It appears to be the case that all current tests in the netcdf-c source tree are integration tests. That is they only access the library using calls to the externally visible API.

The DAP4 code testing is different in that it includes (for the first time) unit tests. These tests reference code that is considered internal to the library. For the library generated under autoconf, this is not a problem because those symbols are visible in the library: nothing is hidden.