On 2014-09-03, Simon King wrote:
> Hi Jean-Pierre,
>
> On 2014-09-03, Jean-Pierre Flori wrote:
>> I remember that at some point ./sage -valgrind did not even woork=20
>> anymore
>> I did not read your full post yet but here are some pointers for myself and=
>>=20
>> others:
>> https://groups.
Hi,
In case anybody is curious, there *will* be a Sage booth again at the
Joint Mathematics Meetings in Texas this January, and I'll be at the
booth pretty much the whole time. Help, etc., will be appreciated.
-- William
--
William Stein
Professor of Mathematics
University of Washington
http:
I'm reading the european grant project description on
https://github.com/sagemath/grant-europe/ and I have no idea whether the
software would be free or not. In fact since the project in its current
state is asking more than half of the money for software engineers mostly
for implementing non m
Hi Jean-Pierre,
On 2014-09-03, Jean-Pierre Flori wrote:
> I remember that at some point ./sage -valgrind did not even woork=20
> anymore
> I did not read your full post yet but here are some pointers for myself and=
>=20
> others:
> https://groups.google.com/d/msg/sage-devel/QXy_2KMbP1k/naLbR
Before you do so, can you tell me if that graphviz is the system (local)
install or the one using the experimental Sage spkg (just covering all my
bases here)?
Best,
Travis
On Wednesday, September 3, 2014 11:40:43 AM UTC-7, Sébastien Labbé wrote:
>
> > Time to make a ticket to trac?
>
> Yes! C
> Time to make a ticket to trac?
Yes! Can you open one?
--
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 g
What I am taking away from this discussion is that to ask the author to
make sure the branch merges. That is actually useful to know.
> To be more precise, the commit causing the conflict is
>
>
Hmm, it already didn't merge before that, though...
--
You received this message because you a
On Wednesday, September 3, 2014 3:47:40 PM UTC+1, wstein wrote:
>
> On Wed, Sep 3, 2014 at 1:44 AM, Dima Pasechnik > wrote:
> > On 2014-09-02, William A Stein > wrote:
> >> Hi Sage-devs,
> >>
> >> Is there anybody out there whose interested in (greatly) increasing
> >> the number of optiona
On Wed, 3 Sep 2014 07:40:35 -0700 (PDT)
Volker Braun wrote:
...
> On the commandline you can do
...
> git diff
> develop...trac/u/vinceknight/game_theory__build_capacity_to_solve_matching_games_in_to_sage_
You can also let cgit do this, by crafting the appropriate url [1].
The diff is huge tho
On Wednesday, September 3, 2014 4:57:19 PM UTC+2, Simon King wrote:
>
> Dear all,
>
> I just installed the valgrind spkg, did "make", and then started "./sage
> --valgrind", in order to run a stress test for what I call "biseq"
> (bounded integer sequences) at #15820. Eventually, I want to use
On 2014-09-03 16:57, Simon King wrote:
Is
there a typical reason for "free(): invalid next size (fast)"? Does that
crash message mean that I was writing into non-allocated memory
I would guess so, yes. Most likely a buffer overrun/underrun or writing
into previously-freed memory.
or could it
Dear all,
I just installed the valgrind spkg, did "make", and then started "./sage
--valgrind", in order to run a stress test for what I call "biseq"
(bounded integer sequences) at #15820. Eventually, I want to use biseqs
to implement Gröbner basis computations with a non-commutative F5
algorithm.
On Wed, 3 Sep 2014, Sébastien Labbé wrote:
> sage: view(latex(graphs.PetersenGraph()), tightpage=True)
Stops with
! LaTeX Error: File `preview.sty' not found.
(Why didn't I got this error before?)
Maybe because of view(latex(p)) versus view(p) ? ...too late now to t
On Wed, Sep 3, 2014 at 1:44 AM, Dima Pasechnik wrote:
> On 2014-09-02, William A Stein wrote:
>> Hi Sage-devs,
>>
>> Is there anybody out there whose interested in (greatly) increasing
>> the number of optional gap packages in the optional GAP spkg for Sage?
>
> Probably it would be better to spl
On Tue, Sep 2, 2014 at 11:27 PM, Samuel Lelièvre
wrote:
>
> William Stein wrote:
>
>> Is there anybody out there whose interested in (greatly) increasing
>> the number of optional gap packages in the optional GAP spkg for Sage?
>>
>> This thread has a lot of info about this.In particular, this
If it doesn't merge then it can't be merged, so it doesn't make sense to
ask what would be added if the ticket were merged.
You can do a normal diff between the "devel" branch and the ticket head on
the command line but that'll include changes for every ticket that has been
added since the bra
On Wednesday, September 3, 2014 2:15:25 PM UTC+1, Jori Mantysalo wrote:
>
> Here: http://www.sis.uta.fi/~jm58660/r-3.1.1.p0.log
>
Seems that Sage's version of libgfortran clashes with what ATLAS has been
compiled with. Try a "make distclean && make" to build from a clean slate
if you haven't do
Two separate commands:
cpp -print-search-dirs
ls -al /lib /lib64
In any case, /usr/lib/../lib64/ == /usr/lib64 is already in the library
search path so you don't have to specify it on the
command line.
On Wednesday, September 3, 2014 2:15:25 PM UTC+1, Jori Mantysalo wrote:
>
> On Wed, 3 Sep
On Wednesday, September 3, 2014 9:46:04 AM UTC-4, Jori Mantysalo wrote:
>
> On Wed, 3 Sep 2014, Sébastien Labbé wrote:
>
> > sage: view(latex(graphs.PetersenGraph()), tightpage=True)
>
> Stops with
>
> ! LaTeX Error: File `preview.sty' not found.
>
> (Why didn't I got this error before?)
M
Dear Sage devs,
>From the description of ticket #16577:
Permutation groups used to only handle permutations of 1,..n, and the
methods permute_rows and friends of matrices coped with this with an
ugly and potentially confusing shift by 1. After this ticket,
permutation of 0,...,n-1 are acc
On Wed, 3 Sep 2014, Sébastien Labbé wrote:
sage: view(latex(graphs.PetersenGraph()), tightpage=True)
Stops with
! LaTeX Error: File `preview.sty' not found.
(Why didn't I got this error before?) Anyways, this now works after
installing missing package. ("yum install tex-preview" on Fedora.)
To be more precise, the commit causing the conflict is
commit 40d4cfaa662913ca6795a8a9a598b53cf931809c
Author: drvinceknight
Date: Tue Sep 2 08:49:08 2014 +0100
Deleting files from other tickets
This deletes files which were changed by other tickets.
--
You received this message because
Can you compare the latex output below with yours?
sage: p = Poset( ([1,2,3,4,5],[[1,2],[1,3],[3,4],[2,5],[4,5]]) )
sage: p
Finite poset containing 5 elements
sage: latex(p)
\begin{tikzpicture}[>=latex,line join=bevel,]
%%
\node (node_4) at (22.00bp,157.00bp) [draw,draw=none] {$5$};
\no
On 2014-09-03 15:19, kcrisman wrote:
Not sure whether this or sage-support is more appropriate...
On e.g. http://trac.sagemath.org/ticket/16331 (well, and elsewhere)
there is a branch listed that for some reason doesn't merge cleanly.
Unfortunately, that means I can find no way to look at the di
> Which one are you using (seen in the output of sage -i) ?
Ok, I compared the line number of the traceback. You seem to have version
dot2tex-20120520 installed.
Can you check other examples? Does the following work?
sage: view(latex(graphs.PetersenGraph()))
sage: view(latex(graphs.PetersenGra
Bonjour,
> What version of dot2tex?
> dot2tex-2.8.7.p2 installed version: 20120520
>
I think dot2tex-2.8.7.p2.spkg [1] is not the most recent version of the
dot2tex package. The most recent is dot2tex-20120520.tar.bz2 [2] and it
uses the new git layout structure for s
On Monday, September 1, 2014 2:28:31 PM UTC-4, Emil Widmann wrote:
>
> Thank you. I am still reading posts here and blog posts. Do you think a
> sleak windows version would interfere with you plans of SCM and the goal to
> raise funding for further developement?
>
>>
>>
> > That's the way *I'
Not sure whether this or sage-support is more appropriate...
On e.g. http://trac.sagemath.org/ticket/16331 (well, and elsewhere) there
is a branch listed that for some reason doesn't merge cleanly.
Unfortunately, that means I can find no way to look at the diff visually
all at once for this b
On Wed, 3 Sep 2014, Volker Braun wrote:
It works for me on Fedora 20 without doing anything like that. Can you post the
R build log
Here: http://www.sis.uta.fi/~jm58660/r-3.1.1.p0.log
cpp -print-search-dirsls -al /lib /lib64
I guess you mean -print-search-dirs. It also gives error from -a
On 2014-09-03, Marc Mezzarobba wrote:
> Volker Braun wrote:
>> I would put it in src/doc/en/tutorial as REsT. For example, there is
>> already src/doc/en/tutorial/sagetex.rst
>
> Wouldn't thematic_tutorials/ be a better location? I thought tutorial/
> was for the main tutorial that everyone tryin
Volker Braun wrote:
> I would put it in src/doc/en/tutorial as REsT. For example, there is
> already src/doc/en/tutorial/sagetex.rst
Wouldn't thematic_tutorials/ be a better location? I thought tutorial/
was for the main tutorial that everyone trying to use sage should skim
through...
--
Marc
It works for me on Fedora 20 without doing anything like that. Can you post
the R build log and the output of:
cpp -print-search-dirs
ls -al /lib /lib64
cat /etc/fedora-release
On Wednesday, September 3, 2014 8:05:47 AM UTC+1, Jori Mantysalo wrote:
>
> Usually ./configure && make works on my 64
I would put it in src/doc/en/tutorial as REsT. For example, there is
already src/doc/en/tutorial/sagetex.rst
On Wednesday, September 3, 2014 10:33:21 AM UTC+1, jplab wrote:
>
> Hi,
>
> Recently, I wrote a small tutorial describing how to draw polytopes in
> TikZ using sage. It is currently on
Hello,
One good thing would be to make a post for the Sage blog at
http://sagemath.blogspot.co.uk/ (assuming your not too much anti
google)
Vincent
2014-09-03 10:33 UTC+01:00, jplab :
> Hi,
>
> Recently, I wrote a small tutorial describing how to draw polytopes in TikZ
>
> using sage. It is curr
Hi,
Recently, I wrote a small tutorial describing how to draw polytopes in TikZ
using sage. It is currently on my webpage [1]. It would be better to have
it somewhere in the sage documentation, but where exactly, and in which
format?
Best,
Jean-Philippe
[1] http://page.mi.fu-berlin.de/labbe/p
On Wed, 3 Sep 2014, Francois Bissey wrote:
on Sage I must say LD_LIBRARY_PATH=/usr/lib64/ (or
SAGE_INSTALL_GCC=yes) before make. Otherwise compiling R stops because
of missing fortran library.
Is it only happening with R?
I don't know. Compiling Sage stops when first error occurs; to me th
Hi,
On Wed, Sep 03, 2014 at 09:06:49AM +0100, Martin Albrecht wrote:
> Oh, looks like we never implemented that, but we should (it's straight
> forward). This is now:
>
> http://trac.sagemath.org/ticket/16924
Thanks for the answer and for opening the ticket, i was not sure since
it not a p
Is it only happening with R? That to me looks more like a bug in fedora but
this is
a weird one because if you don't find libgfortran in /usr/lib64 you should also
fail
to find stuff like libstdc++ in the same folder.
François
On 3/09/2014, at 19:05, Jori Mantysalo wrote:
> Usually ./configur
Oh, looks like we never implemented that, but we should (it's straight
forward). This is now:
http://trac.sagemath.org/ticket/16924
Cheers,
Martin
On Tuesday 02 Sep 2014 22:05:29 Thierry wrote:
> Hi,
>
> looking at this ask question :
> http://ask.sagemath.org/question/24024/satisfying-ass
Usually ./configure && make works on my 64-bit Fedora system. However, on
Sage I must say LD_LIBRARY_PATH=/usr/lib64/ (or SAGE_INSTALL_GCC=yes)
before make. Otherwise compiling R stops because of missing fortran
library.
Is this a bug in Fedora or in Sage?
--
Jori Mäntysalo
--
You received t
40 matches
Mail list logo
