The draft agenda is at https://hackmd.io/TtqnUDvPQgaGeej7zR8seA?both#
There is a section for community suggested topics, feel free to join the
conversation and add in topics that need attention.
Past meeting notes can be seen at
https://github.com/BIDS-numpy/docs/tree/master/status_meetings
This week the status meeting will be on Tues Feb 19 at 12:00 PST, not at
the usual time
The draft agenda is at https://hackmd.io/TtqnUDvPQgaGeej7zR8seA?both
Everyone is invited to join.
Matti, Tyler and Stefan
___
NumPy-Discussion mailing list
NumP
Draft agenda: https://hackmd.io/f_e6dnssTkuIC0Pa0TEV6w?view
There is a section for community suggested topics, feel free to join the
conversation and add in topics that need attention.
BIDS team
___
NumPy-Discussion mailing list
NumPy-Discussion@python.
Draft agenda: https://hackmd.io/5AUINxNfS3iN0txIaN32HA?view
There is a section for community suggested topics, feel free to join the
conversation and add in topics that need attention.
BIDS team
___
NumPy-Discussion mailing list
NumPy-Discussion@python.
The draft agenda is at https://hackmd.io/UnnvbPNpSm-gRpbfTK7cmg?both#
There is a section for community suggested topics, feel free to join the
conversation and add in topics that need attention.
The BIDS team
___
NumPy-Discussion mailing list
NumPy-
The draft agenda is at https://hackmd.io/6N3r7yUtSHqUsijC-CEbJA?both
Everyone is invited to join.
Matti, Tyler and Stefan
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
The draft agenda is at https://hackmd.io/D_0X2QCjRpS-ENiFWokc-g?both#
There is a section for community suggested topics, feel free to join the
conversation and add in topics that need attention.
The BIDS team
___
NumPy-Discussion mailing list
NumPy-
The draft agenda is at https://hackmd.io/D_0X2QCjRpS-ENiFWokc-g?both#
There is a section for community suggested topics, feel free to join the
conversation and add in topics that need attention.
The BIDS team
___
NumPy-Discussion mailing list
NumPy
The draft agenda is at https://hackmd.io/Gn1ymjwkRjm9WVY5Cgbwsw?both
This will be our last meeting of 2018.
The BIDS team
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
The draft agenda is at https://hackmd.io/Gn1ymjwkRjm9WVY5Cgbwsw?both
Everyone is invited to join.
Matti, Tyler and Stefan
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
On Tue, 30 Oct 2018 23:56:17 +0100, Hameer Abbasi wrote:
> I meant we should have a calendar that’s possible to subscribe to, and
> in addition announce the agenda here, and that the calendar could
> contain a link to the meeting agenda.
Here you go:
https://calendar.google.com/calendar?cid=YmVya
Hi,
I meant we should have a calendar that’s possible to subscribe to, and in
addition announce the agenda here, and that the calendar could contain a link
to the meeting agenda.
Best Regards,
Hameer Abbasi
> On Tuesday, Oct 30, 2018 at 11:52 PM, Stefan van der Walt
> mailto:stef...@berkeley.
Hi Hameer,
On Tue, 30 Oct 2018 21:24:36 +0100, Hameer Abbasi wrote:
> If I may make a suggestion, it might be nice to create a separate
> calendar and add people to it as needed for better management.
Can you clarify what you want? Do you mean we should not announce the
meeting agenda here, and
I'll try to make it, but can't guarantee.
The last time there was discussion of the structured-array PRs which are
currently held up, and I sort of promised to have a writeup of the issues.
I put up a draft of that here:
https://gist.github.com/ahaldane/6cd44886efb449f9c8d5ea012747323b
Alla
Hello!
If I may make a suggestion, it might be nice to create a separate calendar and
add people to it as needed for better management.
Best Regards,
Hameer Abbasi
> On Tuesday, Oct 30, 2018 at 8:16 PM, Matti Picus (mailto:matti.pi...@gmail.com)> wrote:
>
> The draft agenda is at https://hackm
The draft agenda is at
https://hackmd.io/D3I3CdO2T9ipZ2g5uAChcA?both.
Everyone is invited to join.
Matti, Tyler and Stefan
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/ma
> On Saturday, Oct 27, 2018 at 6:11 AM, Ralf Gommers (mailto:ralf.gomm...@gmail.com)> wrote:
>
>
> On Sat, Oct 27, 2018 at 11:10 AM Stefan van der Walt (mailto:stef...@berkeley.edu)> wrote:
> > On Sat, 27 Oct 2018 10:27:49 +1300, Ralf Gommers wrote:
> > > Just to make sure we're talking about t
> On Saturday, Oct 27, 2018 at 12:10 AM, Stefan van der Walt
> mailto:stef...@berkeley.edu)> wrote:
> On Sat, 27 Oct 2018 10:27:49 +1300, Ralf Gommers wrote:
> > Just to make sure we're talking about the same things here: Stefan, I think
> > with "sparray" you mean "an n-D sparse array implementa
On Sat, Oct 27, 2018 at 11:10 AM Stefan van der Walt
wrote:
> On Sat, 27 Oct 2018 10:27:49 +1300, Ralf Gommers wrote:
> > Just to make sure we're talking about the same things here: Stefan, I
> think
> > with "sparray" you mean "an n-D sparse array implementation that lives in
> > SciPy", nothing
On Sat, 27 Oct 2018 10:27:49 +1300, Ralf Gommers wrote:
> Just to make sure we're talking about the same things here: Stefan, I think
> with "sparray" you mean "an n-D sparse array implementation that lives in
> SciPy", nothing more specific? In that case pydata/sparse is the one
> implementation,
On Sat, Oct 27, 2018 at 6:10 AM Hameer Abbasi
wrote:
> Hi Stefan!
>
> PyData/Sparse is pretty far along, by January or so we should have a
> CSR/CSC replacement that is ND. It needs optimisation in a lot of cases but
> the API is compatible with NumPy and works pretty well already IMO.
>
> PyData
Hi Stefan!
PyData/Sparse is pretty far along, by January or so we should have a CSR/CSC
replacement that is ND. It needs optimisation in a lot of cases but the API is
compatible with NumPy and works pretty well already IMO.
PyData/Sparse is pretty much independent of any changes to scipy.sparse
Hi Hameer,
On Fri, 26 Oct 2018 10:47:09 +0200, Hameer Abbasi wrote:
> The only core functionality dependent on scipy.sparse is matrix
> multiplication and the like. Everything else is for inter-operability.
Thank you for commenting here.
As you know, I am enthusiastic about seeing an `sparray` e
Hi everyone,
Like I said, we just use those to coerce SciPy arrays to native ones for
compatibility. You could remove all those and the package would work fine, as
long as you were using native PyData/Sparse arrays.
The only core functionality dependent on scipy.sparse is matrix multiplication
What exactly would you like Cython wrappers for? Some of the C++ code
in scipy/sparse/sparsetools?
I see you have COO.from_scipy_sparse(x) in some pydata/sparse code paths,
which presumably you'd like to avoid or improve?
On Thu, 25 Oct 2018 at 03:41, Hameer Abbasi
wrote:
> Hi!
>
> Sorry to mis
Hi!
Sorry to miss this week’s meeting.
If I may point out an inaccuracy in the notes: in PyData/Sparse most things are
implemented from the ground up without relying on scipy.sparse. The only part
that does rely on it is `sparse.matmul`, `sparse.dot` and `sparse.tensordot`,
as well as a few co
Hi all,
On Mon, 22 Oct 2018 09:56:37 +0300, Matti Picus wrote:
> We therefore invite you to join us for our weekly calls,
> each **Wednesday from 12:00 to 13:00 Pacific Time**.
>
> Detail of the next meeting (2018-10-24) is given in the agenda
This week's meeting notes are at:
https://github.co
Hi everyone,
The team at BIDS meets once a week to discuss progress, priorities, and
roadblocks. While our priorities are broadly determined by the project
roadmap [0], we would like to provide an opportunity for the community
to give more regular and detailed feedback on our work.
We therefore
28 matches
Mail list logo
