Re: [sage-devel] Matplotlib plotting style 'classic' hardcoded to Sage
On Monday, July 9, 2018 at 10:40:03 AM UTC+9, François Bissey wrote: > > I am sorry to have introduced that in the upgrade to matplotlib 2.1. > Hardcoding > was easier than setting the style to classic for every calls for the > documentation. > The reports I had was that the default style from 2.1 onwards made the > documentation > plots look ugly. I looked through the documentation rebuilt with the current default style. It still looks great, and I find nothing ugly :-) -- 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] Matplotlib plotting style 'classic' hardcoded to Sage
Yeah, I found one thing that looks ugly on my machine: In the 'classic' style: In the current default style: -- 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] Matplotlib plotting style 'classic' hardcoded to Sage
Generally equations look better with the font choices in the “classic” style which was the default before matplotlib-2. > On 9/07/2018, at 20:34, Kwankyu Lee wrote: > > Yeah, I found one thing that looks ugly on my machine: > > In the 'classic' style: > > > In the current default style: > > > > > > > > > > > > > -- > 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] Re: Trac branch trouble?
On Mon, Jul 9, 2018 at 8:33 AM Simon King wrote: > > On 2018-07-08, Volker Braun wrote: > > The commit SHA1 is immutable, but the branch can evolve over time. > > There is a "commit" field on trac, as you know. So, why is there a > pressing need to replace the "branch" field by the content of the "commit" > field, when this makes it impossible to "git trac checkout"? It's surprising, but it does make sense. A branch can continue to move around even if at some point it was merged into the main branch. Having a named branch in a ticket that has been fixed can be confusing because if someone continues to push to that same branch, it longer represents the code that was actually merged for that ticket. In fact, I am trying to encourage people to delete their upstream branches once a ticket has been closed: https://groups.google.com/d/msg/sage-devel/LuYAxDJ7Nlo/pJnAY82LBQAJ This is why I'm a bit wary of the "git trac" command--while it is certainly convenient it should not be used as the end-all-be-all interface to git. If you know the name of the branch you want to check out and it hasn't been deleted, nothing is stopping anyone from running `git checkout `. > > On Sunday, July 8, 2018 at 8:41:56 PM UTC+2, Dima Pasechnik wrote: > >> > >> maybe this should be fixed - is there a pressing need to replace the > >> corresponding metadata on the ticket? > > > > -- > 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] Matplotlib plotting style 'classic' hardcoded to Sage
Consulting https://matplotlib.org/users/dflt_style_changes.html we may keep specifically only the math font of the classic style by: mpl.rcParams['mathtext.fontset'] = 'cm' mpl.rcParams['mathtext.rm'] = 'serif' and adopt the default matplotlib-2 style generally. I assume that the matplotlib-2 style is an improvement over the classic style in general. -- 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: NTL 11.2.0
These are ery interesting timings. In the region above the diagonal (and sufficiently far to the right - degree 12 I think), I believe we still use the SSA algorithm directly for polynomial arithmetic over Z. So your timings indicate that you are actually beating the Flint FFT directly. This is quite remarkable given the work that went into it on in Flint (it was already significantly faster than the FFT's in Magma and GMP, and faster than the Gaudry, Kruppa, Zimmermann FFT. I congratulate you on what must be some truly impressive work. (I keep telling whoever will listen that we should spend some time trying to catch back up with the NTL benchmarks you have been publishing, but there seems to be little opportunity to work on such projects these days, and there seems to be a real shortage of young people taking on challenges like this. We do know what needs to be done. It's more an issue of finding people who could actually carry out the work.) Anyway, thanks again for the impressive work you've been doing on NTL, for making your code Open Source, so that we can all learn from it, and for the benchmarks you have been making available! Bill. On Saturday, 7 July 2018 20:39:59 UTC+2, Victor Shoup wrote: > > I just released NTL 11.2.0 at http://www.shoup.net/ntl > > The main change is a new and improved implementation of the > Schoenhage-Strassen FFT for multiplication of polynomials over the > integers. The new implementation includes a truncated FFT algorithm, the > "sqrt 2" trick, and better engineered low-level "butterfly" code. See > http://www.shoup.net/ntl/doc/tour-changes.html for details, including > some benchmarks. > > Also see http://www.shoup.net/ntl/benchmarks.pdf for an updated version > of NTL vs FLINT report. > -- 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 parallel should @parallel be?
Hello. since Sage 8.2 sage.parallel.ncpus.ncpus() returns 1 if you have no environment variables such as MAKE, SAGE_NUM_THREADS, MAKEOPTS set. This number is used by the @parallel decorator and similar constructions to determine the number of processes to run in parallel. (Unless during doctests, then it's set to 2 I think.) The question is: What is a good default for things such as @parallel when SAGE_NUM_THREADS has not been set? I think that 1 is not a good one. The actual number of cores/threads on a system probably isn't either on servers with lots of cores. At some point we had `min(8, number of threads)` which appears reasonable to me. Please join the discussion at https://trac.sagemath.org/ticket/24937 :) julian -- 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] How parallel should @parallel be?
On Mon, 9 Jul 2018, Julian Rüth wrote: The question is: What is a good default for things such as @parallel when SAGE_NUM_THREADS has not been set? I think that 1 is not a good one. The actual number of cores/threads on a system probably isn't either on servers with lots of cores. At some point we had `min(8, number of threads)` which appears reasonable to me. I would suppose that by default Sage uses all cores (or one core); all other limits are artificial. (But Sage doc should contain a little page telling how to use timeout, taskset and ulimit commands on some common Linux distribution. Maybe also a link to page telling about cgroups and even about at-command.) -- Jori Mäntysalo
[sage-devel] Re: Sage fails to build on Arch linux, possible recurrence of an old bug
Thank you all for the useful comments!
Antonio, I wasn't aware of the somewhat limiting way a repo installation
works, this remark made me try to stick to building from source.
Thanks Timo for the emphasis, compiling the develop branch was smooth, I'd
switch back to 8.2+patch if needed.
Cheers,
Amit
בתאריך יום ראשון, 8 ביולי 2018 בשעה 12:10:01 UTC+3, מאת Amit Wolecki:
>
> Hi all!
> Installing sage (8.2) from maintained repo on Arch linux provided a low
> functioning installation which symptoms are given here in the end. I then
> tried to build sage from source, failing with a "generate-posix-vars
> failed" and segfault. This issue resembles
> https://bugs.python.org/issue33374 and https://bugs.python.org/issue21166
> yet I could not deduce a solution to my case.
> System: ver 4.17.4 kernel, with gcc 8.1.1. Has python 2.7.15 installed
> CPU: Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz, 4 cores
>
> As for the packaged installation problem, two examples are:
> 1. sage --testall fails to start, returning:
>
> Setting permissions of DOT_SAGE directory so only you can read and write
> it.
> no stored timings available
> Running doctests with ID 2018-07-08-11-31-28-50157d1f.
> Using --optional=optional,sage
> Doctesting entire Sage library.
> Traceback (most recent call last):
> File "/usr/bin/sage-runtests", line 127, in
> err = DC.run()
> File "/usr/lib/python2.7/site-packages/sage/doctest/control.py", line
> 1150, in run
> self.add_files()
> File "/usr/lib/python2.7/site-packages/sage/doctest/control.py", line
> 696, in add_files
> sagenb_loc = working_set.find(Requirement.parse('sagenb')).location
> AttributeError: 'NoneType' object has no attribute 'location'
>
> 2. installation of packages fail due to some environment confusion, for
> example:
> [amit@amit-desk sage-8.2]$ sage -pip install surface_dynamics
> Collecting surface_dynamics
> Using cached
> https://files.pythonhosted.org/packages/52/8d/9d27f127f159ac58f31a318c36a633d992b5f2430f0624a01910e3c1f5b6/surface_dynamics-0.4.0.tar.gz
> Complete output from command python setup.py egg_info:
> Traceback (most recent call last):
> File "/tmp/pip-install-kf5xxcpj/surface-dynamics/setup.py", line 9,
> in
> from sage.env import SAGE_SRC, SAGE_VERSION
> ModuleNotFoundError: No module named 'sage'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "", line 1, in
> File "/tmp/pip-install-kf5xxcpj/surface-dynamics/setup.py", line 11,
> in
> raise ValueError("this package currently installs only inside
> SageMath (http://www.sagemath.org)")
> ValueError: this package currently installs only inside SageMath (
> http://www.sagemath.org)
>
>
> Command "python setup.py egg_info" failed with error code 1 in
> /tmp/pip-install-kf5xxcpj/surface-dynamics/
>
> I tried to search for leads from these two, but couldn't understand the
> underlying problem.
> Many thanks in advance,
> Amit.
>
--
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: How parallel should @parallel be?
I would also expect it to run as many threads as my laptop has cores (+ hyperthreading if available). -- 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: How parallel should @parallel be?
> > The question is: What is a good default for things such as @parallel when > SAGE_NUM_THREADS has not been set? I think that 1 is not a good one. > +1 The actual number of cores/threads on a system probably isn't either on > servers with lots of cores. At some point we had `min(8, number of > threads)` which appears reasonable to me. > +1 -- 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: How parallel should @parallel be?
On Monday, July 9, 2018 at 2:27:20 PM UTC-7, Friedrich Wiemer wrote: > > I would also expect it to run as many threads as my laptop has cores (+ > hyperthreading if available). > This makes sense for single-user machines, but the current default was implemented because it was deemed safer on machines used by multiple users. -- John -- 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] Re: How parallel should @parallel be?
On Mon, 9 Jul 2018, John H Palmieri wrote: I would also expect it to run as many threads as my laptop has cores (+ hyperthreading if available). This makes sense for single-user machines, but the current default was implemented because it was deemed safer on machines used by multiple users. Then there is a need for better maintainer on the machine. Also, limiting number of CPU cores is the most less efective restriction. Timesharing works very well in any case; much more problematic is program that eats memory or just runs heavy I/O. -- Jori Mäntysalo
Re: [sage-devel] Re: How parallel should @parallel be?
On Monday, July 9, 2018 at 9:49:12 PM UTC-7, Jori Mäntysalo wrote: > > On Mon, 9 Jul 2018, John H Palmieri wrote: > > >> I would also expect it to run as many threads as my laptop has > >> cores (+ hyperthreading if available). > > > This makes sense for single-user machines, but the current default was > > implemented because it was deemed safer on machines used by multiple > > users. > > Then there is a need for better maintainer on the machine. > The reality is that there are many machines like that, though. I have also seen docker images that run on only one core, but where "ncpus" still reports all the cpus on the host machine. I don't know what the right default is, but I think there are many situations where "ncpus" isn't it. -- 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] sagemath 8.3 rc0
Hi, I couldn't compile previous version, always some errors. But this rc0 passed without any problems ! ubuntu xenial AMD 64 8 x 16 Go RAM. Regards Henri -- 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.
