Skip to content

Submodules #46

Description

@smwoodman

The current modules are getting unwieldy. For instance, slocum has 10+ functions, while utils has 20+. It is getting hard to track and manage functions within a module.

More importantly, these modules contain functions with a variety of utilities. slocum contains functions that do core slocum glider data processing (eg binary_to_raw_timeseries, as well as pipeline-specific functions (binary_to_nc). The way it is currently structured, it is unclear which fuctions are which. Similarly in utils, some functions are file path management convenience functions, some check glider data, and some get certain info (among several others). Splitting these into submodules will make long-term maintenance, development, and integration that much easier.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Hold

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions