You can subscribe to this list here.
2000 |
Jan
(8) |
Feb
(49) |
Mar
(48) |
Apr
(28) |
May
(37) |
Jun
(28) |
Jul
(16) |
Aug
(16) |
Sep
(44) |
Oct
(61) |
Nov
(31) |
Dec
(24) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(56) |
Feb
(54) |
Mar
(41) |
Apr
(71) |
May
(48) |
Jun
(32) |
Jul
(53) |
Aug
(91) |
Sep
(56) |
Oct
(33) |
Nov
(81) |
Dec
(54) |
2002 |
Jan
(72) |
Feb
(37) |
Mar
(126) |
Apr
(62) |
May
(34) |
Jun
(124) |
Jul
(36) |
Aug
(34) |
Sep
(60) |
Oct
(37) |
Nov
(23) |
Dec
(104) |
2003 |
Jan
(110) |
Feb
(73) |
Mar
(42) |
Apr
(8) |
May
(76) |
Jun
(14) |
Jul
(52) |
Aug
(26) |
Sep
(108) |
Oct
(82) |
Nov
(89) |
Dec
(94) |
2004 |
Jan
(117) |
Feb
(86) |
Mar
(75) |
Apr
(55) |
May
(75) |
Jun
(160) |
Jul
(152) |
Aug
(86) |
Sep
(75) |
Oct
(134) |
Nov
(62) |
Dec
(60) |
2005 |
Jan
(187) |
Feb
(318) |
Mar
(296) |
Apr
(205) |
May
(84) |
Jun
(63) |
Jul
(122) |
Aug
(59) |
Sep
(66) |
Oct
(148) |
Nov
(120) |
Dec
(70) |
2006 |
Jan
(460) |
Feb
(683) |
Mar
(589) |
Apr
(559) |
May
(445) |
Jun
(712) |
Jul
(815) |
Aug
(663) |
Sep
(559) |
Oct
(930) |
Nov
(373) |
Dec
|
From: Perry G. <pe...@st...> - 2006-06-01 20:42:42
|
Just to clarify the issue with regard to numarray since one person brought it up. When we (STScI) are finished getting all our software running under numpy--and we are well more than halfway there--we will start drawing down support for numarray. It won't suddenly stop, but less and less effort will go into it and eventually none. That transition time (starts when we can run all our software on numpy and stops when we no longer support numarray at all) will probably be on the order of 6 months, but note that for much of that time, the support will likely be limited to dealing with major bugs only or support for new versions of major platforms. We will note the start and stop points of this transition on the numpy and scipy lists of course. After that, any support for it will have to come from elsewhere. (Message: if you use numarray, you should be planning now to make the transition if 6 months isn't enough time) Perry |
From: Travis O. <oli...@ie...> - 2006-06-01 20:20:44
|
Berthold Höllmann wrote: > Travis Oliphant <oli...@ie...> writes: > > >> 2) Will you transition within the next 6 months? (if you answered No to #1) >> > > Unlikely > > >> 3) Please, explain your reason(s) for not making the switch. (if you >> answered No to #2) >> > > Lack of resources (Numeric is used in hand coded extensions; are > arrays of type PyObject supported in NumPy, they were not in numarray) > Yes, NumPy is actually quite similar to Numeric. Most C-extensions are easily ported simply by replacing #include Numeric/arrayobject.h with #include numpy/arrayobject.h (and making sure you get the right location for the headers). -Travis |
From: Robert K. <rob...@gm...> - 2006-06-01 20:13:44
|
Charlie Moad wrote: > Here's my crack at it. > > pts = mgrid[minx:maxx,miny:maxy].transpose() > pts.reshape(pts.size/2, 2) > #pts is good to go Well, if we're going for terseness: points = mgrid[minx:maxx, miny:maxy].reshape(2, -1).transpose() -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco |
From: Charlie M. <cw...@gm...> - 2006-06-01 20:08:08
|
Here's my crack at it. pts = mgrid[minx:maxx,miny:maxy].transpose() pts.reshape(pts.size/2, 2) #pts is good to go On 6/1/06, Christopher Barker <Chr...@no...> wrote: > > I'm trying to get the (x,y) coords for all the points in a grid, bound > by xmin, xmax, ymin, ymax. > > This list comprehension does it fine: > > Points = [(x,y) for x in xrange(minx, maxx) for y in xrange(miny, maxy)] > > But I can't think at the moment how to do it with numpy. Any ideas? > > Thanks, > > -Chris > > > -- > Christopher Barker, Ph.D. > Oceanographer > > NOAA/OR&R/HAZMAT (206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > Chr...@no... > > > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > |
From: Tim H. <tim...@co...> - 2006-06-01 19:58:50
|
Christopher Barker wrote: > Thanks all, > > > Robert Kern wrote: > >> Look at vstack() (and also its friends hstack(), dstack() and >> column_stack() for >> completeness). > > > I like this, but need to keep Numeric/numarray compatibility for the > moment -- I think, I've just sent out a query to my users. > > > > Tim Hochberg wrote: > >> If you are using real arrays, use newaxis: >> >> >>> a >> array([0, 1, 2]) >> >>> b >> array([3, 4, 5]) >> >>> concatenate([a[newaxis], b[newaxis]], 0) >> array([[0, 1, 2], >> [3, 4, 5]]) > > > I like this, but again, not in Numeric -- I really need to dump that > as soon as I can! In Numeric, you can use NewAxis instead for the same effect. > >> hate newaxis, wrap the arrays in [] to give them an extra dimension. >> This tends to look nicer, but I suspect has poorer performance than >> above (haven't timed it though): >> >> >>> concatenate([[a], [b]], 0) >> array([[0, 1, 2], >> [3, 4, 5]]) > > > Lovely. much cleaner. > > By they way, wouldn't wrapping in a tuple, be slightly better, > performance-wise (I know, probably negligible, but I always feel that > I should use a tuple when I don't need mutability) I doubt it would make a signifigant difference and the square brackets are much easier to read IMO. Your mileage may vary. -tim |
From: Sasha <nd...@ma...> - 2006-06-01 19:26:11
|
>>> mgrid[0:10, 5:15].reshape(2,100).transpose() array([[ 0, 5], [ 0, 6], [ 0, 7], [ 0, 8], ...]) On 6/1/06, Robert Kern <rob...@gm...> wrote: > Christopher Barker wrote: > > > > I'm trying to get the (x,y) coords for all the points in a grid, bound > > by xmin, xmax, ymin, ymax. > > > > This list comprehension does it fine: > > > > Points = [(x,y) for x in xrange(minx, maxx) for y in xrange(miny, maxy)] > > > > But I can't think at the moment how to do it with numpy. Any ideas? > > In [4]: x, y = mgrid[0:10, 5:15] > > In [5]: x > Out[5]: > array([[0, 0, 0, 0, 0, 0, 0, 0, 0, 0], > [1, 1, 1, 1, 1, 1, 1, 1, 1, 1], > [2, 2, 2, 2, 2, 2, 2, 2, 2, 2], > [3, 3, 3, 3, 3, 3, 3, 3, 3, 3], > [4, 4, 4, 4, 4, 4, 4, 4, 4, 4], > [5, 5, 5, 5, 5, 5, 5, 5, 5, 5], > [6, 6, 6, 6, 6, 6, 6, 6, 6, 6], > [7, 7, 7, 7, 7, 7, 7, 7, 7, 7], > [8, 8, 8, 8, 8, 8, 8, 8, 8, 8], > [9, 9, 9, 9, 9, 9, 9, 9, 9, 9]]) > > In [6]: y > Out[6]: > array([[ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], > [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], > [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], > [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], > [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], > [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], > [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], > [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], > [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], > [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14]]) > > In [8]: points = column_stack((x.ravel(), y.ravel())) > > In [9]: points > Out[9]: > array([[ 0, 5], > [ 0, 6], > [ 0, 7], > [ 0, 8], > [ 0, 9], > [ 0, 10], > ... > > -- > Robert Kern > > "I have come to believe that the whole world is an enigma, a harmless enigma > that is made terrible by our own mad attempt to interpret it as though it had > an underlying truth." > -- Umberto Eco > > > > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > |
From: Robert K. <rob...@gm...> - 2006-06-01 19:20:10
|
Christopher Barker wrote: > > I'm trying to get the (x,y) coords for all the points in a grid, bound > by xmin, xmax, ymin, ymax. > > This list comprehension does it fine: > > Points = [(x,y) for x in xrange(minx, maxx) for y in xrange(miny, maxy)] > > But I can't think at the moment how to do it with numpy. Any ideas? In [4]: x, y = mgrid[0:10, 5:15] In [5]: x Out[5]: array([[0, 0, 0, 0, 0, 0, 0, 0, 0, 0], [1, 1, 1, 1, 1, 1, 1, 1, 1, 1], [2, 2, 2, 2, 2, 2, 2, 2, 2, 2], [3, 3, 3, 3, 3, 3, 3, 3, 3, 3], [4, 4, 4, 4, 4, 4, 4, 4, 4, 4], [5, 5, 5, 5, 5, 5, 5, 5, 5, 5], [6, 6, 6, 6, 6, 6, 6, 6, 6, 6], [7, 7, 7, 7, 7, 7, 7, 7, 7, 7], [8, 8, 8, 8, 8, 8, 8, 8, 8, 8], [9, 9, 9, 9, 9, 9, 9, 9, 9, 9]]) In [6]: y Out[6]: array([[ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14], [ 5, 6, 7, 8, 9, 10, 11, 12, 13, 14]]) In [8]: points = column_stack((x.ravel(), y.ravel())) In [9]: points Out[9]: array([[ 0, 5], [ 0, 6], [ 0, 7], [ 0, 8], [ 0, 9], [ 0, 10], ... -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco |
From: Christopher B. <Chr...@no...> - 2006-06-01 19:13:47
|
Thanks all, Robert Kern wrote: > Look at vstack() (and also its friends hstack(), dstack() and column_stack() for > completeness). I like this, but need to keep Numeric/numarray compatibility for the moment -- I think, I've just sent out a query to my users. Tim Hochberg wrote: > If you are using real arrays, use newaxis: > > >>> a > array([0, 1, 2]) > >>> b > array([3, 4, 5]) > >>> concatenate([a[newaxis], b[newaxis]], 0) > array([[0, 1, 2], > [3, 4, 5]]) I like this, but again, not in Numeric -- I really need to dump that as soon as I can! > hate newaxis, wrap the arrays in [] to give them an extra dimension. > This tends to look nicer, but I suspect has poorer performance than > above (haven't timed it though): > > >>> concatenate([[a], [b]], 0) > array([[0, 1, 2], > [3, 4, 5]]) Lovely. much cleaner. By they way, wouldn't wrapping in a tuple, be slightly better, performance-wise (I know, probably negligible, but I always feel that I should use a tuple when I don't need mutability) -thanks, -chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Christopher B. <Chr...@no...> - 2006-06-01 19:05:08
|
I'm trying to get the (x,y) coords for all the points in a grid, bound by xmin, xmax, ymin, ymax. This list comprehension does it fine: Points = [(x,y) for x in xrange(minx, maxx) for y in xrange(miny, maxy)] But I can't think at the moment how to do it with numpy. Any ideas? Thanks, -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Tim H. <tim...@co...> - 2006-06-01 18:46:58
|
Christopher Barker wrote: > I want to take two (2,) arrays and put them together into one (2,2) > array. I thought one of these would work: > > >>> N.concatenate(((1,2),(3,4)),0) > array([1, 2, 3, 4]) > >>> N.concatenate(((1,2),(3,4)),1) > array([1, 2, 3, 4]) > > Is this the best I can do? > > >>> N.concatenate(((1,2),(3,4))).reshape(2,2) > array([[1, 2], > [3, 4]]) > > Is it because the arrays I'm putting together are rank-1? Yes. You need to add a dimension somehow. There are (at least) two ways to do this. If you are using real arrays, use newaxis: >>> a array([0, 1, 2]) >>> b array([3, 4, 5]) >>> concatenate([a[newaxis], b[newaxis]], 0) array([[0, 1, 2], [3, 4, 5]]) Alternatively, if you don't know that 'a' and 'b' are arrays or you just hate newaxis, wrap the arrays in [] to give them an extra dimension. This tends to look nicer, but I suspect has poorer performance than above (haven't timed it though): >>> concatenate([[a], [b]], 0) array([[0, 1, 2], [3, 4, 5]]) -tim > > >>> N.__version__ > '0.9.6' > > -Chris > > > > > |
From: Alan G I. <ai...@am...> - 2006-06-01 18:44:54
|
On Thu, 01 Jun 2006, Christopher Barker apparently wrote:=20 > Is this the best I can do?=20 > >>> N.concatenate(((1,2),(3,4))).reshape(2,2)=20 > array([[1, 2],=20 > [3, 4]])=20 >>> import numpy as N >>> N.vstack([(1,2),(3,4)]) array([[1, 2], [3, 4]]) hth, Alan Isaac |
From: Alexandre F. <ale...@lo...> - 2006-06-01 18:44:47
|
On Thu, Jun 01, 2006 at 11:32:06AM -0700, Christopher Barker wrote: > I want to take two (2,) arrays and put them together into one (2,2)=20 > array. I thought one of these would work: >=20 > >>> N.concatenate(((1,2),(3,4)),0) > array([1, 2, 3, 4]) > >>> N.concatenate(((1,2),(3,4)),1) > array([1, 2, 3, 4]) >=20 > Is this the best I can do? >=20 > >>> N.concatenate(((1,2),(3,4))).reshape(2,2) > array([[1, 2], > [3, 4]]) >=20 > Is it because the arrays I'm putting together are rank-1? concatenate is not meant to do that. Try putting your arrays in a list and building an array from that list.=20 a1 =3D array([1,2]) a2 =3D array([3,4]) print array([a1, a2]) /bin/bash: q: command not found --=20 Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations D=E9veloppement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science |
From: Robert K. <rob...@gm...> - 2006-06-01 18:42:22
|
Christopher Barker wrote: > I want to take two (2,) arrays and put them together into one (2,2) > array. I thought one of these would work: > >>>> N.concatenate(((1,2),(3,4)),0) > array([1, 2, 3, 4]) >>>> N.concatenate(((1,2),(3,4)),1) > array([1, 2, 3, 4]) > > Is this the best I can do? > >>>> N.concatenate(((1,2),(3,4))).reshape(2,2) > array([[1, 2], > [3, 4]]) > > Is it because the arrays I'm putting together are rank-1? Yes. Look at vstack() (and also its friends hstack(), dstack() and column_stack() for completeness). -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco |
From: Christopher B. <Chr...@no...> - 2006-06-01 18:32:16
|
I want to take two (2,) arrays and put them together into one (2,2) array. I thought one of these would work: >>> N.concatenate(((1,2),(3,4)),0) array([1, 2, 3, 4]) >>> N.concatenate(((1,2),(3,4)),1) array([1, 2, 3, 4]) Is this the best I can do? >>> N.concatenate(((1,2),(3,4))).reshape(2,2) array([[1, 2], [3, 4]]) Is it because the arrays I'm putting together are rank-1? >>> N.__version__ '0.9.6' -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Christopher B. <Chr...@no...> - 2006-06-01 16:54:30
|
Fernando Perez wrote: >> 2. Pointing www.numpy.org to numeric.scipy.org instead of the SF page > Well, ipython is not scipy either, and yet its homepage is > ipython.scipy.org. I think it's simply a matter of convenience that > the Enthought hosting infrastructure is so much more pleasant to use > than SF Pardon me for being a lazy idiot. numeric.scipy.org is a fine place for it. I was reacting to a post a while back that suggested pointing people searching for numpy to the main scipy page, which I did not think was a good idea. Objection withdrawn. >> Can you even build it with gcc 4 yet? > I built it on a recent ubuntu not too long ago, without any glitches. > I can check again tonitght on a fresh Dapper with up-to-date SVN if > you want. Well, I need FC4 (and soon 5) as well as OS-X, so I'll try again when I get the chance. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Robert K. <rob...@gm...> - 2006-06-01 16:47:30
|
Nadav Horesh wrote: > I recently upgraded to gcc4.1.1. When I tried to compile scipy from today's svn repository it halts with the following message: > > Traceback (most recent call last): > File "setup.py", line 50, in ? > setup_package() > File "setup.py", line 42, in setup_package > configuration=configuration ) > File "/usr/lib/python2.4/site-packages/numpy/distutils/core.py", line 170, in > setup > return old_setup(**new_attr) > File "/usr/lib/python2.4/distutils/core.py", line 149, in setup > dist.run_commands() > File "/usr/lib/python2.4/distutils/dist.py", line 946, in run_commands > self.run_command(cmd) > File "/usr/lib/python2.4/distutils/dist.py", line 966, in run_command > cmd_obj.run() > File "/usr/lib/python2.4/distutils/command/build.py", line 112, in run > self.run_command(cmd_name) > File "/usr/lib/python2.4/distutils/cmd.py", line 333, in run_command > self.distribution.run_command(command) > File "/usr/lib/python2.4/distutils/dist.py", line 966, in run_command > cmd_obj.run() > File "/usr/lib/python2.4/site-packages/numpy/distutils/command/build_ext.py", > line 109, in run > self.build_extensions() > File "/usr/lib/python2.4/distutils/command/build_ext.py", line 405, in build_e > xtensions > self.build_extension(ext) > File "/usr/lib/python2.4/site-packages/numpy/distutils/command/build_ext.py", > line 301, in build_extension > link = self.fcompiler.link_shared_object > AttributeError: 'NoneType' object has no attribute 'link_shared_object' > > ---- > > The output of gfortran --version: > > GNU Fortran 95 (GCC) 4.1.1 (Gentoo 4.1.1) Hmm. The usual suspect (not finding the version) doesn't seem to be the problem here. >>> from numpy.distutils.ccompiler import simple_version_match >>> m = simple_version_match(start='GNU Fortran 95') >>> m(None, 'GNU Fortran 95 (GCC) 4.1.1 (Gentoo 4.1.1)') '4.1.1' > I have also the old g77 compiler installed (g77-3.4.6). Is there a way to force numpy/scipy to use it? Sure. python setup.py config_fc --fcompiler=gnu build_src build_clib build_ext build -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco |
From: Nadav H. <na...@vi...> - 2006-06-01 14:17:38
|
I recently upgraded to gcc4.1.1. When I tried to compile scipy from = today's svn repository it halts with the following message: Traceback (most recent call last): File "setup.py", line 50, in ? setup_package() File "setup.py", line 42, in setup_package configuration=3Dconfiguration ) File "/usr/lib/python2.4/site-packages/numpy/distutils/core.py", line = 170, in setup return old_setup(**new_attr) File "/usr/lib/python2.4/distutils/core.py", line 149, in setup dist.run_commands() File "/usr/lib/python2.4/distutils/dist.py", line 946, in run_commands self.run_command(cmd) File "/usr/lib/python2.4/distutils/dist.py", line 966, in run_command cmd_obj.run() File "/usr/lib/python2.4/distutils/command/build.py", line 112, in run self.run_command(cmd_name) File "/usr/lib/python2.4/distutils/cmd.py", line 333, in run_command self.distribution.run_command(command) File "/usr/lib/python2.4/distutils/dist.py", line 966, in run_command cmd_obj.run() File = "/usr/lib/python2.4/site-packages/numpy/distutils/command/build_ext.py", line 109, in run self.build_extensions() File "/usr/lib/python2.4/distutils/command/build_ext.py", line 405, in = build_e xtensions self.build_extension(ext) File = "/usr/lib/python2.4/site-packages/numpy/distutils/command/build_ext.py", line 301, in build_extension link =3D self.fcompiler.link_shared_object AttributeError: 'NoneType' object has no attribute 'link_shared_object' ---- The output of gfortran --version: GNU Fortran 95 (GCC) 4.1.1 (Gentoo 4.1.1) Copyright (C) 2006 Free Software Foundation, Inc. GNU Fortran comes with NO WARRANTY, to the extent permitted by law. You may redistribute copies of GNU Fortran under the terms of the GNU General Public License. For more information about these matters, see the file named COPYING I have also the old g77 compiler installed (g77-3.4.6). Is there a way = to force numpy/scipy to use it? Nadav |
From: zpxknsxt w. <cc...@in...> - 2006-06-01 12:49:37
|
INFX**INFX**INFX**INFX**INFX**INFX**INFX**INFX** Infinex Ventures Inc. (INFX) Current Price: $0.52 The Rally has begun Watch this one like a hawk, this report is sent because the potential is incredible This is AS sure as it gets H U G E N E W S read below COMPANY OVERVIEW Aggressive and energetic, Infinex boasts a dynamic and diversified portfolio of operations across North America, with an eye on international expansion. Grounded in natural resource exploration, Inifinex also offers investors access to exciting new developments in the high-tech sector and the booming international real estate market. Our market based experience, tenacious research techniques, and razor sharp analytical skills allow us to leverage opportunities in emerging markets and developing technologies. Identifying these opportunities in the earliest stages allows us to accelerate business development and fully realize the companys true potential. Maximizing overall profitability and in turn enhancing shareholder value. Current Press Release Infinex Announces Extension to Its Agreement in Chile LAS VEGAS, NV, May 9 /PRNewswire-FirstCall/ - Infinex Ventures Inc. (INFX:OB - News; "the Company") and its Board of Directors are pleased to announce that the Company has received an extension (90 days) to its Agreement for the due diligence period, in an effort to fully verify the offered title and all additional documentation, including but not limited to, Trial C-1912- 2001 at the 14th Civil Court of Santiago and Criminal Trial 1160-2002 at the 19th Court of Crime of Santiago of Chile, Ministry of Mines of Chile over its sole and exclusive right to acquire a 50% interest in the Tesoro 1-12 Mining Claims. Infinex Announces Joint Venture and Option Agreement Extension LAS VEGAS, May 5 /PRNewswire-FirstCall/ - Infinex Ventures Inc. (INFX:OB - "the Company") and its Board of Directors are please to announce that the Company has been granted an extension of 120 days to fulfill its contractual obligations under the Joint Venture and Option Agreement dated June 14, 2004 on the Texada Island "Yew Gr0up" Mining Claims: Shake like a leaf. We'll hand you out to dry. We'll hand you out to dry. Stand your ground. Ugly as a mud fence. Scraping the bottom of the barrel. Sly as a fox. A snail's pace. Your ass is grass. There is always next year. Rise and shine. Sly as a fox. Putting the cart before the horse. Walking on thin ice. Stand your ground. Root it out. The stronger the breeze the stronger the trees. Putting it in a nutshell. This is for the birds. Wrinkled as a prune. Up one side and down the other. Rise and shine. Sour as a green apple. You say potayto, I say potahto. She's a mother hen. Say it with flowers. A thorn in my side. Weed out. |
From: Fernando P. <fpe...@gm...> - 2006-06-01 04:19:28
|
On 5/31/06, Alan G Isaac <ai...@am...> wrote: > On Wed, 31 May 2006, "Russell E. Owen" apparently wrote: > > Please improve notification of documentation updates. > > I keep seeing complaints from folks who've bought the > > numpy documentation that they get no notification of > > updates. That makes me very reluctant to buy the > > documentation myself. > > The documentation is excellent, and I've been completely > satisfied with Travis's handling of the updates. I'll add my voice on this front. When I've needed a special update (for a workshop, where I needed to print out hardcopies as up-to-date as possible), Travis was very forthcoming and gave me quickly his most recent copy. So while a few weeks ago a couple of emails may not have been replied quite on the spot, overall I don't feel in any way slighted by his handling of the doc system, quite the opposite. And he also indicated he was in the process of setting up a more automated system. To be honest, I'd rather wait for a manual upate than see Travis devote one or two evenings to configuring something of this nature when he could be coding for numpy :) Cheers, f |
From: Travis O. <oli...@ie...> - 2006-06-01 04:02:59
|
Nils Wagner wrote: >>>> numpy.__version__ >>>> > '0.9.9.2553' > > > numpy.test(1,10) results in > ====================================================================== > FAIL: check_types (numpy.core.tests.test_scalarmath.test_types) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File > "/usr/lib64/python2.4/site-packages/numpy/core/tests/test_scalarmath.py", > line 63, in check_types > assert val.dtype.num == typeconv[k,l] and \ > AssertionError: error with (0,7) > This is probably on a 64-bit system. It would be great if you could take the code in the test module and adapt it to print out the typecodes that are obtained using 0-dimensional arrays. Of course, maybe that's a better way to run the test.... -Travis > ---------------------------------------------------------------------- > Ran 368 tests in 0.479s > > FAILED (failures=1) > > Nils > > > > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion > |
From: Alan G I. <ai...@am...> - 2006-06-01 02:57:29
|
On Wed, 31 May 2006, "Russell E. Owen" apparently wrote: > Please improve notification of documentation updates. > I keep seeing complaints from folks who've bought the > numpy documentation that they get no notification of > updates. That makes me very reluctant to buy the > documentation myself. The documentation is excellent, and I've been completely satisfied with Travis's handling of the updates. It is also a minimal investment in an excellent project. fwiw, Alan Isaac |
From: Travis O. <oli...@ie...> - 2006-06-01 00:39:07
|
Stefan van der Walt wrote: > I filed this as ticket #135: > > http://projects.scipy.org/scipy/numpy/ticket/135 > > Thanks. This one is due to a bug/oddity in Python itself. Apparently complex-number subtypes can't use a different memory allocator than the Python memory allocator. I've let Python powers know about the bug and worked around it in NumPy, for now. -Travis |
From: Stefan v. d. W. <st...@su...> - 2006-05-31 23:07:34
|
I filed this as ticket #135: http://projects.scipy.org/scipy/numpy/ticket/135 Regards St=E9fan On Wed, May 31, 2006 at 05:47:25PM +0200, Nils Wagner wrote: > test_wrap (numpy.core.tests.test_umath.test_special_methods) ... ok > check_types (numpy.core.tests.test_scalarmath.test_types)*** glibc > detected *** free() : invalid pointer: > 0xb7ab74a0 *** >=20 > Program received signal SIGABRT, Aborted. |
From: Russell E. O. <ro...@ce...> - 2006-05-31 21:48:26
|
In article <447...@ie...>, Travis Oliphant <oli...@ie...> wrote: > Please help the developers by responding to a few questions. > > 1) Have you transitioned or started to transition to NumPy (i.e. import > numpy)? No, not beyond installing it to see if it works. > 2) Will you transition within the next 6 months? (if you answered No to #1) I expect to start to transition within a few months of both numpy and pyfits-with-numpy being released and being reported as stable and fast. > 4) Please provide any suggestions for improving NumPy. Please improve notification of documentation updates. I keep seeing complaints from folks who've bought the numpy documentation that they get no notification of updates. That makes me very reluctant to buy the documentation myself. I wish that full support for masked arrays had made it in (i.e. masked arrays are first class citizens that are accepted by all functions). The inability in numeric to apply 2d filters on masked image arrays is the main thing missing for me in numarray. -- Russell |
From: Fernando P. <fpe...@gm...> - 2006-05-31 21:35:23
|
On 5/31/06, Christopher Barker <Chr...@no...> wrote: > > Ed Schofield wrote: > > Improvements for NumPy's web presence: > > http://projects.scipy.org/scipy/numpy/ticket/132 > > From that page: > > NumPy's web presence could be improved by: > > 2. Pointing www.numpy.org to numeric.scipy.org instead of the SF page > > I don't like this. *numpy is not scipy*. It should have it's own page > (which would refer to scipy). That page should be something better than > the raw sourceforge page, however. Well, ipython is not scipy either, and yet its homepage is ipython.scipy.org. I think it's simply a matter of convenience that the Enthought hosting infrastructure is so much more pleasant to use than SF, that other projects use scipy.org as an umbrella. In that sense, I think it's fair to say that numpy is part of the 'scipy family'. I don't know, at least this doesn't particularly bother me. > A lot of us use numpy without anything else from the scipy project, and > scipy is still a major pain in the *&&^* to build. Can you even build it > with gcc 4 yet? I built it on a recent ubuntu not too long ago, without any glitches. I can check again tonitght on a fresh Dapper with up-to-date SVN if you want. Cheers, f |