[sage-devel] Re: Finding the right place to edit code

2016-05-09 Thread saad khalid 
So, I've set the besselexpand option to true in the init_code of 
maxima_lib. I was thinking, however, that it would be a good idea to have 
an easy way to turn besselexpand off, so that those who Want the bessel 
version of the output can easily get it. This is where I'm running into 
some issues, I'm not really sure what the best course of action would be. 
First, I was thinking that I could try to edit the code for sum in 
calculus.py and maxima_lib.py. I was thinking that, if I added another 
input variable to symbolic_sum in calculus.py, something like 
besselexpand='true'. So, the function would look like 
symbolic_sum(expression, v, a, b, algorithm='maxima',besselexpand='true')

Then, the value for besselexpand could be fed into the call to 
maxima.sr_sum, and the code could be edited there to let it change the 
init.code to set besselexpand to false. Ideally, I could add code to 
symbolic_sum in calculus.py that lets me change the init.code from there, 
but I don't think that's possible(or rather, I don't know of how to do 
that). Even with this, however, I can't figure out how to let the function 
sr_sum change the init.code to set besselexpand to false from within the 
function. 

Another issue is whether this would even be useful at all, to add this 
option within sum. I'm assuming there are other situations in which the 
bessel function appears as output apart from just the sum function? If 
that's the case, then what I really need is a easy global way to change the 
setting on besselexpand, and then a good place to document it. I'm new to 
this, so I would really appreciate everyones thoughts. 

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Finding the right place to edit code

2016-05-09 Thread saad khalid 
Thank you for your response! Sorry for replying so late, but I was 
wondering, what benefit would there be in leaving the bessel function in 
that form rather than simplifying it? Assuming that setting besselexpand to 
true(thus simplifying it when it can from bessel to trig functions) doesn't 
cause any errors, what reason would there be in leaving it in bessel form 
by default rather than simplifying it by default? 

On Saturday, April 30, 2016 at 3:55:10 PM UTC-5, Nils Bruin wrote:
>
> On Saturday, April 30, 2016 at 11:16:21 AM UTC-7, saad khalid wrote:
>>
>>
>> Specifically, I wanted to try and find where the besselexpand option was 
>> in the source code, so that I could make it default to true globally, 
>> instead of false. However, I have no idea where to look to find where this 
>> option is defined in the source files. If I want to find an option that's 
>> built into sage, it's very easy to type "the_command"?? and have it give me 
>> the source code. However, I haven't had similar luck when trying to edit 
>> global variables or things that are imported from Sympy or Maxima. Is there 
>> an easy way to edit code from them as well? And, my main issue, that file 
>> should I be looking at in order to change the besselexpand option? Thanks 
>> for your patience
>>
>> It can sometimes be a little bit of a goose chase to find which code 
> actually gets executed. In this case, you can trace that "sum" would call 
> the "sum" method on a symbolic expression, and looking at the SR('x').sum 
> implementation you can see that sage.calculus.calculus.symbolic_sum gets 
> called, which leads to sage.interfaces.maxima_lib.
>
> The right place to set the besselexpand option would be in the `init_code` 
> variable there.
>
> I don't know a better way to find these things other than to read code. 
> Note that we're not setting the besselexpand option at all at the moment; 
> we're just going with the default. So searching for it in the source 
> doesn't get you anywhere. (you'd get hits in the maxima source of course, 
> but that's not where you want to change anything for this)
>

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error installing package ecl-15.3.7p0

2016-05-09 Thread Volker Braun 
Do you have libffi-devel installed (however the package is talled on Suse)?


On Monday, May 9, 2016 at 3:08:58 PM UTC+2, Johannes Martin wrote:
>
> Hi,
>
> I cannot compile the source files of sage on
> openSuse Leap 42
>
> Linux linux-noh5 4.1.20-11-default #1 SMP PREEMPT Fri Mar 18 14:42:07 UTC 
> 2016 (0a392b2) x86_
> 64 x86_64 x86_64 GNU/Linux
>
> The corresponding log-file shows the following information
>
> gcc -DECLDIR="\"/home/jmartin/Downloads/sage-7.1/local/lib/ecl-15.3.7\"" 
> -I. -I/home/jmartin/
> Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/build 
> -I/home/jmartin/Downloads/
> sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/src/c -I../ecl/gc 
> -DECL_API -DECL_NO_LEGAC
> Y   -I/home/jmartin/Downloads/sage-7.1/local/include 
> -I/home/jmartin/Downloads/sage-7.1/local
> /include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2  -fPIC -Dlinux -c -o 
> ffi.o ffi.o.c 
>
> /home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/src/c/ffi.d:146:27
> : error: 'FFI_SYSV' undeclared here (not in a function) 
>  {@':cdecl', FFI_SYSV}, 
>   ^ 
> Makefile:81: recipe for target 'ffi.o' failed 
> make[5]: *** [ffi.o] Error 1 
> make[5]: Leaving directory 
> '/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
> 3.7p0/src/build/c' 
> Makefile:109: recipe for target 'libeclmin.a' failed 
> make[4]: *** [libeclmin.a] Error 2 
> make[4]: Leaving directory 
> '/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
> 3.7p0/src/build' 
> Makefile:70: recipe for target 'all' failed 
> make[3]: *** [all] Error 2 
> make[3]: Leaving directory 
> '/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
> 3.7p0/src' 
> Error - Failed to build ECL ... exiting 
>
> real0m22.295s 
> user0m17.176s 
> sys 0m1.792s 
>  
> Error installing package ecl-15.3.7p0 
> 
>
>
>

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] arando back online [was: Re: arando down due to a hardware issue]

2016-05-09 Thread Dima Pasechnik 
Arando is back online. Please feel free to restart the bots there.
Cheers,
Dima


On Friday, February 12, 2016 at 5:33:33 PM UTC, Dima Pasechnik wrote:
>
> Our 32-bit buildbot arando was making noises sounding like a dying fan. 
> I've had to shut down it 
> until I have time to fix it.
>
> Dima
>

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error installing package ecl-15.3.7p0

2016-05-09 Thread Dima Pasechnik 
can we see the complete install.log? (from SAGEROOT/logs/ ) ?

On Monday, May 9, 2016 at 2:08:58 PM UTC+1, Johannes Martin wrote:
>
> Hi,
>
> I cannot compile the source files of sage on
> openSuse Leap 42
>
> Linux linux-noh5 4.1.20-11-default #1 SMP PREEMPT Fri Mar 18 14:42:07 UTC 
> 2016 (0a392b2) x86_
> 64 x86_64 x86_64 GNU/Linux
>
> The corresponding log-file shows the following information
>
> gcc -DECLDIR="\"/home/jmartin/Downloads/sage-7.1/local/lib/ecl-15.3.7\"" 
> -I. -I/home/jmartin/
> Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/build 
> -I/home/jmartin/Downloads/
> sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/src/c -I../ecl/gc 
> -DECL_API -DECL_NO_LEGAC
> Y   -I/home/jmartin/Downloads/sage-7.1/local/include 
> -I/home/jmartin/Downloads/sage-7.1/local
> /include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2  -fPIC -Dlinux -c -o 
> ffi.o ffi.o.c 
>
> /home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/src/c/ffi.d:146:27
> : error: 'FFI_SYSV' undeclared here (not in a function) 
>  {@':cdecl', FFI_SYSV}, 
>   ^ 
> Makefile:81: recipe for target 'ffi.o' failed 
> make[5]: *** [ffi.o] Error 1 
> make[5]: Leaving directory 
> '/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
> 3.7p0/src/build/c' 
> Makefile:109: recipe for target 'libeclmin.a' failed 
> make[4]: *** [libeclmin.a] Error 2 
> make[4]: Leaving directory 
> '/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
> 3.7p0/src/build' 
> Makefile:70: recipe for target 'all' failed 
> make[3]: *** [all] Error 2 
> make[3]: Leaving directory 
> '/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
> 3.7p0/src' 
> Error - Failed to build ECL ... exiting 
>
> real0m22.295s 
> user0m17.176s 
> sys 0m1.792s 
>  
> Error installing package ecl-15.3.7p0 
> 
>
>
>

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: FGb - Gröbner basis computation code

2016-05-09 Thread john_perry_usm 
On Monday, May 9, 2016 at 4:03:49 AM UTC-5, parisse wrote:

