On Sunday, June 2, 2013 7:58:05 PM UTC+1, tdumont wrote:
> -> In that case, I recall that the main problem will be actually to
> *create* the CSR structure: you want to enter non zero coefficients
> (i,j)-> a_ij in any order. The mechanism used by by scipy (and thus
> sage) is very very slow...
Le 02/06/2013 19:28, Volker Braun a écrit :
On Sunday, June 2, 2013 9:01:01 AM UTC+1, Charles Bouillaguet wrote:
There is a presumably standard sparse-blas API :
http://math.nist.gov/spblas/
Yes, though it doesn't seem to mandate any matrix storage format. So
apparently you can't let
On Sunday, June 2, 2013 9:01:01 AM UTC+1, Charles Bouillaguet wrote:
> There is a presumably standard sparse-blas API :
> http://math.nist.gov/spblas/
>
Yes, though it doesn't seem to mandate any matrix storage format. So
apparently you can't let it run on a given chunk of memory but you need
On Sunday, June 2, 2013 10:01:01 AM UTC+2, Charles Bouillaguet wrote:
> http://docs.scipy.org/doc/scipy/reference/sparse.linalg.html
>
yes, i just wanted to point to that. this is the list of implementations,
i.e. CSC/CSR (compressed sparse columns or rows) is already there.
http://docs.scip
Hey,
Could we at least get the hacked sage-sync-build into 5.10? The combinat
queue has a few patch which create new cython files that replace python
files (i.e. cythonizes them) which requires the sync-build to be run when
people are moving ahead of those patches. Rebuilding all cython files
leif wrote:
leif wrote:
4) Minimally adapt sage-sync-build.py to reflect the (hard-coded) change
by #14570. [May be easy as well, but potentially unsafe.]
Even that turns out to be non-trivial, AFAICS, i.e., the whole strategy
would have to get changed, as opposed to just some file / director
I have emailed Harald about it.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-
@Veronica: Hello and welcome. I look forward to your contributions!
On Sunday, June 2, 2013 6:19:13 AM UTC+8, mmarco wrote:
>
> Welcome on board, Veronica.
>
> Please keep us up to date to your progress. I am your mentor, but i am
> sure the rest of the sage community would like to have you invo
On Sat, Jun 1, 2013 at 3:55 AM, leif wrote:
> John H Palmieri wrote:
>>
>> On Thursday, May 30, 2013 9:57:07 PM UTC-7, leif wrote:
>>
>> leif wrote:
>> > Looks like reinstalling the Sage library spkg would meanwhile also
>> > trigger the rebuild of *all* extension modules; not sure s
On Jun 2, 2013, at 9:20 AM, Dima Pasechnik wrote:
> On 2013-06-01, Volker Braun wrote:
> [...]
>>
>> On a related note, sparse matrices in Sage suck (dictionary of keys).
>> Sparse matrices in LELA only suck slightly less (list of lists). For fast
>> computation one should implement compressed
On 2013-06-01, Volker Braun wrote:
[...]
>
> On a related note, sparse matrices in Sage suck (dictionary of keys).
> Sparse matrices in LELA only suck slightly less (list of lists). For fast
> computation one should implement compressed sparse row/column, I think.
IMHO one needs to create a fra
11 matches
Mail list logo