On Monday, September 8, 2014 2:38:45 PM UTC+2, simon.ei...@vol.at wrote:
Hi all,
I am not sure if this message went through or not but it seems not.
I just have a quick question.
How easy is it now to compile sage 6.3 on a raspberry pi?
I tried that with version 5.13 and this was
That's the first time I use Sage-Magma interface.
Am I doing something wrong?
Thanks in advance.
(Latest sage beta, magma 2.19-2)
sage: p = next_prime(14)
sage: n = next_prime(13)
sage: k = GF(p)
sage: R.x = PolynomialRing(k)
sage: f = R.irreducible_element(n)
sage: g = R.irreducible_element(n,
On Monday, July 15, 2013 10:14:35 AM UTC+2, Emmanuel Charpentier wrote:
Dear William,
Le lundi 15 juillet 2013 à 00:48 -0700, William Stein a écrit :
On Mon, Jul 15, 2013 at 12:15 AM, Emmanuel Charpentier
emanuel.c...@gmail.com javascript: wrote:
Dear William,
Le dimanche
On Friday, June 21, 2013 6:43:29 PM UTC+2, William stein wrote:
-- Forwarded message --
From: Savin Diana savin...@univ-ovidius.ro javascript:
Date: Thu, Jun 20, 2013 at 2:46 AM
Subject: question - SAGE
To: wst...@uw.edu javascript: wst...@uw.edu javascript:
Dear
Today at some Sage meeting in Paris, we encountered this problem once more
with Sage 4.7.2 vbox image within Windows 7.
The image was correctly (or seemingly correctly) preconfigured with 8000 on
the outside pointing toward 8000 on the inside and into 22.
Once more it was possible to ssh
And I think that the port 8000 was dysfunctional because some service
already listened on that port (I don't have the computer at hand anymore so
cannot check...)
as suggested by this result from a simple google query:
http://superuser.com/questions/360236/why-is-system-listening-on-port-8000
On Wednesday, May 9, 2012 4:40:32 PM UTC+2, Volker Braun wrote:
On Wednesday, May 9, 2012 10:33:22 AM UTC-4, Jean-Pierre Flori wrote:
http://superuser.com/questions/360236/why-is-system-listening-on-port-8000
My money is on the following answer posted on the above ask page
There is some Sage meeting this afternoon in Paris.
I have a Windows 7 installation on my laptop, I'll give a VirtualBox
installation a try, maybe I'll be more lucky than last time.
That was particularly painful to have people ready to try Sage on their
computer at a previous meeting, but being
I think I had the same problem although the VirtualBox port forwarding was
correctly configured and I could not resolve it in the little time I had.
My late conclusion was that maybe the Windows firewall is blocking the
connection (even though it's a local one...) ?
Could you try connecting to
Dear all,
Is there any way to draw easily a 3D multicolor torus with Sage ?
I.e. using parametric_plot3d and an equivalent of adaptive=True,
color=rainbow(60, 'rgbtuple') options ?
Cheers,
JP
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group,
Python was recently updated to not build with OpenSSL support on
Debian, so I cannot build Sage anymore on my Debian Sid.
http://packages.debian.org/changelogs/pool/main/p/python-defaults/python-defaults_2.6.6-14/changelog
python2.6 (2.6.6-9) unstable; urgency=low
* Build without OpenSSL v2
This is now #11561.
On 1 juil, 10:59, Jean-Pierre Flori jpfl...@gmail.com wrote:
Python was recently updated to not build with OpenSSL support on
Debian, so I cannot build Sage anymore on my Debian Sid.
http://packages.debian.org/changelogs/pool/main/p/python-defaults/pyt...
python2.6 (2.6.6
And is nothing but a duplicate of #11447...
Sorry for the noise.
On 1 juil, 11:42, Jean-Pierre Flori jpfl...@gmail.com wrote:
This is now #11561.
On 1 juil, 10:59, Jean-Pierre Flori jpfl...@gmail.com wrote:
Python was recently updated to not build with OpenSSL support on
Debian, so
This is now #11521.
On 16 juin, 17:13, Jean-Pierre Flori jpfl...@gmail.com wrote:
The following piece of code also seems to leak memory.
The problem seems to occur while resolving the action of ZZ on E.
sage: K = GF(155,'t')
sage: a = K.random_element()
sage: while 1:
: E
The following piece of code also seems to leak memory.
The problem seems to occur while resolving the action of ZZ on E.
sage: K = GF(155,'t')
sage: a = K.random_element()
sage: while 1:
: E = EllipticCurve(j=a); P = E.random_point(); 2*P;
On 16 juin, 02:51, Jean-Pierre Flori jpfl
Thanks a lot, I'll have a look at that.
On 15 juin, 14:26, Alastair Irving alastair.irv...@sjc.ox.ac.uk
wrote:
On 14/06/2011 21:58, Jean-Pierre Flori wrote:
On 14 juin, 08:44, Simon Kingsimon.k...@uni-jena.de wrote:
Since sage-nt seems to agree that it is a bug, I opened trac ticket
S the memleak seems to be located within creation or rather coercing
to MPolynomial_libsingular.
Calling gc.collect() whithin the loop seem to fix or are least
attenuate the problem.
However, calling afterwards does not free memory back.
On 15 juin, 14:29, Jean-Pierre Flori jpfl...@gmail.com
I finally found the memleak in different si2sa_* functions in
sage.libs.singular.singular and provided a fix on Trac.
On 15 juin, 21:50, Jean-Pierre Flori jpfl...@gmail.com wrote:
S the memleak seems to be located within creation or rather coercing
to MPolynomial_libsingular.
Calling
But theres another memleak in the roots method of polynomial_zzpex...
On 16 juin, 00:09, Jean-Pierre Flori jpfl...@gmail.com wrote:
I finally found the memleak in different si2sa_* functions in
sage.libs.singular.singular and provided a fix on Trac.
On 15 juin, 21:50, Jean-Pierre Flori jpfl
Which seems to come from list() method.
On 16 juin, 00:09, Jean-Pierre Flori jpfl...@gmail.com wrote:
I finally found the memleak in different si2sa_* functions in
sage.libs.singular.singular and provided a fix on Trac.
On 15 juin, 21:50, Jean-Pierre Flori jpfl...@gmail.com wrote:
S
and from ZZ_pE_c_to_list function
On 16 juin, 01:18, Jean-Pierre Flori jpfl...@gmail.com wrote:
Which seems to come from list() method.
On 16 juin, 00:09, Jean-Pierre Flori jpfl...@gmail.com wrote:
I finally found the memleak in different si2sa_* functions
Ok so the memleak comes from ZZ_pE_to_ZZ_pX in
c_lib/src/ntl_wrap.cpp
It should have been fixed by trac #1092, but has been reverted by
commit 8503.
I'll reopen #1092.
On 16 juin, 02:07, Jean-Pierre Flori jpfl...@gmail.com wrote:
and from ZZ_pE_c_to_list function
On 16 juin, 01:18, Jean-Pierre
this is now 11495
On 16 juin, 02:46, Jean-Pierre Flori jpfl...@gmail.com wrote:
Ok so the memleak comes from ZZ_pE_to_ZZ_pX in
c_lib/src/ntl_wrap.cpp
It should have been fixed by trac #1092, but has been reverted by
commit 8503.
I'll reopen #1092.
On 16 juin, 02:07, Jean-Pierre Flori jpfl
On 14 juin, 08:44, Simon King simon.k...@uni-jena.de wrote:
Since sage-nt seems to agree that it is a bug, I opened trac ticket
#11474.
Good !
About the original memleak, I tried looking at how
EllipticCurves_finite_field (maybe not correct name) are created but
could not find anything fishy,
, Jean-Pierre Flori jpfl...@gmail.com wrote:
Using the following piece of code makes the memory footprint of sage
grow indefinitely:
I just noticed that elliptic curves are instances of
sage.structure.parent.Parent, but violate the unique parent
assumption:
sage: K = GF(150,'t')
sage: j
FYI, the interface to Maxima changed in 4.7.1.alpha0 IIRC, so you
could also try one of the more recent alphas available at:
http://sage.math.washington.edu/home/release/
The things with MARKER are not involved in that new interface.
On 10 juin, 08:34, NigelSmart ni...@cs.bris.ac.uk wrote:
Hi
Dear all,
Using the following piece of code makes the memory footprint of sage
grow indefinitely:
sage: K = GF(150,'t')
sage: j = K.random_element()
sage: while 1:
:E = EllipticCurve(j=j)
:del E
:
This seems to be less dramatic with finite fields of char != 2 and
inexistant
On my computer I get a segfault just doing :
--
| Sage Version 4.7.rc1, Release Date: 2011-04-30 |
| Type notebook() for the GUI, and license() for information.|
sage: R.t = Zq(8,2,'fixed-mod')
sage: 1/t
(t^2 + 1) + (t^2 + 1)*2 + O(2^2)
sage: 1/(t+t^2)
/home/jp/boulot/sage/sage-4.7.rc1/local/lib/libcsage.so(print_backtrace
+0x31)[0x7f3d2a9afdf2]
/home/jp/boulot/sage/sage-4.7.rc1/local/lib/libcsage.so(sigdie+0x14)
[0x7f3d2a9afe24]
I'll take care of it with a fix hopefully.
The value 16 is of course related to FF implementation.
From 16 it uses NTL and GF2X.
There's something nasty occuring in charpoly() or deeper.
On 27 mai, 14:27, Simon King simon.k...@uni-jena.de wrote:
Hi Jean-Pierre,
On 27 Mai, 14:08, Jean-Pierre
Mai, 14:31, Jean-Pierre Flori jpfl...@gmail.com wrote:
I'll take care of it with a fix hopefully.
It turns out that the error occurs in the list() method of a homset,
which starts with
sage: K = GF(116,'a'); L = GF(132,'b')
sage: self = K.Hom(L)
sage: D = self.domain()
sage: C
Adding
(FiniteField_ntl_gf2eself._parent).F.restore()
before calling
cdef GF2X_c r = GF2X_IrredPolyMod(GF2E_rep(self.x),GF2E_modulus())
fixes everything.
Not sure yet why it does not get called before in that situation...
On 27 mai, 15:03, Jean-Pierre Flori jpfl...@gmail.com wrote
and a doctest hoping that
someone with a better understanding of ntl and gf2x will confirm that
it is ok or provide a correct fix.
Cheers,
On 27 mai, 15:22, Jean-Pierre Flori jpfl...@gmail.com wrote:
Adding
(FiniteField_ntl_gf2eself._parent).F.restore()
before calling
cdef GF2X_c r
This is now Trac #11390.
On 27 mai, 15:41, Jean-Pierre Flori jpfl...@gmail.com wrote:
I must admit that I do not know what that method call exactly does,
but calling it resolve the mentionned bug.
Moreover it is called in different places all over the file in a
similar manner so I have
When from sage.calculus.calculus import * is executed, the default
var() function from sage.calculus.var (L4) gets replaced by another
one from sage.symbolic.ring (L506).
There is indeed an import made in sage.calculus.calculus (L370).
However, the behavior of var() changes afterward because
Hi,
Huh. Can I ask where one would import * from sage.calculus.calculus?
In my badly written code.
I wanted to call symbolic_sum which is not reachable by default,
rather than sum when doing some tests.
Cheers,
JP
--
To post to this group, send email to sage-support@googlegroups.com
To
I see. Why not just import that one function, in that case? That is
a very natural thing to do. Only import a whole namespace if you
really have to - it can really mess things up, as you have pointed
out.
I'm aware of that, that piece of code was stupid because I was lazy
when I wrote that.
error:
gcc: gl/lib/strnlen.o: No such file or directory
Replacing patch source code by the latest alpha from
ftp://alpha.gnu.org/gnu/patch/
solved the issue.
On 19 nov, 18:18, Jean-Pierre Flori jpfl...@gmail.com wrote:
Hi,
Everything runs fine now (after fighting with nfs).
I've even built
Hi,
Everything runs fine now (after fighting with nfs).
I've even built the new maxima and ecl, patched everything (one hunk
failed, looked at it, it must be a test which has benn added after
4.5.1 release...)
I'm now trying to run doctests of interfaces/maxima.py.
I'll run it on the Sunblade
Hi,
Can you send me the output of
$ gcc -v
$ gfortran -v
$ command -v gcc
$ cmmand -v gfortran
on your system.
Here it is:
bash-3.00$ gcc -v
Reading specs from /usr/local/packages/gcc3/bin/../lib/gcc/sparc-sun-
solaris2.10/3.4.3/specs
Configured with:
You were right, there is something wrong with the libgfortran file
under SAGE_ROOT/local/lib/ .
It was a symlink to ./../lib/libgfortran.so, strange.
Sage is working with the libraries you posted above. Thanks !
--
To post to this group, send email to sage-support@googlegroups.com
To
Hi,
I unpacked Sage 4.5.1 binaries on Solaris, but when I try to launch
Sage, it complains about missing libgfortran:
ImportError: ld.so.1: python: fatal: libgfortran.so.3: open failed: No
such file or directory
I searched a bit and found something which looks related here:
Thanks for taking care of this !
I was just trying to run tests on Solaris for the next Ecl and Maxima
spgk's...
I'll try downlaoding your lib tomorrow, I'm not at work right now and
am too tired to ssh and etc...
Just one point: we've got a quite recent gcc installed on our Solaris,
I'd say
I can confirm it fixes the bug, I'll add myself as a reviewer on Trac.
If I understand correctly, originally, __copy__ function of
element.pyx calls Expression.__new__(Expression) which should call an
__init__ function (without argument ? but I don't know which ?) so
_gobj is not initialized.
On 7 oct, 01:36, Jason Grout jason-s...@creativetrax.com wrote:
On 10/6/10 9:18 AM, Jean-Pierre Flori wrote:
Sage segfaults when printing a copy of something symbolics :
sage: copy(x)
Unhandled SIGSEGV: A segmentation
Sage segfaults when printing a copy of something symbolics :
sage: copy(x)
Unhandled SIGSEGV: A segmentation fault occurred in Sage.
This probably occurred because a *compiled* component
of Sage has a bug in it (typically accessing
Hi,
Some remarks and questions...
I guess the order you want is 'degrevlex' as Sage's default order for
multivariate polynomial ring and as the name of your functions
suggest.
Am I wrong ?
At present, I did not modify a lot of things.
A few signs, replaced seq[0] by the smallest item of the
Ok, I have finally looked at the comparison functions and exchanging :
cmpval = seq[0].coeff.compare(other.exponent);
by
cmpval = -seq[0].coeff.compare(other.exponent);
in mul::compare_pow (mul.cpp:1265) seems to prevent the above bug from
happening.
It seems to fit better with the change made by
the above patch, that won't be necessary.
Cheers,
On 29 sep, 17:33, Burcin Erocal bur...@erocal.org wrote:
Hi,
On Wed, 29 Sep 2010 07:00:39 -0700 (PDT)
Jean-Pierre Flori jpfl...@gmail.com wrote:
Ok, I have finally looked at the comparison functions and exchanging :
cmpval = seq[0
to do that.
But if you'd better use the above patch, that won't be necessary.
Cheers,
On 29 sep, 17:33, Burcin Erocal bur...@erocal.org wrote:
Hi,
On Wed, 29 Sep 2010 07:00:39 -0700 (PDT)
Jean-Pierre Flori jpfl...@gmail.com wrote:
Ok, I have finally looked at the comparison
On 29 sep, 20:28, Burcin Erocal bur...@erocal.org wrote:
On Wed, 29 Sep 2010 09:48:25 -0700 (PDT)
Jean-Pierre Flori jpfl...@gmail.com wrote:
Maybe it is a good thing to keep the same order as ginac internally
and your more usual ordering for printing.
It is good to keep the ginac
in both git repositories,
but as I was going through the source code, I saw that
numeric::do_print_csrc is defined in GiNaC but not in pynac.
Regards,
On 12 sep, 15:40, Burcin Erocal bur...@erocal.org wrote:
Hi Jean-Pierre,
On Thu, 9 Sep 2010 02:13:27 -0700 (PDT)
Jean-Pierre Flori jpfl
*x or 2*x3*x. Handle with care!
but that function is made to be used that way so...
Moreover replacing it by expair_is_less do not change anything.
However, something fishy is going on here.
On 8 sep, 10:04, Jean-Pierre Flori jpfl...@gmail.com wrote:
On 8 sep, 02:52, kcrisman kcris...@gmail.com
On 8 sep, 02:52, kcrisman kcris...@gmail.com wrote:
On Sep 7, 5:26 pm, Burcin Erocal bur...@erocal.org wrote:
Hi,
Here is a short example to replicate the first error mentioned below:
b = [var('b_%s'%i) for i in range(4)]
precomp = (2^b_2 + 2)*(2^b_1 + 2^(-b_1) + 2^b_1*2^b_0 -
for a such a great piece of
software.
Best regards,
Jean-Pierre Flori
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage
55 matches
Mail list logo
