[sage-devel] Re: Tuning values needed for MPIR (help needed)

['Bill Hart' via sage-devel]

Apparently if you have a very recent machine, yasm may fail to build the
assembly files for your architecture. To get around this, install the
latest yasm [1] and use MPIR's --with-system-yasm option.

If your system is recent and detects as core2 or k8 or simply x86_64 or
something else obviously out-of-date, when tuning, please also send us a
copy of cat /proc/cpuinfo so we can add support for your processor to MPIR.

Bill.

[1] http://yasm.tortall.net/

On 13 February 2017 at 18:41, Bill Hart  wrote:

> Hi all,
>
> MPIR has been modified recently, and new tuning crossovers have been added.
>
> If you have a machine that you want MPIR to run fast on, we would really
> appreciate help getting tuning values for your machine. Here is how.
>
> git clone https://github.com/wbhart/mpir
> cd mpir
> ./configure --enable-gmpcompat
> make -j4
> make check
> cd tune
> make tune
>
> Please attach the tuning values that are printed to this post. Please
> ensure that the first line is not missing, e.g.
>
>Parameters for ./mpn/x86_64/k8/k10/k102/gmp-mparam.h
>
> as this tells us what machine the values are for.
>
> If the tuning program crashes, or starts to take too long, just send us
> the values you have.
>
> Any help that people can provide is really appreciated.
>
> Note that we DON'T require tuning values for the following arches:
>
> mpn/x86_64/k8/k10/k102
> mpn/x86_64/haswell
>
> If someone already attached values for your arch, no need to supply them
> again.
>
> Bill.
>
>

-- 
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] ComplexField dilog precision bug

[Nathan Dunfield]

FYI, I found a very similar issue with "exp" and "log" for purely imaginary 
numbers:

http://pari.math.u-bordeaux.fr/cgi-bin/bugreport.cgi?bug=1896

Nathan

-- 
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: Sharing my course notes "Logiciels mathématiques"

[Dominique Laurain]

Bonjour Sébastien,
Merci pour le partage.
J'espère que ton travail bénéficiera à quelques enseignants et élèves en 
Belgique et en France.
Je ne peux que te remercier à leur place, car pour ma part je ne fais des 
maths avec SAGE que par pure distraction, et n'utilise pas trop les modules 
Ipython etc.
Dominique

-- 
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: a 7(!) year old (Singular) overflow issue still holds

['Bill Hart' via sage-devel]

I can only answer one of your questions.

On Saturday, 11 February 2017 17:16:29 UTC+1, Jakob Kroeker wrote:
>
> By default, Singular uses 16 bit exponents. But it is perfectly capable of 
>> working with exponents up to 64 bits. That will be slower of course.
>>
>
> How to change this? Is it runtime or compile-time?
>

I believe it can be set at runtime. Hans surely knows how to change it.
 

> Is it transparent for overflow detection?
>

I don't understand the question.
 

>
> I guess it isn't easy for Sage to change the relevant ring upon overflow 
>> to one using 64 bit exponents.
>>
>
> I have no idea;
>
> Jakob
>

-- 
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: Timeouts on patchbots

[Volker Braun]

I think there is also still an issue where openblas internal state becomes 
wedged when interrupting; I disabled multi-threading which made it much 
less frequent but it is not 100% reliable. I'm seeing random issues in 
/abvar/ occasionally on the buildbot.




On Monday, February 13, 2017 at 12:33:14 PM UTC+1, Clemens Heuberger wrote:
>
> It is my subjective observation that timeouts on patchbots have become 
> more 
> frequent. For instance, for ticket 
> https://patchbot.sagemath.org/ticket/22340/ 
> two patchbots failed due to timeout, 
>
> quasar times out with 
>
> sage: ls = J0(46)._calculate_endomorphism_generators() ; ls ## line 213 ## 
>
> ** 
> -- 
> sage -t --long src/sage/modular/abvar/abvar_ambient_jacobian.py  # Timed 
> out 
>
> whereas pbua times out with 
>
> sage: maxima._batch('10003;',batchload=False) ## line 869 ## 
>
> ** 
> -- 
> sage -t --long --warn-long 255.7 src/sage/interfaces/maxima.py  # Timed 
> out 
>
> Do we have any idea how this can happen at all? (Naively, one would 
> believe that 
> either the test works or it does not, I do not understand this quite 
> random 
> behaviour here). 
>
> I know about the recommendation to avoid high system load; but this is 
> somewhat 
> hard to control. On "my" two patchbots, I restrict myself to one or two 
> processes although sometimes I could volunteer more CPU time, but then, 
> timeouts 
> get more likely. 
>
> Can we do anything about that? Usefullness of patchbots is somewhat 
> limited with 
> that many false positives. 
>
> Regards, 
>
> Clemens 
>

-- 
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: Timeouts on patchbots

[Jakob Kroeker]

>
> It is my subjective observation that timeouts on patchbots have become 
> more 
> frequent. For instance, for ticket 
> https://patchbot.sagemath.org/ticket/22340/ 
> two patchbots failed due to timeout, 
>


If I recall correctly, I did hit similar issues when testing sage.
Parallelism or any additional running processes during testing  may have 
negative impact on timings.
(e.g memory cache is shared between several applications) . 


As far as I know for testing the default is to use 3 parallel threads,
see 

https://wiki.sagemath.org/buildbot

Set it to 1 and see if the problem remains, run only one patchbot.
Please report your findings.

I know about the recommendation to avoid high system load; but this is 
> somewhat 
> hard to control. 
>

The best test environment is a separate computer for running patchbot and 
nothing else.


Jakob



Am Montag, 13. Februar 2017 12:33:14 UTC+1 schrieb Clemens Heuberger:
>
> It is my subjective observation that timeouts on patchbots have become 
> more 
> frequent. For instance, for ticket 
> https://patchbot.sagemath.org/ticket/22340/ 
> two patchbots failed due to timeout, 
>
> quasar times out with 
>
> sage: ls = J0(46)._calculate_endomorphism_generators() ; ls ## line 213 ## 
>
> ** 
> -- 
> sage -t --long src/sage/modular/abvar/abvar_ambient_jacobian.py  # Timed 
> out 
>
> whereas pbua times out with 
>
> sage: maxima._batch('10003;',batchload=False) ## line 869 ## 
>
> ** 
> -- 
> sage -t --long --warn-long 255.7 src/sage/interfaces/maxima.py  # Timed 
> out 
>
> Do we have any idea how this can happen at all? (Naively, one would 
> believe that 
> either the test works or it does not, I do not understand this quite 
> random 
> behaviour here). 
>
> I know about the recommendation to avoid high system load; but this is 
> somewhat 
> hard to control. On "my" two patchbots, I restrict myself to one or two 
> processes although sometimes I could volunteer more CPU time, but then, 
> timeouts 
> get more likely. 
>
> Can we do anything about that? Usefullness of patchbots is somewhat 
> limited with 
> that many false positives. 
>
> Regards, 
>
> Clemens 
>

-- 
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] Tuning values needed for MPIR (help needed)

['Bill Hart' via sage-devel]

Hi all,

MPIR has been modified recently, and new tuning crossovers have been added.

If you have a machine that you want MPIR to run fast on, we would really
appreciate help getting tuning values for your machine. Here is how.

git clone https://github.com/wbhart/mpir
cd mpir
./configure --enable-gmpcompat
make -j4
make check
cd tune
make tune

Please attach the tuning values that are printed to this post. Please
ensure that the first line is not missing, e.g.

   Parameters for ./mpn/x86_64/k8/k10/k102/gmp-mparam.h

as this tells us what machine the values are for.

If the tuning program crashes, or starts to take too long, just send us the
values you have.

Any help that people can provide is really appreciated.

Note that we DON'T require tuning values for the following arches:

mpn/x86_64/k8/k10/k102
mpn/x86_64/haswell

If someone already attached values for your arch, no need to supply them
again.

Bill.

-- 
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: Sharing my course notes "Logiciels mathématiques"

[Eric Gourgoulhon]

Hi Sébastien,

Thank you for sharing!

Best regards,

   Eric.


-- 
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: Reporting a bug apparently appearing in sage-7.5 and sage-7.5.1 but not in sage-7.4

[baliza Eyo]

Thanks a lot Ralf Stefan.
Best regards,
Eyo

-- 
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] Sharing my course notes "Logiciels mathématiques"

[Sébastien Labbé]

Dear sage-devel,

During my postdoc at Université de Liège in Belgium, I gave an introduction 
course to math softwares for first year bachelors. It was a new course in 
the department, so I needed to prepare from scratch. I could not use Sage 
as they were unable to install it on the Windows machines. I could not use 
USB SageDebian Live because booting on USB drive was forbidden in the lab. 
Therefore I based the course not on Sage itself but on Python librairies 
(SymPy, Pandas, mpmath, etc.) that are available in Sage but also in the 
Anaconda suite that we manage to install on the machines there. It also 
includes a chapter on Geogebra and another one on Mathematica as that's 
what is mostly used by teachers there. Anyways, I want to share with you my 
notes (in French):

http://www.slabbe.org/Enseignements/MATH2010/notesdecours/

I am using the same CSS file that Nicolas Rougier used in his book "From 
Python to Numpy" [1] released just last month. Thanks to him, it gives a 
nice looking result.

Cheers,

Sébastien Labbé

[1] http://www.labri.fr/perso/nrougier/from-python-to-numpy/

-- 
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] Timeouts on patchbots

[Jeroen Demeyer]

On 2017-02-13 12:33, Clemens Heuberger wrote:

It is my subjective observation that timeouts on patchbots have become more
frequent.


Possible reasons:

1. Python upgrade: https://trac.sagemath.org/ticket/22037#comment:63

2. People are adding more and more doctests everywhere without 
considering the impact on doctest timing.


