Activity for Ken Mankoff
-
Ken Mankoff posted a comment on discussion Help
Hi Charlie, The file with two missing_value actually processes orders of magnitude faster. The other is the slow one. Digging further, I find that the fast file has empty LON and LAT arrays, but the slow one has populated LON and LAT arrays (and for some reason, using weird range/values) float LON(y, x) ; LON:units = "Degree" ; LON:actual_range = -639.4561f, 855.5441f ; Can you advise what nco command can empty a variable so that ncdump shows: LON = , , , , , , , , , , , , , , , , , , , , , , , ,...
-
I have two NetCDF files from a regional climate model. When I post-process one variable w/ Python (xarray + dask) it takes 3 minutes. When I post-process another it takes 3 days (!). The only difference appears to be the metadata. I'd like to clone the "fast" metadata to the "slow" file to see if that fixes things. Below is the fast metadat, then the slow, then the diff. Can you advise how to use nco to do this? Thanks, -k. FAST: dimensions: time = 90 ; x = 1496 ; y = 2700 ; variables: float time(time)...
-
I have two NetCDF files from a regional climate model. When I post-process one variable w/ Python (xarray + dask) it takes 3 minutes. When I post-process another it takes 3 days (!). The only difference appears to be the metadata. I'd like to clone the "fast" metadata to the "slow" file to see if that fixes things. Below is the fast metadat, then the slow, then the diff. Can you advise how to use nco to do this? Thanks, -k. FAST: dimensions: time = 90 ; x = 1496 ; y = 2700 ; variables: float time(time)...
-
I have two NetCDF files from a regional climate model. When I post-process one variable w/ Python (xarray + dask) it takes 3 minutes. When I post-process another it takes 3 days (!). The only difference appears to be the metadata. I'd like to clone the "fast" metadata to the "slow" file to see if that fixes things. Below is the fast metadat, then the slow, then the diff. Can you advise how to use nco to do this? Thanks, -k. FAST: dimensions: time = 90 ; x = 1496 ; y = 2700 ; variables: float time(time)...
-
I have two NetCDF files from a regional climate model. When I post-process one variable w/ Python (xarray + dask) it takes 3 minutes. When I post-process another it takes 3 days (!). The only difference appears to be the metadata. I'd like to clone the "fast" metadata to the "slow" file to see if that fixes things. Below is the fast metadat, then the slow, then the diff. Can you advise how to use nco to do this? Thanks, -k. FAST: dimensions: time = 90 ; x = 1496 ; y = 2700 ; variables: float time(time)...
-
Support notes/comments/texts on highlight/strikethrough/underline
-
work-around here: https://apple.stackexchange.com/questions/79429/make-skim-save...
-
work-around here: https://apple.stackexchange.com/questions/79429/make-skim-save...
-
work-around here: https://apple.stackexchange.com/questions/79429/make-skim-save...
-
work-around here: https://apple.stackexchange.com/questions/79429/make-skim-save...
-
work-around here: https://apple.stackexchange.com/questions/79429/make-skim-save...
-
Work-around here: https://apple.stackexchange.com/questions/79429/make-skim-save...
-
Bug still exists in 1.3.3 release.
-
Perhaps this should be closed. GDL devs pointed out this bug fixed in April. GDL...
-
Yes fixed. Sorry I didn't find that previously. Thanks for the update. Now... how...
-
'plplot_config.h' file not found
-
Ah. I think this is a plplot bug then. Seems like someone recently ran into it w/...
-
I opened a new bug about building from source on OS X. PLPLOT errors are stopping...
-
More info: I'm setting up the build with cmake, and I've tried turning on and off...
-
PLPLOT compile error on OS X 10.9 Mavericks
-
Correct this is not a Hombrew issue but a feature request (or platform port request?)...
-
Show interior/exterior dimensions
-
Support OS X install via Homebrew
1