>
>
> Le lundi 9 mai 2016 09:18:53 UTC+2, john_perry_usm a écrit :
>>
>>
>> For the homogeneous cyclic-8,
>>
>> > int RT = rtimer; int T=timer; size(sba(k,0,0)); rtimer-RT; timer-T; 
>> 1182
>> 6854
>> 5113
>>
>>
> Strange figures: I get 455 for the first (which is correct for the basis 
> size, while 1182 is wrong), and a little less than 13s for the timings, 
> indeed faster than singular groebner but still 10 to 4* slower than 
> mgb/fgb/giac f4 .. and you must dig into singular documentation!
>

I was doing this late last night & may have typed the ideal wrong. I did 
think the number was wrong, but was too tired to look at it again.

Anyway, Christian replied with this:

yes, the sba() implementation is old and only faster than std() for
>
> dense systems like katsura. We have some students working on this, but
>
> not much effort. There will be an F4 implementation based on GBLA in
>
> Singular sometimes this year. Afterwards we will work on an F5 with
>
> linear algebra.
>
>

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Error installing package ecl-15.3.7p0

2016-05-09 Thread Johannes Martin 
Hi,

I cannot compile the source files of sage on
openSuse Leap 42

Linux linux-noh5 4.1.20-11-default #1 SMP PREEMPT Fri Mar 18 14:42:07 UTC 
2016 (0a392b2) x86_
64 x86_64 x86_64 GNU/Linux

The corresponding log-file shows the following information

gcc -DECLDIR="\"/home/jmartin/Downloads/sage-7.1/local/lib/ecl-15.3.7\"" 
-I. -I/home/jmartin/
Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/build 
-I/home/jmartin/Downloads/
sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/src/c -I../ecl/gc 
-DECL_API -DECL_NO_LEGAC
Y   -I/home/jmartin/Downloads/sage-7.1/local/include 
-I/home/jmartin/Downloads/sage-7.1/local
/include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2  -fPIC -Dlinux -c -o 
ffi.o ffi.o.c 
/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.3.7p0/src/src/c/ffi.d:146:27
: error: 'FFI_SYSV' undeclared here (not in a function) 
 {@':cdecl', FFI_SYSV}, 
  ^ 
Makefile:81: recipe for target 'ffi.o' failed 
make[5]: *** [ffi.o] Error 1 
make[5]: Leaving directory 
'/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
3.7p0/src/build/c' 
Makefile:109: recipe for target 'libeclmin.a' failed 
make[4]: *** [libeclmin.a] Error 2 
make[4]: Leaving directory 
'/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
3.7p0/src/build' 
Makefile:70: recipe for target 'all' failed 
make[3]: *** [all] Error 2 
make[3]: Leaving directory 
'/home/jmartin/Downloads/sage-7.1/local/var/tmp/sage/build/ecl-15.
3.7p0/src' 
Error - Failed to build ECL ... exiting 

real0m22.295s 
user0m17.176s 
sys 0m1.792s 
 
Error installing package ecl-15.3.7p0 



-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] How to implement conversion between LaurentPolynomial and Symbolic rings?

2016-05-09 Thread mmarco 
Right now Sage can convert seamlessly between polynomial rings and symbolic 
ring. I am trying to extend this ability to Laurent polynomial rings.

I have already worked out the conversion to symbolic ring, by defining a 
method called _symbolic_ in the LaurentPolynomial classes. But now I am not 
sure which whould be the right way to proceed. I have considered the 
following options:

1) Modifying the LaurentPolynomialRing to declare a convert_method_name 
during creation, and then implement this convert method in symbolic 
expressions.

2) Modify the element constructor of LaurentPolynomials to check if the 
input is a symbolic expression and then try to construct the polynomial 
from it.

Which is the recommended 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 group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Building Sage on top of GMP

2016-05-09 Thread Jean-Pierre Flori 
On Monday, May 9, 2016 at 11:48:43 AM UTC+2, Jeroen Demeyer wrote:
>
> Did you use the GCC from the system or from Sage? (to verify: does 
> $SAGE_ROOT/local/bin/gcc exist?) 
>

Hum, yes there is.
A 'make clean' was surely not enough to clean up my setup, doing 'make 
distclean' right now. 

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Building Sage on top of GMP

2016-05-09 Thread Jeroen Demeyer 
Did you use the GCC from the system or from Sage? (to verify: does 
$SAGE_ROOT/local/bin/gcc exist?)


--
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Building Sage on top of GMP

2016-05-09 Thread Jean-Pierre Flori 
Hi all,

