Indeed, that link is no longer valid. Please visit this one instead:
https://tinyurl.com/yac6cyzg
On Tue, Sep 4, 2018 at 7:48 PM, saad khalid wrote:
> Hello:
>
> The link seems to be broken, I was hoping to take a second look at some of
> the items on the wishlist. is there any way you could re
Hello:
The link seems to be broken, I was hoping to take a second look at some of
the items on the wishlist. is there any way you could repost it? Thank you.
-Saad
On Tuesday, July 24, 2018 at 3:18:32 PM UTC-4, William wrote:
>
> Hi,
>
> I just wrote a short talk that I'm about to give at ICMS
If anyone with topological interests wants a new project, take a look at
incorporating these into Sage:
- Ripser, "a lean C++ code for the computation of Vietoris–Rips persistence
barcodes",http://ripser.org
- Flagser, "Computing homology of directed flag complexes" (based on
ripser), https://
Wow! That did the trick!! Thanks for taking those guesses :)
Best,
Nagesh
On Tue, Sep 4, 2018 at 3:25 PM John H Palmieri
wrote:
> I am not an expert in configure scripts, but it looks to me as though the
> next thing in R's configure script deals with java. Maybe java is broken on
> your system
I am not an expert in configure scripts, but it looks to me as though the
next thing in R's configure script deals with java. Maybe java is broken on
your system badly enough that it halts the configure script? You could try
this:
- copy the flies java and javac from SAGE_ROOT/build/pkgs/r/patc
Hi Dima and John,
I got the libstd++-static installed. I did not use screen this time. I am
not sure how to make "check ...static libraries" to yes. The gcc, g++ and
gfortran are all version 7.3.1 20180303 (Red Hat 7.3.1-5).
I am still getting the error for r. I am attaching the fresh log again j
Note that some interest has recently emerged in renewing
the Sage's interface to Macaulay2, see
- Sage trac ticket 25885
Fixes for outdated Macaulay2 interface
https://trac.sagemath.org/ticket/25885
For other Sage tickets related to Macaulay2, see
https://trac.sagemath.org/query?order=id&des
On Tue, Sep 4, 2018 at 3:02 PM Daniel Krenn wrote:
>
> On 09/04/2018 02:33 PM, Jeroen Demeyer wrote:
> > Let me make one important comment (something that I've said before
> > though): a large part of what makes the current workflow work is not so
> > much Trac itself but our git server and the "g
Keeping in mind that this is still sort of off-topic, in my mind, from
the subject at hand which is allowing merge request submissions from
GitLab, which still get turned into Trac tickets...
On Tue, Sep 4, 2018 at 2:33 PM Jeroen Demeyer wrote:
>
> Let me make one important comment (something tha
On 09/04/2018 02:33 PM, Jeroen Demeyer wrote:
> Let me make one important comment (something that I've said before
> though): a large part of what makes the current workflow work is not so
> much Trac itself but our git server and the "git trac" scripts.
>
> For example, I very much like the fact
On Tue, Sep 4, 2018 at 2:33 PM Jeroen Demeyer wrote:
>
> Let me make one important comment (something that I've said before
> though): a large part of what makes the current workflow work is not so
> much Trac itself but our git server and the "git trac" scripts.
>
> For example, I very much like
Let me make one important comment (something that I've said before
though): a large part of what makes the current workflow work is not so
much Trac itself but our git server and the "git trac" scripts.
For example, I very much like the fact that we have a single git repo
where all pull reques
Hi Dima,
On 2018-09-04, Dima Pasechnik wrote:
> M2 needs a libgc-compatible version of everything, including fflas. That's
> probably why
> two copies etc.
>
>
> M2 is maintained and developed. What is not maintained is Sagemath's M2
> package.
I see. In that case: *IF* someone explains to me ho
On Tue, 4 Sep 2018, 11:57 Simon King, wrote:
> Hi Clement,
>
> On 2018-09-04, Clement Pernet wrote:
> > Le 02/09/2018 à 14:13, Simon King a écrit :
> >>
> /home/king/Projekte/Macaulay2/M2/M2/usr-host/include/fflas-ffpack/fflas/fflas_ftrsm_src.inl:279:27:
> error: ‘openblas_set_num_threads’ was n
Hi Clement,
On 2018-09-04, Clement Pernet wrote:
> Le 02/09/2018 à 14:13, Simon King a écrit :
>> /home/king/Projekte/Macaulay2/M2/M2/usr-host/include/fflas-ffpack/fflas/fflas_ftrsm_src.inl:279:27:
>> error: ‘openblas_set_num_threads’ was not declared in this scope
>> openblas_set_num_thread
Le 02/09/2018 à 14:13, Simon King a écrit :
5. Use Macaulay2
Bad: (a) The experimental spkg is broken, it won't install.
(b) The installation instructions for Ubuntu on the project
pages are rather verbose and require adding obscure
repositories.
(c
On Mon, Sep 3, 2018 at 5:04 PM Jeroen Demeyer wrote:
>
> On 2018-09-03 15:53, Erik Bray wrote:
> > P.S. If anyone has additional comments, positive or negative, on
> > https://trac.sagemath.org/ticket/25914 they would be most appreciated
>
> That doesn't seem the right ticket.
No, that's the righ
FWIW:
Hannes wrote in the Singular forum that he finds it a bad idea to use 64
bit integers, because it would behave differently on 32bit machines. He
also argues that bigint vectors exist in Singular, since there are bigint
*matrices* in Singular; right, but the syntax is different and thus it
is
18 matches
Mail list logo
