NOAA-PMEL / Python_Users_Group

Collection of documents and notes for PMEL Python Users Group
The Unlicense
0 stars 0 forks source link

Welcome! Request for Future Topics #1

Open shaunwbell opened 7 years ago

shaunwbell commented 7 years ago

Reply to this thread to request future topics.

Some that came up already...

  1. Does python with its netcdf4 package, handle netcdf files generated with parallel I/O?

  2. How does python deal with large netcdf data files? How does xarray deal with large netcdf data files? How does enabling DASK in xarray help?

(we can post answers as example programs or start new issues for discussion on any one topic)

shaunwbell commented 7 years ago

Do Pure Python or Primarily Python/Cython Ocean or Atmospheric models exist?

crdietrich-noaa commented 7 years ago

Picking and deploying an interpreter and package manager at PMEL, best choices? Current limitations? http://python-guide-pt-br.readthedocs.io/en/latest/starting/which-python/ and conda/pip/etc?

On Wed, May 17, 2017 at 2:33 PM, shaunwbell notifications@github.com wrote:

Do Pure Python or Primarily Python/Cython Ocean or Atmospheric models exist?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NOAA-PMEL/Python_Users_Group/issues/1#issuecomment-302237961, or mute the thread https://github.com/notifications/unsubscribe-auth/APuxXyvKL315eJd4F_XWKgCD_lQ0Demuks5r62eWgaJpZM4Nedep .

-- Colin Dietrich Research Scientist Carbon Program | Pacific Marine Environmental Laboratory NOAA-UW Joint Institute for the Study of the Atmosphere and Ocean 206-526-6195 | Alt: colinrd@uw.edu

shaunwbell commented 7 years ago

When (and how) to worry about unit tests, pylint, and other responsible programming characterstics.

crdietrich-noaa commented 7 years ago

netCDF, xarray & Pandas

On Wed, May 17, 2017 at 3:21 PM, shaunwbell notifications@github.com wrote:

When (and how) to worry about unit tests, pylint, and other responsible programming characterstics.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NOAA-PMEL/Python_Users_Group/issues/1#issuecomment-302247894, or mute the thread https://github.com/notifications/unsubscribe-auth/APuxX4Ft39ubXNkyslSIOwarLqp2Nv8Kks5r63LWgaJpZM4Nedep .

-- Colin Dietrich Research Scientist Carbon Program | Pacific Marine Environmental Laboratory NOAA-UW Joint Institute for the Study of the Atmosphere and Ocean 206-526-6195 | Alt: colinrd@uw.edu

nanderson123 commented 7 years ago

1) General programming techniques and modularizing code.

2a) Handling "big data" and netcdf files in the tens of terrabytes (coming soon).

2b) Plotting "big data". I've already run into plots freezing, not zooming, etc. when plotting a year's worth of 1min data, and 20Hz data will be 1200x as dense. Slicing/minimizing can help, but any QC issues are then harder to detect by eye, since we do always visualize our data before posting. Filtering (e.g. hanning) to other resolutions will also start to be a computing challenge.

3) Working with netcdf3 vs netcdf4, and tools for reading/viewing netcdf in python (I currently write netcdf in python and/or matlab, but read them exclusively in matlab, since I have a one-click script to load data as doubles or netcdf4 data as structures if groups are involved).

Thanks,