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.

Sign up for GitHub

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

Jump to bottom

PyDisdrometer Roadmap #24

Open
9 of 12 tasks
josephhardinee opened this issue Apr 18, 2016 · 1 comment
Open
9 of 12 tasks

PyDisdrometer Roadmap #24

josephhardinee opened this issue Apr 18, 2016 · 1 comment
Milestone
v1.1

Comments

@josephhardinee
Copy link
Owner

josephhardinee commented Apr 18, 2016 •
edited
Loading

After talking with @nguy the following represents what we see as the roadmap to getting PyDisdrometer to a V1 release.

  • All readers using standardized Time.
  • File Saving ( Will standardize a format, netcdf Based).
  • All Readers Consistent syntax and internal structure, extendable.
  • Standard Plotting Routines setup
  • Documentation and Cookbook examples finalized
  • Masked arrays for fields.
  • Rename to PyDSD to represent the larger number of instruments we will support
  • Readers moved into .io
  • All fields more consistent with labeling(Dictionary Syntax)
  • Documentation Generation in Travis-CI
  • Arbitrary Dielectric Scattering/Temperature.
  • Implement the rest of pyparticleprobes dsd parameter calculation
    I'm sure I'm missing a few things. Nick, if you want to comment on anything else I'll add it to the list.
@nguy
Copy link
Collaborator

nguy commented Apr 19, 2016

I would say the readers to have consistent core structure with the ability to be extendable.

Also and expansion of DSD parameter calculations.

@josephhardinee josephhardinee added this to the v1.0 - New Name and pyparticleprobe merge. milestone Sep 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.1
Development

No branches or pull requests
2 participants
@josephhardinee @nguy