I was trying to build Sage (trac/develp) on top of GMP using the configure 
flag.
The doc failed to build (unrelated) but when I typed 'make' again it 
decided to rebuild GMP.
Did anyone encounter the same issue (or tried to use GMP)?

Best,
JP

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: FGb - Gröbner basis computation code

2016-05-09 Thread parisse 


Le lundi 9 mai 2016 09:18:53 UTC+2, john_perry_usm a écrit :
>
>
> For the homogeneous cyclic-8,
>
> > int RT = rtimer; int T=timer; size(sba(k,0,0)); rtimer-RT; timer-T; 
> 1182
> 6854
> 5113
>
>
Strange figures: I get 455 for the first (which is correct for the basis 
size, while 1182 is wrong), and a little less than 13s for the timings, 
indeed faster than singular groebner but still 10 to 4* slower than 
mgb/fgb/giac f4 .. and you must dig into singular documentation!
I'm not convinced it's really worth spending time implementing signature 
algorithms anyway (and it seems Roman Pearce and Allan Steel share the same 
feeling), f4 seems good enough for modular computations, and for 
computations over Q with modular algorithms, you can discard useless pairs 
using the first modular run.

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Fwd: [sage-trac-account] BUG Report

2016-05-09 Thread Kannappan Sampath 
Dear Debajyoti:

Thank you for your report. We appreciate it. sage-devel is one place to
report bugs!

=

Dear all:

This is a bug report sent to sage-trac-account.

Regards,
KnS.

-- Forwarded message --
From: Debajyoti Nandi 
Date: Mon, May 9, 2016 at 1:17 AM
Subject: [sage-trac-account] BUG Report
To: sage-trac-acco...@googlegroups.com


Name: Debajyoti Nandi
Preferred Username: deehzee
Contact email: deeh...@gmail.com
Reason: BUG Report

I'm not sure if I'm at right place for reporting this. But here is the
issue:

All links in the "modules" page on docs.sagemath.org are broken.  Below is
the URL which lists the modules (but the links within this page doesn't
work):
http://doc.sagemath.org/html/en/developer/py-modindex.html

Thank you very much and best regards,
Debajyoti.

-- 
-- 
You received this message because you are subscribed to the Google Groups
"sage-trac-account" group.
To post to this group, send email to sage-trac-acco...@googlegroups.com
To unsubscribe from this group, send email to
sage-trac-account+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-trac-account

---
You received this message because you are subscribed to the Google Groups
"sage-trac-account" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to sage-trac-account+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Building binaries...

2016-05-09 Thread Dima Pasechnik 
A different (Linux-only ?) approach to this problem might be to use unshare 
(1) and private mounts.
See https://github.com/mwilliamson/whack

 

