Opened 18 years ago

Closed 15 years ago

#58 closed defect (fixed)

Consider migrating ANUGA to use numpy (from scipy) rather than Numeric

Reported by: ole Owned by: rwilson
Priority: highest Milestone:
Component: Architecture and API Version: 1.0
Severity: normal Keywords: numpy migration
Cc:

Description

Change History (6)

comment:1 Changed 18 years ago by anonymous

  • Owner changed from someone to ole

SVN Branch Created and migration started.

Problem: Scientific.IO.NetCDF does not yet work with numpy. See http://starship.python.net/~hinsen/ScientificPython

comment:2 Changed 18 years ago by anonymous

  • Priority changed from normal to lowest

This has been looked into . Numpy was good. Netcdf is not supported though, so we will stick with Numeric

comment:3 Changed 17 years ago by ole

It seems that NetCDF is now supported:

See http://netcdf4-python.googlecode.com/svn/trunk/docs/netCDF4-module.html or http://code.google.com/p/netcdf4-python/ or http://pydap.org/plugins/netcdf.html

This may also solve the 2GB limitation mentioned in ticket:35

Numpy can be downloaded at http://www.numpy.org/

comment:4 Changed 16 years ago by ole

  • Keywords numpy migration added
  • Owner changed from ole to rwilson
  • Priority changed from lowest to highest

Initial work towards migration to Numpy was done in changeset:2544 through to changeset:2548 as well as changeset:3749. It wasn't too hard but the NetCDF issue stopped the progress at the time. Now, two years later, we are pretty optimistic that it'll work.

comment:5 Changed 15 years ago by rwilson

  • Status changed from new to assigned

comment:6 Changed 15 years ago by sexton

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.