On Thu, Nov 6, 2008 at 1:55 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 6, 2008 at 15:12, Barry Wark <[EMAIL PROTECTED]> wrote:
>> On Thu, Nov 6, 2008 at 12:09 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>>> On Thu, Nov 6, 2008 at 14:05, Barry Wark
On Thu, Nov 6, 2008 at 12:09 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 6, 2008 at 14:05, Barry Wark <[EMAIL PROTECTED]> wrote:
>> I'm just about to embark on a long-term research project and was
>> planning to use numpy.random to generate stimuli fo
I'm just about to embark on a long-term research project and was
planning to use numpy.random to generate stimuli for our experiments.
We plan to store only the parameters and RandomState seed for each
stimulus and I'm concerned about stability of the API in the long
term: will the parameters and r
On Mon, Sep 29, 2008 at 8:24 PM, Anne Archibald
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> Once again there has been a thread on the numpy/scipy mailing lists
> requesting (essentially) some form of spatial data structure. Pointers
> have been posted to ANN (sadly LGPLed and in C++) as well as a handful
Stéfan,
Again, thanks to you and Thomas.
cheers,
Barry
On Tue, Aug 12, 2008 at 10:08 AM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> 2008/8/12 Barry Wark <[EMAIL PROTECTED]>:
>> Stefan,
>>
>> I'm sorry I dropped the ball on this one. I didn't have
Stefan,
I'm sorry I dropped the ball on this one. I didn't have time to get
things working again before I left town for a month and, obviously,
there it sat. Again, sorry.
Barry
On Mon, Aug 11, 2008 at 3:11 PM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Due to hardware failure,
very likely a path issue. i've had two hard drive crashed on the
buildslave box this week. i'm sure something's fubar'd. i'll take a
look. thanks for the heads up.
On Wed, Jul 2, 2008 at 2:22 PM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
>
>
> On Wed, Ju
Fixed. Sorry.
On Wed, Jul 2, 2008 at 1:07 PM, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> The buildbot test command should be using sys.exit to return the
> success flag from the test run, but it's not. The FreeBSD's test
> command is:
>
> /usr/local/bin/python2.4 -c 'import numpy,sys;sys.exit(not
Could this also be added as a comment in the module docstring for
test modules? It seems that anyone hacking on test code would be most
likely to see it there...?
Barry
On Tue, Jun 10, 2008 at 2:57 AM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> 2008/6/10 Alan McIntyre <[EMAIL PROTECTED]>:
On Wed, Jun 4, 2008 at 2:40 AM, Robin <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 4, 2008 at 9:25 AM, J. Stark <[EMAIL PROTECTED]> wrote:
>> Robert,
>>
>> I see your point, but why not just install a separate NumPy to run
>> with the system Python? That is what I have always done in the past
>> withou
I appologize that the Mac OSX buildbot has been so flakey. For some
reason it stops being able to resolve scipy.org on a regular basis
(though other processes on the same machine don't seem to have
trouble). Restarting the slave fixes the issue. Anyways, if anyone is
testing an OS X issue and the s
For comparison of ctypes and SWIG wrappers of a simple C++ codebase,
feel free to take a look at the code for scikits.ann
(http://scipy.org/scipy/scikits/wiki/AnnWrapper). The original wrapper
was written using SWIG and the numpy typemaps. Rob Hetland has coded
an almost-the-same API wrapper using
thanks.
On Jan 22, 2008 10:04 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> On Jan 18, 2008 11:17 PM, Barry Wark <[EMAIL PROTECTED]> wrote:
> > I promise: last change. I changed the URL to
> > http://physionconsulting.blogspot.com/search/label/scipy. My wife said
&
Jarrod,
I promise: last change. I changed the URL to
http://physionconsulting.blogspot.com/search/label/scipy. My wife said
physion consultants is a crappy name. Oh well :)
barry
On Jan 1, 2008 6:35 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> On Jan 1, 2008 6:18 PM, Barry War
Looks great. Thanks for setting this up!
barry
On Jan 2, 2008 5:23 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> On Jan 2, 2008 1:40 PM, Stefan van der Walt <[EMAIL PROTECTED]> wrote:
> > Great, thanks! Would you mind putting links to templates like
> >
> > http://planet.scipy.org/rss20.xml
>
Jarrod,
Sorry. Correct URL: http://physionconsultants.blogspot.com/search/label/scipy
Sorry for the mix up.
Barry
On Jan 1, 2008 6:35 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> On Jan 1, 2008 6:18 PM, Barry Wark <[EMAIL PROTECTED]> wrote:
> > I'd like to submit
Jarrod,
I'd like to submit my blog for inclusion too...
http://softwareforscientists.blogspot.com/search/label/scipy
Again, not too many posts yet, but things will be ramping up.
On Jan 1, 2008 1:31 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> On Jan 1, 2008 12:07 PM, Ondrej Certik <[EMAIL P
On 11/30/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Barry Wark wrote:
>
> > Some remaining issues:
> > - which SDK to build against. Leopard ships with a Python build
> > against the 10.5 SDK. It would be much easier, at least initially, for
> > us to produce
On 11/29/07, David Cournapeau <[EMAIL PROTECTED]> wrote:
> Barry Wark wrote:
> > Using the gfortran from http://r.research.att.com/tools/, it's trivial
> > to build a universal build from source. The instructions on scipy.org
> > won't lead you astray.
> >
Using the gfortran from http://r.research.att.com/tools/, it's trivial
to build a universal build from source. The instructions on scipy.org
won't lead you astray.
I will ask around at work. Perhaps we can start building universal
scipy builds for distribution. Can anyone from the scipy devs email
The MacOSX/x86 buildslave at buildbot.scipy.org is running universal
gfortran. The output of gfortran -v -arch XX is:
siegfried:~ barry$ gfortran -v -arch i386
Using built-in specs.
Target: i686-apple-darwin8
Configured with: /Builds/unix/gcc/gcc-4.2/configure
--prefix=/usr/local --mandir=/share/m
Try
r = r.view(numpy.recarray)
barry
On 10/5/07, John Hunter <[EMAIL PROTECTED]> wrote:
> On 9/26/07, Robert Kern <[EMAIL PROTECTED]> wrote:
>
> > Here is the straightforward way:
> >
> > In [15]: import numpy as np
> >
> > In [16]: dt = np.dtype([('foo', int), ('bar', float)])
> >
> > In [17]:
Sorry about the hassle. It was working fine before a reboot. I'll try
to fix it this evening.
barry
On 9/14/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Charles R Harris wrote:
> > I got another buildbot notification and as far as I can tell it has
> > nothing to do with my last commit. The stdio
Is there a reason not to add an argument to fromiter that specifies
the final size of the n-d array? Reading this discussion, I realized
that there are several places in my code where I create 2-D arrays
like this:
arr = N.array([d.data() for d in list_of_data_containers]),
where d.data() returns
he IT people. I'll get back to you ASAP.
thanks,
Barry
On 7/8/07, Albert Strasheim <[EMAIL PROTECTED]> wrote:
> Hello
>
> On Mon, 02 Jul 2007, Barry Wark wrote:
>
> > I have the potential to add OS X Server Intel (64-bit) and OS X Intel
> > (32-bit) to the list, if
Stefan,
No worries. I thought it was something like that. Any thoughts on my
other questions? I'd love to have some ammunition to take to my boss.
Thanks,
Barry
On 7/7/07, stefan <[EMAIL PROTECTED]> wrote:
>
> On Mon, 2 Jul 2007 17:26:15 -0700, "Barry Wark" <[EMAIL
I have the potential to add OS X Server Intel (64-bit) and OS X Intel
(32-bit) to the list, if I can convince my boss that the security risk
(including DOS from compile times) is minimal. I've compiled both
numpy and scipy many times, so I'm not worried about resources for a
single compile/test, bu
Matt,
Yes, I agree. I wasn't coming at so much from the goal of making Pylab
a Matlab clone (as you point out, that's silly, and misses much of the
advantage of Python), but rather from the goal of making interactive
use as efficient as possible. When I fire up ipython -pylab to do some
quick expl
Perhaps we should consider two use cases: interactive use ala Matlab
and larger code bases. In the first case, being able to import * saves
a lot of typing and the namespace polution problem isn't a big deal.
The second use, obviously, benefits from avoiding import *.
Returning to the OP's questio
oops. and it works in test(). sorry. my eyes aren't what they used to be :)
On 1/8/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> On 1/8/07, Barry Wark <[EMAIL PROTECTED]> wrote:
> > I think you want
> > y = x[0,i]
>
> I followed the weave.inli
Keith,
I think you want
y = x[0,i]
Remember that indexing in numpy/scipy is the python way (using []),
not the matlab way (using () )... I've been bitten by the distinction
many times.
Barry
On 1/8/07, Keith Goodman <[EMAIL PROTECTED]> wrote:
> My first weave attempt weaves something to be desi
31 matches
Mail list logo
