difference between NumPy and Scipy
i saw the news of NumPy release and SciPy release. Numpy is said to be the core of Scipy. But why they have different releases? for example: NumPy 0.9.6 released! (2006-03-14) See the Download and Release Notes pages. SciPy 0.4.6 released! (2006-02-16) See the Download and Release Notes pages. NumPy 0.9.5 released! (2006-02-16) See the Download and Release Notes pages.
linda.s wrote:
i saw the news of NumPy release and SciPy release. Numpy is said to be the core of Scipy. But why they have different releases?
Because NumPy is the core of other packages as well. So, it has a different release schedule. It would be nice if NumPy and SciPy had synchronous releases, but we need more people to help with releases to make that possible. For now, SciPy releases are usually a little behind. -Travis
Travis Oliphant wrote:
linda.s wrote:
i saw the news of NumPy release and SciPy release. Numpy is said to be the core of Scipy. But why they have different releases?
Because NumPy is the core of other packages as well. So, it has a different release schedule.
It would be nice if NumPy and SciPy had synchronous releases, but we need more people to help with releases to make that possible. For now, SciPy releases are usually a little behind.
I could try to make a new SciPy release this weekend. Before then, though, I suggest we change the package name of nd_image. Here was my proposal from a previous thread:
I have a minor suggestion: that we rename the package from 'nd_image' to 'image' for consistency with the other packages, like 'signal', 'optimize' and 'sparse'. There's currently an 'image' package in the sandbox, but that looks much less mature, and should probably be integrated with the existing package when it actually does come into the main tree.
What do people think? At the very least we should remove the underscore, so it's more consistent with linalg and fftpack (which aren't lin_alg, fft_pack ;) -- Ed
On Thu, 16 Mar 2006, Ed Schofield wrote: [...]
I could try to make a new SciPy release this weekend.
that would be great! (for various reasons;-)
Before then, though, I suggest we change the package name of nd_image. Here was my proposal from a previous thread:
I have a minor suggestion: that we rename the package from 'nd_image' to 'image' for consistency with the other packages, like 'signal', 'optimize' and 'sparse'. There's currently an 'image' package in the sandbox, but that looks much less mature, and should probably be integrated with the existing package when it actually does come into the main tree.
What do people think? At the very least we should remove the underscore, so it's more consistent with linalg and fftpack (which aren't lin_alg, fft_pack ;)
+1 for image - the shorter the better ;-) Arnd
Ed Schofield wrote:
I could try to make a new SciPy release this weekend.
Before then, though, I suggest we change the package name of nd_image. Here was my proposal from a previous thread:
I have a minor suggestion: that we rename the package from 'nd_image' to 'image' for consistency with the other packages, like 'signal', 'optimize' and 'sparse'. There's currently an 'image' package in the sandbox, but that looks much less mature, and should probably be integrated with the existing package when it actually does come into the main tree.
What do people think? At the very least we should remove the underscore, so it's more consistent with linalg and fftpack (which aren't lin_alg, fft_pack ;)
Probably the right thing to do, especially as we improve it. Right now it's just a copy of nd_image from numarray (thus the name). Anybody who wants to make the necessary name changes is welcome. -Travis
Travis Oliphant wrote:
Ed Schofield wrote:
I could try to make a new SciPy release this weekend.
Before then, though, I suggest we change the package name of nd_image.
Probably the right thing to do, especially as we improve it. Right now it's just a copy of nd_image from numarray (thus the name).
Anybody who wants to make the necessary name changes is welcome.
Done it. I've renamed the package at the Python level; the C module is still available to Python as _nd_image, with the leading underscore etc. Is the nd_image package still being maintained in numarray, or is SciPy now its official home? :) -- Ed
Ed Schofield wrote:
Travis Oliphant wrote:
Ed Schofield wrote:
I could try to make a new SciPy release this weekend.
Before then, though, I suggest we change the package name of nd_image.
Probably the right thing to do, especially as we improve it. Right now it's just a copy of nd_image from numarray (thus the name).
Anybody who wants to make the necessary name changes is welcome.
Done it. I've renamed the package at the Python level; the C module is still available to Python as _nd_image, with the leading underscore etc.
Is the nd_image package still being maintained in numarray, or is SciPy now its official home? :)
Peter, the original author, has said (for reasons that were not entirely clear) that he will not be supporting the numpy version (or eventually the numarray version, either --- I think he's planning on writing some other library-based solution). So, what we have in SciPy is "the official" home for the numpy version of his package. -Travis
Hi, I just noticed that nd_image is going to be named scipy.image. My concern is that that might remind to much of jpg,bmp,tiff,... image files... Also "image" sounds very 2d ! like 'picture' ;-) I thought that Peter Verveer's nd_image name took nicely care of both of these concerns... (As a reminder: Peter's package contains lot's of generic ND filtering and some nice segmentation and morphology routines: Multi-dimensional image processing [http://stsdas.stsci.edu/numarray/numarray-1.5.html/module-numarray.ndimage.h...]) Did I miss the beginning of this thread ? Just my 2 cents. - Sebastian Haase Travis Oliphant wrote:
Ed Schofield wrote:
Travis Oliphant wrote:
Ed Schofield wrote:
I could try to make a new SciPy release this weekend.
Before then, though, I suggest we change the package name of nd_image.
Probably the right thing to do, especially as we improve it. Right now it's just a copy of nd_image from numarray (thus the name).
Anybody who wants to make the necessary name changes is welcome.
Done it. I've renamed the package at the Python level; the C module is still available to Python as _nd_image, with the leading underscore etc.
Is the nd_image package still being maintained in numarray, or is SciPy now its official home? :)
Peter, the original author, has said (for reasons that were not entirely clear) that he will not be supporting the numpy version (or eventually the numarray version, either --- I think he's planning on writing some other library-based solution).
So, what we have in SciPy is "the official" home for the numpy version of his package.
-Travis
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.net http://www.scipy.net/mailman/listinfo/scipy-user
Sebastian Haase wrote:
Hi, I just noticed that nd_image is going to be named scipy.image. My concern is that that might remind to much of jpg,bmp,tiff,... image files... Also "image" sounds very 2d ! like 'picture' ;-)
True, it might give that connotation. While I'm not one who thinks much of the distinction between 2-d and N-d, there are many that do, So, perhaps we should rename (yet again --- isn't SVN nice :-) ) the library to ndimage or imagend, or something like that. -Travis
On 17/03/2006, at 9:26 AM, Travis Oliphant wrote:
Sebastian Haase wrote:
Hi, I just noticed that nd_image is going to be named scipy.image. My concern is that that might remind to much of jpg,bmp,tiff,... image files... Also "image" sounds very 2d ! like 'picture' ;-)
True, it might give that connotation. While I'm not one who thinks much of the distinction between 2-d and N-d, there are many that do,
So, perhaps we should rename (yet again --- isn't SVN nice :-) ) the library to ndimage or imagend, or something like that.
I don't think an image has to be 2-d. And the package easily handles 2-d images as a special case, right? ;) But I don't feel particularly strongly about it. What do other people think? -- Ed
Hi,
I just noticed that nd_image is going to be named scipy.image. My concern is that that might remind to much of jpg,bmp,tiff,... image files... Also "image" sounds very 2d ! like 'picture' ;-)
My vote is for ndimage - I tend to agree about 'image' being slightly confusing. Matthew
On Friday 17 March 2006 03:32, Matthew Brett wrote:
Hi,
I just noticed that nd_image is going to be named scipy.image. My concern is that that might remind to much of jpg,bmp,tiff,... image files... Also "image" sounds very 2d ! like 'picture' ;-)
My vote is for ndimage - I tend to agree about 'image' being slightly confusing.
Matthew
ndimage would probably be my vote too - nd_image was OK too... ( I don't like image_n !) -- - Sebastian Haase
Sebastian Haase wrote:
On Friday 17 March 2006 03:32, Matthew Brett wrote:
Hi,
I just noticed that nd_image is going to be named scipy.image. My concern is that that might remind to much of jpg,bmp,tiff,... image files... Also "image" sounds very 2d ! like 'picture' ;-)
My vote is for ndimage - I tend to agree about 'image' being slightly confusing.
Matthew
ndimage would probably be my vote too - nd_image was OK too... ( I don't like image_n !)
I think in scipy we're trying to (loosely) follow the Python naming PEP, which discourages underscores in module names. In that case, ndimage would win over nd_image. Cheers, f
i vote for ndimage as well.... -- jonathan Fernando Perez wrote:
Sebastian Haase wrote:
On Friday 17 March 2006 03:32, Matthew Brett wrote:
Hi,
I just noticed that nd_image is going to be named scipy.image. My concern is that that might remind to much of jpg,bmp,tiff,... image files... Also "image" sounds very 2d ! like 'picture' ;-)
My vote is for ndimage - I tend to agree about 'image' being slightly confusing.
Matthew
ndimage would probably be my vote too - nd_image was OK too... ( I don't like image_n !)
I think in scipy we're trying to (loosely) follow the Python naming PEP, which discourages underscores in module names. In that case, ndimage would win over nd_image.
Cheers,
f
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.net http://www.scipy.net/mailman/listinfo/scipy-user
-- ------------------------------------------------------------------------ I'm part of the Team in Training: please support our efforts for the Leukemia and Lymphoma Society! http://www.active.com/donate/tntsvmb/tntsvmbJTaylor GO TEAM !!! ------------------------------------------------------------------------ Jonathan Taylor Tel: 650.723.9230 Dept. of Statistics Fax: 650.725.8977 Sequoia Hall, 137 www-stat.stanford.edu/~jtaylo 390 Serra Mall Stanford, CA 94305
Matthew Brett wrote:
Hi,
I just noticed that nd_image is going to be named scipy.image. My concern is that that might remind to much of jpg,bmp,tiff,... image files... Also "image" sounds very 2d ! like 'picture' ;-)
My vote is for ndimage - I tend to agree about 'image' being slightly confusing.
+1 on ndimage: scipy includes pilutils, which wraps the PIL whose import statement is import Image and is very oriented towards 'image as a picture' processing. I think it's a good idea to avoid confusion in the minds of possible users between the well established Image module and scipy's more flexible (but with a different focus) n-dimensional package. Cheers, f
On Fri, 17 Mar 2006, Alan G Isaac wrote:
On Fri, 17 Mar 2006, Travis Oliphant apparently wrote:
ndimage or imagend
or image_n (imagine)
great - what about another round of name-changing including a voting page? (I loved the one leading to numpy ...;-) Sorry, couldn't resist, Arnd
I think, in the true spirit of python, every extension module should be renamed Bruce. Slightly more seriously, I agree it should be changed to avoid confusion with PIL. You could call it ndimage or imageproc or ndimproc. Gary R Arnd Baecker wrote:
On Fri, 17 Mar 2006, Alan G Isaac wrote:
On Fri, 17 Mar 2006, Travis Oliphant apparently wrote:
ndimage or imagend or image_n (imagine)
great - what about another round of name-changing including a voting page? (I loved the one leading to numpy ...;-)
Sorry, couldn't resist, Arnd
On 3/17/06, Gary Ruben <gruben@bigpond.net.au> wrote:
I think, in the true spirit of python, every extension module should be renamed Bruce.
Slightly more seriously, I agree it should be changed to avoid confusion with PIL. You could call it ndimage or imageproc or ndimproc.
In the spirit of political correctness, every other extension module should be renamed Sheila. I prefer imageproc over ndimage for what it's worth. -- Paul
participants (12)
-
Alan G Isaac -
Arnd Baecker -
Ed Schofield -
Fernando Perez -
Gary Ruben -
Jonathan Taylor -
linda.s -
Matthew Brett -
Paul Barrett -
Sebastian Haase -
Travis Oliphant -
Travis Oliphant