GitHub user huikyole opened a pull request:
https://github.com/apache/climate/pull/144
CLIMATE-564: Managing multiple netcdf files stored on a local machine
Mike, thanks a million for your review and valuable advice.
There is a similar function named plotAccuInTimeRange in
https://github.com/apache/climate/blob/master/mccsearch/code/mccSearch.py,
although this function does not use any OCW libraries and only works for TRMM
data.
Some changes have been amended.
- Hard coded file paths have been removed.
- No space near '=' for keyword parameters.
- All of the print statements have been removed.
Somehow, users of load_files want to check the name of netCDF files. For
example, if we want to look at summer time precipitation datasets for 2006,
there are 92 files to read for each simulation. Do you have a better suggestion
other than removing 'print'?
Currently, OCW assumes that all the datasets are regularly gridded. If we
spatially subset some model outputs whose data are irregularly gridded,
value_dim = 2 and values.shape = (time_count, grid_count). I would suggest
commenting out 'utils.normalize_lat_lon_values' in class Dataset because the
assumption of data structure does not make any sense for the irregularly
gridded data.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/huikyole/climate CLIMATE-564
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/climate/pull/144.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #144
----
commit 4d372fe4d43272e6e99a455b798dc7fb53c96332
Author: Huikyo Lee <[email protected]>
Date: 2015-01-16T02:46:36Z
CLIMATE-564: Managing multiple netcdf files stored on a local machine
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
