On Thu, Jul 31, 2008 at 01:12, Andrew Dalke <[EMAIL PROTECTED]> wrote:
> On Jul 31, 2008, at 3:53 AM, David Cournapeau wrote:
>> You are supposed to run the tests on an installed numpy, not in the
>> sources:
>>
>> import numpy
>> numpy.test(verbose = 10)
>
> Doesn't that make things more cumbersom
On Thu, 2008-07-31 at 08:12 +0200, Andrew Dalke wrote:
> On Jul 31, 2008, at 3:53 AM, David Cournapeau wrote:
> > You are supposed to run the tests on an installed numpy, not in the
> > sources:
> >
> > import numpy
> > numpy.test(verbose = 10)
>
> Doesn't that make things more cumbersome to test?
A Thursday 31 July 2008, Matt Knox escrigué:
> While on the topic of FAME... being a financial analyst, I really am
> quite fond of the multitude of quarterly frequencies we have in the
> timeseries package (with different year end points) because they are
> very useful when doing things like "cale
On Jul 31, 2008, at 3:53 AM, David Cournapeau wrote:
> You are supposed to run the tests on an installed numpy, not in the
> sources:
>
> import numpy
> numpy.test(verbose = 10)
Doesn't that make things more cumbersome to test? That is, if I were
to make a change I would need to:
- python se
On Jul 31, 2008, at 4:21 AM, Alan McIntyre wrote:
> They actually do two different things; numpy.test() runs test for all
> of numpy, and numpy.testing.test() runs tests for numpy.testing only.
> There are similar functions in numpy.lib, numpy.core, etc.
Really? This is the code from numpy/__init
>> >> If it's really just weekdays why not call it that instead of using a
>> >> term like business days that (quite confusingly) suggests holidays
>> >> are handled properly?
>>
>> Well, we were adopting the name from the TimeSeries package. Perhaps
>> the authors can answer this better than me.
On Wed, Jul 30, 2008 at 8:19 PM, Andrew Dalke <[EMAIL PROTECTED]> wrote:
> numpy defines
>
> numpy.test
> numpy.bench
>
> and
>
> numpy.testing.test
>
> The two 'test's use the same implementation. This is a likely
> unneeded duplication and one should be removed. The choice depends on
> if peo
On Thu, 2008-07-31 at 02:07 +0200, Andrew Dalke wrote:
> On Jul 30, 2008, at 10:59 PM, Stéfan van der Walt wrote:
> > I.e. most people don't start up NumPy all the time -- they import
> > NumPy, and then do some calculations, which typically take longer than
> > the import time.
>
> Is that intera
Hello,
I am very pleased to announce that Traits 3.0 has just been released!
All Traits projects have been registered with PyPi (aka The Cheeseshop)
and each project's listing on PyPi currently includes a source
tarball. In the near future, we will also upload binary eggs for
Windows and Mac OS
On Jul 30, 2008, at 10:51 PM, Alan McIntyre wrote:
> I suppose it's necessary for providing the test() and bench()
> functions in subpackages, but I that isn't a good reason to impose
> upon all users the time required to set up numpy.testing.
I just posted this in my reply to Stéfan, but I'll say
On Jul 30, 2008, at 10:59 PM, Stéfan van der Walt wrote:
> I.e. most people don't start up NumPy all the time -- they import
> NumPy, and then do some calculations, which typically take longer than
> the import time.
Is that interactively, or is that through programs?
> For a benefit of 0.03s, I
Howdy (esp. Alan McIntyre):
I've been using numpy's decorators a lot, many thanks to Matthew B and
Alan for this code! Here's a snippet to auto-generate labeling
decorators that might come in handy to avoid repetition in creating
decos like @slow & friends. It's doctested as well as validating
t
Hi All,
Using:
Python 2.5.2,
f2py ver 2_4422,
gfortran --version GNU Fortran (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
on kubuntu 8.04 (Hardy) up-to-date on a Thinkpad T60.
After building and using an f2py-generated lib for a while with this
command:
f2py --opt="-O3" -c -m fd_rrt1d --fcompiler=g
2008/7/30 Alan McIntyre <[EMAIL PROTECTED]>:
> On Wed, Jul 30, 2008 at 5:01 PM, Stéfan van der Walt <[EMAIL PROTECTED]>
> wrote:
>> If others agree, could we suppress the output of skipped tests unless
>> specifically requested? They clutter the output, and makes it more
>> difficult to see which
On Wed, Jul 30, 2008 at 5:01 PM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> If others agree, could we suppress the output of skipped tests unless
> specifically requested? They clutter the output, and makes it more
> difficult to see which "real" tests fail.
I'll see if there's some easy wa
Alan,
If others agree, could we suppress the output of skipped tests unless
specifically requested? They clutter the output, and makes it more
difficult to see which "real" tests fail.
Stéfan
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
2008/7/30 Andrew Dalke <[EMAIL PROTECTED]>:
> Based on those results I've been digging into the code trying to
> figure out why numpy imports so many files, and at the same time I've
> been trying to guess at the use case Robert Kern regards as typical
> when he wrote:
>
> Your use case isn't s
> oops. It is ATLAS. I was able to run with a nonoptimized lapack.
Just to confirm, it also works for me when I use Netlib BLAS instead
of ATLAS.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/num
On Wed, Jul 30, 2008 at 4:12 PM, Andrew Dalke <[EMAIL PROTECTED]> wrote:
> 4) numpy.testing takes 0.041 seconds to import. The text I quoted
> above says that it's a numpy requirement that 'testing' always be
> imported, even though I'm hard pressed to figure out why that's
> important.
I suppos
On Jul 4, 2008, at 2:22 PM, Andrew Dalke wrote:
> [josiah:numpy/build/lib.macosx-10.3-fat-2.5] dalke% time python -c
> 'pass'
> 0.015u 0.042s 0:00.06 83.3% 0+0k 0+0io 0pf+0w
> [josiah:numpy/build/lib.macosx-10.3-fat-2.5] dalke% time python -c
> 'import numpy'
> 0.084u 0.231s 0:00.33 93.9%
Yes this all makes a lot of sense. I would propose changing the name
from business days to weekdays though. Does anyone object wih that?
On 7/30/08, Ivan Vilata i Balaguer <[EMAIL PROTECTED]> wrote:
> Tom Denniston (el 2008-07-30 a les 13:12:45 -0500) va dir::
>
> > If it's really just weekdays
Tom Denniston (el 2008-07-30 a les 13:12:45 -0500) va dir::
> If it's really just weekdays why not call it that instead of using a
> term like business days that (quite confusingly) suggests holidays are
> handled properly?
Yes, that may be a better term. I guess we didn't choose that because
we
A Wednesday 30 July 2008, Tom Denniston escrigué:
> If it's really just weekdays why not call it that instead of using a
> term like business days that (quite confusingly) suggests holidays
> are handled properly?
Well, we were adopting the name from the TimeSeries package. Perhaps
the authors c
Hi,
After several weeks of gathering and pondering through very valuable
feedback, we are happy to release the third (and final?) version of the
proposal for the addition of the date/time types in NumPy.
The bad news is that, due to a series of circumstances (apparently not
related on how this
If it's really just weekdays why not call it that instead of using a
term like business days that (quite confusingly) suggests holidays are
handled properly?
Also, I view the timezone and holiday issues as totally seperate. I
would definately NOT recommend basing holidays on a timezone because
ho
A Wednesday 30 July 2008, Tom Denniston escrigué:
> When people are refering to busienss days are you talking about
> weekdays or are you saying weekday non-holidays?
Plain weekdays. Taking in account holidays for all the world round
would be certainly much more complex than timezones, which nei
A Wednesday 30 July 2008, Pierre GM escrigué:
> Which brings me to another question:
> datetime64 and timedelta64 are just dtypes, therefore they don't
> impose any restriction (in terms of uniqueness of elements, ordering
> of the elements...) on the underlying ndarray, right ?
That's right. Per
When people are refering to busienss days are you talking about
weekdays or are you saying weekday non-holidays?
On 7/30/08, Francesc Alted <[EMAIL PROTECTED]> wrote:
> A Wednesday 30 July 2008, Pierre GM escrigué:
> > > > Now, what format do you consider for this reference ?
> > >
> > > Whatever
On Wednesday 30 July 2008 13:16:25 Francesc Alted wrote:
> A Wednesday 30 July 2008, Pierre GM escrigué:
> > It's just that I have trouble understanding the
> > meaning of something like
> > t2 = numpy.ones(5, dtype="datetime64[s]")
> >
> > That's five times one second after the epoch, right ? Bu
A Wednesday 30 July 2008, Pierre GM escrigué:
> > > Now, what format do you consider for this reference ?
> >
> > Whatever that can be converted into a datetime64 scalar. Some
> > examples:
> >
> > ref = '2001-04-01'
> > ref = datetime.datetime(2001, 4, 1)
>
> Er, should I see ref as having a 'day
On Wed, Jul 30, 2008 at 12:35 PM, Francesc Alted <[EMAIL PROTECTED]>wrote:
> A Wednesday 30 July 2008, Pierre GM escrigué:
> > In my mind, .tounit(*args) should be available for both relative
> > (timedeltas) and absolute (datetime) times.
>
> Well, what we are proposing is that the conversion tim
A Wednesday 30 July 2008, Pierre GM escrigué:
> On Wednesday 30 July 2008 06:35:32 Francesc Alted wrote:
> > A Wednesday 30 July 2008, Ivan Vilata i Balaguer escrigué:
> > > Pierre GM (el 2008-07-29 a les 15:47:52 -0400) va dir::
> > > > On Tuesday 29 July 2008 15:14:13 Ivan Vilata i Balaguer wrote
On Wednesday 30 July 2008 06:35:32 Francesc Alted wrote:
> A Wednesday 30 July 2008, Ivan Vilata i Balaguer escrigué:
> > Pierre GM (el 2008-07-29 a les 15:47:52 -0400) va dir::
> > > On Tuesday 29 July 2008 15:14:13 Ivan Vilata i Balaguer wrote:
> > > > Pierre GM (el 2008-07-29 a les 12:38:19 -040
If you read the cov function documentation you'll see that if a second vector
is given, it joins the 2 into one matrix and calculate the covariance of it. In
your case, you are looking for the off-diagonal elements.
Nadav.
-הודעה מקורית-
מאת: [EMAIL PROTECTED] בשם Keith Goodman
נשלח:
On Tue, Jul 29, 2008 at 9:10 PM, Anthony Kong
<[EMAIL PROTECTED]> wrote:
> I am trying out the example here
> (http://www.scipy.org/Numpy_Example_List_With_Doc#cov)
>
>
from numpy import *
> ...
T = array([1.3, 4.5, 2.8, 3.9])
P = array([2.7, 8.7, 4.7, 8.2])
cov(T,P)
>
> The ans
Hi there,
I have a question concerning numpy.memmap.
I'm working with a binary format, consisting of a header of certain size
(1024 byte) in the beginning and a 2d-float32 array afterwards. I would
like to open the array-part using a memmap-object using
mm =
n.memmap("test.dat",dtype=n.float32,
A Wednesday 30 July 2008, Ivan Vilata i Balaguer escrigué:
> Pierre GM (el 2008-07-29 a les 15:47:52 -0400) va dir::
> > On Tuesday 29 July 2008 15:14:13 Ivan Vilata i Balaguer wrote:
> > > Pierre GM (el 2008-07-29 a les 12:38:19 -0400) va dir::
> > > > > Relative time versus relative time
> > > >
Pierre GM (el 2008-07-29 a les 15:47:52 -0400) va dir::
> On Tuesday 29 July 2008 15:14:13 Ivan Vilata i Balaguer wrote:
> > Pierre GM (el 2008-07-29 a les 12:38:19 -0400) va dir::
> > > > Relative time versus relative time
> > > > --
> > > >
> > > > This case would
Thanks for all your comments. It's definitely time to read a good book now.
My original problem is a convolution of two complex functions given as samples
over quite different intervals with different n. The imaginary part of one of
these functions is Lorentz-shaped. I thought it might be good
39 matches
Mail list logo
