Re: [sage-devel] Making the transition from user to developer
Thank you so much for these ideas. On Thursday, July 12, 2018 at 7:44:45 AM UTC-7, mathzeta2 wrote: > > On 12/07/2018 05:28, Ursula Whitcher wrote: > > On 7/11/2018 3:19 PM, prof...@gmail.com wrote: > >> What would be a good way for a Sage user with a basic programming > >> background to learn about Sage development and how codebases are > >> built? Projects ultimately of interest so far are (1) a > >> "show-my-steps" feature for differentiation in Sage or (2) a feature > >> for generating proofs by induction for some class of problems. Are > >> there any relevant tutorial-like things? > > > > A very good way is to attend a Sage Days. > > > > There are some tutorials in the Developers' Guide: > > > > https://doc.sagemath.org/html/en/developer/ > > > > A good first project is nearly always finding something unclear in the > > Developers' Guide and fixing it. > > > > Does "a basic programming background" include some knowledge of Python? > > If not, picking up a little bit of Python is a good place to start. > > > > --Ursula Whitcher. > > > > These are good tips. > > More concretely, for the specific project (1), have you looked into > SymPy's manualintegrate module? Quoting the docs [1]: > > "The option manual=True can be used to use only an algorithm that tries > to mimic integration by hand. This algorithm does not handle as many > integrands as the other algorithms implemented but may return results in > a more familiar form. The manualintegrate module has functions that > return the steps used (see the module docstring for more information)." > > Some examples on SymPy Gamma: > http://www.sympygamma.com/input/?i=integrate+log(x^2)#intsteps > http://www.sympygamma.com/input/?i=integrate%28x*sin%283*x%29%2C+x%29 > and the sourcecode for that can be found at > https://github.com/sympy/sympy_gamma/blob/master/app/logic/intsteps.py > > SymPy is included in Sage, and it might be nice to integrate (pardon the > pun) it better. > > Regards, > TB > > [1] http://docs.sympy.org/latest/modules/integrals/integrals.html > -- 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] Making the transition from user to developer
Thanks for the great tips. And yes, I heart Python. On Wednesday, July 11, 2018 at 7:28:48 PM UTC-7, Ursula Whitcher wrote: > > On 7/11/2018 3:19 PM, prof...@gmail.com wrote: > > What would be a good way for a Sage user with a basic programming > > background to learn about Sage development and how codebases are built? > > > Projects ultimately of interest so far are (1) a "show-my-steps" feature > > for differentiation in Sage or (2) a feature for generating proofs by > > induction for some class of problems. Are there any relevant > > tutorial-like things? > > A very good way is to attend a Sage Days. > > There are some tutorials in the Developers' Guide: > > https://doc.sagemath.org/html/en/developer/ > > A good first project is nearly always finding something unclear in the > Developers' Guide and fixing it. > > Does "a basic programming background" include some knowledge of Python? > If not, picking up a little bit of Python is a good place to start. > > --Ursula Whitcher. > -- 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] Poll about adopting matplotlib2 style for Sage graphics
Hi, This ticket https://trac.sagemath.org/ticket/25799 is about removing the classic style hardcoded to all sage graphics rendered by matplotlib. The hardcoding happened in trac #23696 as people disliked some aspects of the new default style of matplotlib2. It seems that people disliked mainly the new math font (a sans-serif font, not the computer modern font of TeX used in previous matplotlib). Hence the ticket #25799 removes the classic style, and in effect adopts the default style of matplotlib2, but also keep the computer modern math fonts of the classic style. As this change would affect many Sage users, I think this needs a poll here before a reviewer make a decision. So please vote. I recommend you to examine the Sage documentation built with the patch of #25799 before voting. -- 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: Sage on WSL
Thu 2018-07-12 16:12:57 UTC+2, Friedrich Wiemer: > There were some discussions here on running Sage in the > Windows Subsystem for Linux, which comes with Windows 10. > This is just a status update, for those who are interested in > using Sage this way under Windows: > I have successfully compiled Sage 8.3.rc0 and most of the > tests also succeeds, attached is a test log. Many of the > failures during testing is due to the printed warning > /home/asante/local/src/sage/local/lib/python2.7/site-packages/psutil/_pslinux.py:469: RuntimeWarning: 'sin' and 'sout' swap memory stats couldn't be determined and were set to 0 ([Errno 2] No such file or directory: '/proc/vmstat') > warnings.warn(msg, RuntimeWarning) > but there are also some other problems - however, I have > not really looked into those. > Overall, from my little testing up to now, it looks like > compilation is "ok-ish" (still quite slow due to the many > hard-drive accesses I guess), and definitely one possibility > to start hacking on Sage when using Windows. > > If anyone would like me to test something specific, let me know. Thanks for this status update! See also - Ask Sage question 42959 RuntimeWarning [Sage 8.2 WSL] https://ask.sagemath.org/question/42959 -- 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] Making the transition from user to developer
On 12/07/2018 05:28, Ursula Whitcher wrote: On 7/11/2018 3:19 PM, profgr...@gmail.com wrote: What would be a good way for a Sage user with a basic programming background to learn about Sage development and how codebases are built? Projects ultimately of interest so far are (1) a "show-my-steps" feature for differentiation in Sage or (2) a feature for generating proofs by induction for some class of problems. Are there any relevant tutorial-like things? A very good way is to attend a Sage Days. There are some tutorials in the Developers' Guide: https://doc.sagemath.org/html/en/developer/ A good first project is nearly always finding something unclear in the Developers' Guide and fixing it. Does "a basic programming background" include some knowledge of Python? If not, picking up a little bit of Python is a good place to start. --Ursula Whitcher. These are good tips. More concretely, for the specific project (1), have you looked into SymPy's manualintegrate module? Quoting the docs [1]: "The option manual=True can be used to use only an algorithm that tries to mimic integration by hand. This algorithm does not handle as many integrands as the other algorithms implemented but may return results in a more familiar form. The manualintegrate module has functions that return the steps used (see the module docstring for more information)." Some examples on SymPy Gamma: http://www.sympygamma.com/input/?i=integrate+log(x^2)#intsteps http://www.sympygamma.com/input/?i=integrate%28x*sin%283*x%29%2C+x%29 and the sourcecode for that can be found at https://github.com/sympy/sympy_gamma/blob/master/app/logic/intsteps.py SymPy is included in Sage, and it might be nice to integrate (pardon the pun) it better. Regards, TB [1] http://docs.sympy.org/latest/modules/integrals/integrals.html -- 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] Compiling Sage stops at PPL
On Thu, Jul 12, 2018 at 4:26 PM Erik Bray wrote: > > On Fri, Jul 6, 2018 at 5:53 PM Odile wrote: > > > > Hi > > > > I downloaded > > http://www-ftp.lip6.fr/pub/math/sagemath/src/sage-8.2.tar.gz > > > > I installed all the dependencies, including gcc and gfortran > > > > I attach ppl.log and my PPL config.log > > Well here's certainly something interesting from the ppl config.log: > > 2837 config.lt:681: creating libtool > 2838 configure:21701: checking for the GMP library version 4.1.3 or above > 2839 configure:21790: ./libtool --mode=link --tag=CXX g++ -o conftest > -g -O2 -frounding-math -I/home/odile/prj/sage2/local/include > -I/home/odile/prj/sage2/local/include > -L/home/odile/prj/sage2/local/lib > -Wl,-rpath,/home/odile/prj/sage2/local/lib conftest.cpp > -L/home/odile/prj/sage2/local/lib -lgmpxx -lgmp >&5 > 2840 libtool: link: g++ -o conftest -g -O2 -frounding-math > -I/home/odile/prj/sage2/local/include > -I/home/odile/prj/sage2/local/include -Wl,-rpath > -Wl,/home/odile/prj/sage2/local/lib conftest.cpp > -L/home/odile/prj/sage2/local/lib -lgmpxx -lgmp > 2841 configure:21790: $? = 0 > 2842 configure:21790: ./conftest > 2843 ./configure: line 2318: 5834 Illegal instruction > ./conftest$ac_exeext > 2844 configure:21790: $? = 132 > 2845 configure: program exited with status 132 > > > Hmm--a bug in MPIR with your CPU perhaps? What CPU model/architecture is it? Perhaps relevant: https://groups.google.com/d/msg/mpir-devel/wWCb_iPzIWc/ku0lnhKcBAAJ -- 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] Compiling Sage stops at PPL
On Fri, Jul 6, 2018 at 5:53 PM Odile wrote: > > Hi > > I downloaded > http://www-ftp.lip6.fr/pub/math/sagemath/src/sage-8.2.tar.gz > > I installed all the dependencies, including gcc and gfortran > > I attach ppl.log and my PPL config.log Well here's certainly something interesting from the ppl config.log: 2837 config.lt:681: creating libtool 2838 configure:21701: checking for the GMP library version 4.1.3 or above 2839 configure:21790: ./libtool --mode=link --tag=CXX g++ -o conftest -g -O2 -frounding-math -I/home/odile/prj/sage2/local/include -I/home/odile/prj/sage2/local/include -L/home/odile/prj/sage2/local/lib -Wl,-rpath,/home/odile/prj/sage2/local/lib conftest.cpp -L/home/odile/prj/sage2/local/lib -lgmpxx -lgmp >&5 2840 libtool: link: g++ -o conftest -g -O2 -frounding-math -I/home/odile/prj/sage2/local/include -I/home/odile/prj/sage2/local/include -Wl,-rpath -Wl,/home/odile/prj/sage2/local/lib conftest.cpp -L/home/odile/prj/sage2/local/lib -lgmpxx -lgmp 2841 configure:21790: $? = 0 2842 configure:21790: ./conftest 2843 ./configure: line 2318: 5834 Illegal instruction ./conftest$ac_exeext 2844 configure:21790: $? = 132 2845 configure: program exited with status 132 Hmm--a bug in MPIR with your CPU perhaps? What CPU model/architecture is 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.