On Saturday, May 7, 2016 at 4:46:20 PM UTC+1, William wrote:
>
> On Sat, May 7, 2016 at 2:00 AM, Volker Braun  > wrote: 
> > The sage script in your PATH is outdated: 
> > 
> > $ ./sage -advanced | grep bdist 
> > $ egrep -r bdist src/ 
> > $ 
> > 
> > The way to build binary (relocatable) packages is 
> > https://github.com/sagemath/binary-pkg, which says: 
> > 
> > git clone https://github.com/sagemath/binary-pkg.git 
> > cd binary-pkg 
> > make bdist-sage-linux # If you are on Linux 
> > make bdist-sage-osx   # If you are on OSX 
> > ls dist/  # Built binaries will be in this directory 
>
> I read that github page, but I don't know what binary-pkg actually 
> does.  The docs don't answer my questions. 
>
> For context, I used to (1) build a copy of Sage, (2) possibly 
> customize it, then (3) type 
>
>   ./sage -bdist  
>
> to make a binary from it. 
>
> What does this binary-pkg program do?   Does it package up an existing 
> Sage install?  If so, how do you specify which sage install it 
> packages?   Yes, I read over the yaml file but couldn't figure it out. 
>
>
>  
> I am sad that I can't copy existing sage installs, and I'm now even 
> sadder that I can't type "./sage -bdist" anymore.  Two of the most 
> important things for making sage dev easy for people are gone.   If I 
> had the time, I would make a fork of Sage that restored exactly this 
> behavior then always merge it into sage... 
>  
>
> William 
>
>
> > 
> > 
> > 
> > On Saturday, May 7, 2016 at 2:05:00 AM UTC+2, William Stein wrote: 
> >> 
> >> Either my build is completely hosed, or "sage -bdist" is completely 
> >> broken: 
> >> 
> >> salvus@compute7-us:/projects/sage/sage-develop$ time ./sage -bdist tmp 
> >> sage-run received unknown option: -bdist 
> >> usage: sage [options] 
> >> Try 'sage -h' for more information. 
> >> salvus@compute7-us:/projects/sage/sage-develop$ sage -advanced|grep 
> dist 
> >> Making Sage packages or distributions: 
> >>   -bdist  -- build a binary distribution of Sage 
> >>   -sdist  -- build a source distribution of Sage 
> >> salvus@compute7-us:/projects/sage/sage-develop$ ls 
> >> aclocal.m4  bootstrap  config  config.status  configure.ac 
> >> local  m4README.md  src   VERSION.txt 
> >> autom4te.cache  build  config.log  configure  COPYING.txt 
> >> logs   Makefile  sage   upstream 
> >> 
> >> --- 
> >> 
> >> Also, even if bdist worked, I don't understand the docs.  What's 
> >> ??!?? Where does the bdist actually go??   It used to go in a 
> >> directory SAGE_ROOT/dist, I think. 
> >> 
> >> William 
> >> 
> >> 
> >> On Fri, May 6, 2016 at 2:42 AM, Eric Gourgoulhon  
> >> wrote: 
> >> > As it stands, symbolic calculus is quite severely broken in Sage 7.2: 
> >> > making 
> >> > any assumption on a symbolic variable turns it into an integer. For 
> >> > instance 
> >> > assume(x>0) yields sin(pi*x)=0. This has many undesirable 
> consequences 
> >> > and 
> >> > users will probably complain a lot. Fortunately a fix is provided by 
> the 
> >> > upgrade to the latest version of pynac, which is proposed in #20475. 
> I 
> >> > am 
> >> > reviewing this ticket and IMHO it should be merged before releasing 
> 7.2. 
> >> > 
> >> > -- 
> >> > You received this message because you are subscribed to the Google 
> >> > Groups 
> >> > "sage-release" group. 
> >> > To unsubscribe from this group and stop receiving emails from it, 
> send 
> >> > an 
> >> > email to sage-release...@googlegroups.com. 
> >> > To post to this group, send email to sage-r...@googlegroups.com. 
> >> > Visit this group at https://groups.google.com/group/sage-release. 
> >> > For more options, visit https://groups.google.com/d/optout. 
> >> 
> >> 
> >> 
> >> -- 
> >> William (http://wstein.org) 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "sage-release" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to sage-release...@googlegroups.com . 
> > To post to this group, send email to sage-r...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-release. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> William (http://wstein.org) 
>

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: FGb - Gröbner basis computation code

2016-05-09 Thread john_perry_usm 
Changing the rewrite order greatly improves performance (though not yet to 
an acceptable level). I tested this using Singular's web-interface. For the 
inhomogeneous cyclic-8,

> int RT = rtimer; int T=timer; size(sba(k,0,0)); rtimer-RT; timer-T; 
372
6369
5304

For the homogeneous cyclic-8,

> int RT = rtimer; int T=timer; size(sba(k,0,0)); rtimer-RT; timer-T; 
1182
6854
5113

There's another option for the module order, but I haven't found a setting 
that makes that improve.

I find this curious, as I had the impression from conversations that things 
were much better than this. In fact, I thought they chose the default for 
the second option because experimental evidence suggested it was better, 
but here we see it getting worse. (I can certainly understand why the 
second option would be worse in practice, but then it shouldn't have ended 
up as the default. Then again, one example does not a standard make.) I 
have inquired & will report back.

john perry

On Sunday, May 8, 2016 at 12:56:32 AM UTC-5, parisse wrote:
>
>
>
> Le dimanche 8 mai 2016 04:08:54 UTC+2, john_perry_usm a écrit :
>>
>> What about homogeneous cyclic-8? I'm not sure it will be any better; I'm 
>> just curious.
>>
>> I do know Singular is working on improving aspects of the sba() 
>> implementation, and I'm a bit surprised it's that slow.
>>
>  
> That's indeed better : about 1mn15s (and 635M). But it's slower than 
> groebner (26s, 4M) and much slower than giac (3.6s).
>

-- 
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-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.