On Wed, Jul 21, 2010 at 8:24 PM, Charles R Harris
wrote:
>
> On Wed, Jul 21, 2010 at 5:44 PM, Keith Goodman wrote:
>> Can someone confirm that the copy in np.linalg.lstsq
>>
>> bstar[:b.shape[0],:n_rhs] = b.copy()
>>
>> is not needed? I'm assuming that ndarray.__setitem__ never gives a
>> view o
On Wed, Jul 21, 2010 at 5:44 PM, Keith Goodman wrote:
> On Wed, Jul 21, 2010 at 4:35 PM, Skipper Seabold
> wrote:
> > On Tue, Jul 20, 2010 at 10:24 PM, Keith Goodman
> wrote:
> >> Good point. Looks like we can get rid of 2 copies! I didn't get rid of
> >> the second copy but I did cut things do
On Wed, Jul 21, 2010 at 4:35 PM, Skipper Seabold wrote:
> On Tue, Jul 20, 2010 at 10:24 PM, Keith Goodman wrote:
>> Good point. Looks like we can get rid of 2 copies! I didn't get rid of
>> the second copy but I did cut things down just to see what the timing
>> was like. I also threw out the abi
On Wed, Jul 21, 2010 at 7:25 PM, David Warde-Farley wrote:
> On 2010-07-20, at 10:16 PM, Skipper Seabold wrote:
>
>> Out of curiosity, is there an explicit way to check if these share memory?
>
>
> You could do the exact calculations (I think) but this isn't actually
> implemented in NumPy, thoug
On Tue, Jul 20, 2010 at 10:24 PM, Keith Goodman wrote:
> Good point. Looks like we can get rid of 2 copies! I didn't get rid of
> the second copy but I did cut things down just to see what the timing
> was like. I also threw out the ability to handle complex numbers (only
> saves an if iscomplex s
On 2010-07-20, at 10:16 PM, Skipper Seabold wrote:
> Out of curiosity, is there an explicit way to check if these share memory?
You could do the exact calculations (I think) but this isn't actually
implemented in NumPy, though np.may_share_memory is a conservative test for it
that will err on
On Tue, Jul 20, 2010 at 7:16 PM, Skipper Seabold wrote:
> On Tue, Jul 20, 2010 at 10:12 PM, Keith Goodman wrote:
>> On Tue, Jul 20, 2010 at 6:35 PM, Keith Goodman wrote:
>>> On Mon, Jul 19, 2010 at 10:08 PM, Charles R Harris
>>> wrote:
On Mon, Jul 19, 2010 at 9:40 PM, Keith Goodm
On Tue, Jul 20, 2010 at 10:12 PM, Keith Goodman wrote:
> On Tue, Jul 20, 2010 at 6:35 PM, Keith Goodman wrote:
>> On Mon, Jul 19, 2010 at 10:08 PM, Charles R Harris
>> wrote:
>>>
>>>
>>> On Mon, Jul 19, 2010 at 9:40 PM, Keith Goodman wrote:
On Mon, Jul 19, 2010 at 8:27 PM, Charles R H
On Tue, Jul 20, 2010 at 6:35 PM, Keith Goodman wrote:
> On Mon, Jul 19, 2010 at 10:08 PM, Charles R Harris
> wrote:
>>
>>
>> On Mon, Jul 19, 2010 at 9:40 PM, Keith Goodman wrote:
>>>
>>> On Mon, Jul 19, 2010 at 8:27 PM, Charles R Harris
>>> wrote:
>>> >
>>> >
>>> > On Mon, Jul 19, 2010 at 9:02
On Mon, Jul 19, 2010 at 10:08 PM, Charles R Harris
wrote:
>
>
> On Mon, Jul 19, 2010 at 9:40 PM, Keith Goodman wrote:
>>
>> On Mon, Jul 19, 2010 at 8:27 PM, Charles R Harris
>> wrote:
>> >
>> >
>> > On Mon, Jul 19, 2010 at 9:02 PM, Keith Goodman
>> > wrote:
>> >>
>> >> On Mon, Jul 19, 2010 at 6
On Tue, Jul 20, 2010 at 11:23 AM, Charles R Harris
wrote:
>
>
> On Tue, Jul 20, 2010 at 8:32 AM, Skipper Seabold
> wrote:
>>
>> On Tue, Jul 20, 2010 at 1:08 AM, Charles R Harris
>> wrote:
>> >
>> >
>> > On Mon, Jul 19, 2010 at 9:40 PM, Keith Goodman
>> > wrote:
>> >>
>> >> On Mon, Jul 19, 2010
On Tue, Jul 20, 2010 at 8:32 AM, Skipper Seabold wrote:
> On Tue, Jul 20, 2010 at 1:08 AM, Charles R Harris
> wrote:
> >
> >
> > On Mon, Jul 19, 2010 at 9:40 PM, Keith Goodman
> wrote:
> >>
> >> On Mon, Jul 19, 2010 at 8:27 PM, Charles R Harris
> >> wrote:
> >> >
> >> >
> >> > On Mon, Jul 19, 2
On Tue, Jul 20, 2010 at 1:08 AM, Charles R Harris
wrote:
>
>
> On Mon, Jul 19, 2010 at 9:40 PM, Keith Goodman wrote:
>>
>> On Mon, Jul 19, 2010 at 8:27 PM, Charles R Harris
>> wrote:
>> >
>> >
>> > On Mon, Jul 19, 2010 at 9:02 PM, Keith Goodman
>> > wrote:
>> >>
>> >> On Mon, Jul 19, 2010 at 6:
On Mon, Jul 19, 2010 at 9:40 PM, Keith Goodman wrote:
> On Mon, Jul 19, 2010 at 8:27 PM, Charles R Harris
> wrote:
> >
> >
> > On Mon, Jul 19, 2010 at 9:02 PM, Keith Goodman
> wrote:
> >>
> >> On Mon, Jul 19, 2010 at 6:53 PM, Joshua Holbrook
> >> wrote:
> >> > On Mon, Jul 19, 2010 at 5:50 PM,
On Mon, Jul 19, 2010 at 8:27 PM, Charles R Harris
wrote:
>
>
> On Mon, Jul 19, 2010 at 9:02 PM, Keith Goodman wrote:
>>
>> On Mon, Jul 19, 2010 at 6:53 PM, Joshua Holbrook
>> wrote:
>> > On Mon, Jul 19, 2010 at 5:50 PM, Charles R Harris
>> > wrote:
>> >> Hi All,
>> >>
>> >> I'm thinking about a
On Mon, Jul 19, 2010 at 9:02 PM, Keith Goodman wrote:
> On Mon, Jul 19, 2010 at 6:53 PM, Joshua Holbrook
> wrote:
> > On Mon, Jul 19, 2010 at 5:50 PM, Charles R Harris
> > wrote:
> >> Hi All,
> >>
> >> I'm thinking about adding some functionality to lstsq because I find
> myself
> >> doing the
On Mon, Jul 19, 2010 at 9:02 PM, Keith Goodman wrote:
> On Mon, Jul 19, 2010 at 6:53 PM, Joshua Holbrook
> wrote:
> > On Mon, Jul 19, 2010 at 5:50 PM, Charles R Harris
> > wrote:
> >> Hi All,
> >>
> >> I'm thinking about adding some functionality to lstsq because I find
> myself
> >> doing the
On Mon, Jul 19, 2010 at 6:53 PM, Joshua Holbrook
wrote:
> On Mon, Jul 19, 2010 at 5:50 PM, Charles R Harris
> wrote:
>> Hi All,
>>
>> I'm thinking about adding some functionality to lstsq because I find myself
>> doing the same fixes over and over. List follows.
>>
>> Add weights so data points c
On Mon, Jul 19, 2010 at 5:50 PM, Charles R Harris
wrote:
> Hi All,
>
> I'm thinking about adding some functionality to lstsq because I find myself
> doing the same fixes over and over. List follows.
>
> Add weights so data points can be weighted.
> Use column scaling so condition numbers make more
Hi All,
I'm thinking about adding some functionality to lstsq because I find myself
doing the same fixes over and over. List follows.
1. Add weights so data points can be weighted.
2. Use column scaling so condition numbers make more sense.
3. Compute covariance approximation?
Unfortun
20 matches
Mail list logo