--
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] Boolean-valued functions and seealso-blocks

[Daniel Krenn]

On 2017-02-13 12:54, Jori Mäntysalo wrote:
> On Mon, 13 Feb 2017, Daniel Krenn wrote:
> 
>> +1 for crosslinks of any kind
> 
> An example: https://trac.sagemath.org/ticket/22377

LGTM

-- 
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] Boolean-valued functions and seealso-blocks

[Jori Mäntysalo]

On Mon, 13 Feb 2017, Daniel Krenn wrote:


+1 for crosslinks of any kind


An example: https://trac.sagemath.org/ticket/22377

--
Jori Mäntysalo

Re: [sage-devel] Boolean-valued functions and seealso-blocks

[Daniel Krenn]

On 2017-02-13 11:29, Jori Mäntysalo wrote:
> For example https://groupprops.subwiki.org/wiki/Solvable_group contains
> lists "Stronger properties" and "Weaker properties".
> 
> What would you think about SEEALSO-blocks of is_* -functions having list
> of nearest stronger and weaker properties? For example
> is_sectionally_complemented() would have something like
> 
> See also:
> 
> - Stronger properties: is_relatively_complemented
> - Weaker properties: is_complemented, is_regular
> 
> or maybe
> 
> - Implied by: is_relatively_complemented
> - Implies: is_complemented, is_regular
> 
> I do not mean the whole list, just those properties that covers or are
> covered by the Boolean property in a poset of property implications.

+1 for crosslinks of any kind

-- 
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] Timeouts on patchbots

[Clemens Heuberger]

It is my subjective observation that timeouts on patchbots have become more
frequent. For instance, for ticket
https://patchbot.sagemath.org/ticket/22340/
two patchbots failed due to timeout,

quasar times out with

sage: ls = J0(46)._calculate_endomorphism_generators() ; ls ## line 213 ##

**
--
sage -t --long src/sage/modular/abvar/abvar_ambient_jacobian.py  # Timed out

whereas pbua times out with

sage: maxima._batch('10003;',batchload=False) ## line 869 ##

**
--
sage -t --long --warn-long 255.7 src/sage/interfaces/maxima.py  # Timed out

Do we have any idea how this can happen at all? (Naively, one would believe that
either the test works or it does not, I do not understand this quite random
behaviour here).

I know about the recommendation to avoid high system load; but this is somewhat
hard to control. On "my" two patchbots, I restrict myself to one or two
processes although sometimes I could volunteer more CPU time, but then, timeouts
get more likely.

Can we do anything about that? Usefullness of patchbots is somewhat limited with
that many false positives.

Regards,

Clemens

-- 
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] Boolean-valued functions and seealso-blocks

[Jeroen Demeyer]

Very general answer: YES to more crosslinks in the documentation.

Corollary: YES to your question.

--
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] Boolean-valued functions and seealso-blocks

[Jori Mäntysalo]

For example https://groupprops.subwiki.org/wiki/Solvable_group contains 
lists "Stronger properties" and "Weaker properties".


What would you think about SEEALSO-blocks of is_* -functions having list 
of nearest stronger and weaker properties? For example 
is_sectionally_complemented() would have something like


See also:

- Stronger properties: is_relatively_complemented
- Weaker properties: is_complemented, is_regular

or maybe

- Implied by: is_relatively_complemented
- Implies: is_complemented, is_regular

I do not mean the whole list, just those properties that covers or are 
covered by the Boolean property in a poset of property implications.


--
Jori Mäntysalo

Re: [sage-devel] ComplexField dilog precision bug

[Jeroen Demeyer]

On 2017-02-13 10:19, John Cremona wrote:

Thanks Jeroen for the very fast diagnosis and fix.


The fix comes from PARI (Karim Belabas to be precise), not me.

--
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] ComplexField dilog precision bug

[John Cremona]

Thanks Jeroen for the very fast diagnosis and fix.

On 13 February 2017 at 08:23, Jeroen Demeyer  wrote:
> On 2017-02-13 09:18, Jeroen Demeyer wrote:
>>
>> Reported upstream:
>> https://pari.math.u-bordeaux.fr/cgi-bin/bugreport.cgi?bug=1895
>
>
> And already fixed (within 30 minutes of reporting it!)
>
> I will add the patch to
> https://trac.sagemath.org/ticket/22276
>
>
> --
> 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.

-- 
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] ComplexField dilog precision bug

[Jeroen Demeyer]

On 2017-02-13 09:18, Jeroen Demeyer wrote:

Reported upstream:
https://pari.math.u-bordeaux.fr/cgi-bin/bugreport.cgi?bug=1895


And already fixed (within 30 minutes of reporting it!)

I will add the patch to
https://trac.sagemath.org/ticket/22276

--
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] ComplexField dilog precision bug

[Jeroen Demeyer]

Reported upstream: 
https://pari.math.u-bordeaux.fr/cgi-bin/bugreport.cgi?bug=1895


--
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.