[sage-devel] Re: Education: hints to manual integration
This is now #28415 https://trac.sagemath.org/ticket/28415 El lunes, 19 de agosto de 2019, 13:24:10 (UTC+2), mmarco escribió: > > I have been working a bit on some functions to help students do > integration by hands. Under the hood, they use sympy's integral_steps > function (see [1]), but I am not sure which is the right way to present it. > The options I am considering are: > > 1) Go full step-by-step integrations, in the spirit of sympygamma site > (or wolframalpha, if you have access to the pro version). In that case, I > guess returning a text (or html) stringwould be the sensible choice. > > 2) Just show a hint for the next step to the student, something like: > > sage: integration_hint(sin(x)*x, x) > Integrate by parts, with u=x, dv=sin(x)dx. So integral(sin(x)*x, x) = x* > cos(x)-integral(cos(x),x) > > In this case, maybe we should return a specific class where the student > can get the expression to follow the computation by hand. Also, we could > have different display methods for different envirments (mainly, command > line and jupyter notebook) > > So my questions are: > > - Which option do you think would be preferable? Show the full step by > step solution, or just give hints as they are asked for? > - In any case, which would be the right way to handle different > representations deppending on the environments? I assume that if we have a > specific class for this, it should have some __repr__, __latex__, and > __pretty_print__ > - Which would be the right place to put this code? I would say > sage.symbolic.integral, but some time ago someone mentioned the posibility > to create an education module, to put the different pieces of code that was > writen with for educational purposes. > > What do you think? > > > > > [1] https://docs.sympy.org/0.7.5/modules/integrals/integrals.htm > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/870cb43f-a94e-4be7-aa60-60798903003d%40googlegroups.com.
[sage-devel] Re: error building barvinok (sage 8.9.beta8 + system NTL)
Thanks. I guess what I'm asking for is a solution. From what you say here, and what is said in the links, the problem seems to be a bug in libtool, not NTL. So a solution would be, either: 1) a patch other type of libtool workaround, or 2) an alternative to libtool. I though the whole point of libtool was to take care of all this nonsense, and if it's not doing that, then it seems kind of pointless. On Tuesday, August 27, 2019 at 1:42:51 PM UTC-4, Antonio Rojas wrote: > > > > El martes, 27 de agosto de 2019, 16:25:12 (UTC+2), Victor Shoup escribió: >> >> I reviewed some comments which mentioned a problem with ntl and threads. >> I’m happy to fix that, but I don’t think I understand what the issue is. >> Can anyone explain? Thanks. > > > Hi Victor, > IIRC I reported this to you about a year ago. The problem is that you are > using libtool as a build command, which calls the compiler with the > -nostdlib flag, which in turn overrides the -pthread flag, so the binaries > end up not being linked to libpthread. See eg. [1][2] for more info. > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=661333 > [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25460 > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/8399069c-b8db-4ca5-ba63-54e14aba890e%40googlegroups.com.
Re: [sage-devel] Re: error building barvinok (sage 8.9.beta8 + system NTL)
Victor, as far as I understand the main configuration script of ntl is the perl DoConfig script. It has nothing to do with libtool. libtool is robust if you let it handle the configuration. It will not try to fix a given one. In a libtool configure.ac script you would just have a directive AC_CHECK_LIB for pthread. In short, I would suggest 3) Replace DoConfig by a configure.ac script Vincent Le 28/08/2019 à 15:15, Victor Shoup a écrit : Thanks. I guess what I'm asking for is a solution. From what you say here, and what is said in the links, the problem seems to be a bug in libtool, not NTL. So a solution would be, either: 1) a patch other type of libtool workaround, or 2) an alternative to libtool. I though the whole point of libtool was to take care of all this nonsense, and if it's not doing that, then it seems kind of pointless. On Tuesday, August 27, 2019 at 1:42:51 PM UTC-4, Antonio Rojas wrote: El martes, 27 de agosto de 2019, 16:25:12 (UTC+2), Victor Shoup escribió: I reviewed some comments which mentioned a problem with ntl and threads. I’m happy to fix that, but I don’t think I understand what the issue is. Can anyone explain? Thanks. Hi Victor, IIRC I reported this to you about a year ago. The problem is that you are using libtool as a build command, which calls the compiler with the -nostdlib flag, which in turn overrides the -pthread flag, so the binaries end up not being linked to libpthread. See eg. [1][2] for more info. [1] https://bugzilla.redhat.com/show_bug.cgi?id=661333 [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25460 -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/fa916b1e-c62c-d64d-485e-a84b736a4bff%40gmail.com.
[sage-devel] Re: error building barvinok (sage 8.9.beta8 + system NTL)
El miércoles, 28 de agosto de 2019, 15:15:18 (UTC+2), Victor Shoup escribió: > > Thanks. I guess what I'm asking for is a solution. From what you say > here, and what is said in the links, the problem seems to be a bug in > libtool, not NTL. So a solution would be, either: > 1) a patch other type of libtool workaround, or > 2) an alternative to libtool. > I though the whole point of libtool was to take care of all this nonsense, > and if it's not doing that, then > it seems kind of pointless. > > I'd say the easiest fix would be to treat libpthread just like any other library and link to it by passing -lpthread to the linker instead of relying on the -pthread gcc flag (I don't speak perl so I can't help with a patch, sorry) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/e48173fb-ec1f-4e69-af58-19dc6035b32d%40googlegroups.com.
Re: [sage-devel] Re: error building barvinok (sage 8.9.beta8 + system NTL)
On Wed, 28 Aug 2019 at 14:55, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Victor, as far as I understand the main configuration script of ntl > is the perl DoConfig script. It has nothing to do with libtool. libtool > is robust if you let it handle the configuration. It will not try to > fix a given one. > > In a libtool configure.ac script you would just have a directive > AC_CHECK_LIB for pthread. > > In short, I would suggest > > 3) Replace DoConfig by a configure.ac script > Good luck with that. Feel free to consult eclib's configure.ac which was 90% written by people more knowledgeable than me, and which ensures that NTL works for eclib. John > > Vincent > > Le 28/08/2019 à 15:15, Victor Shoup a écrit : > > Thanks. I guess what I'm asking for is a solution. From what you say > here, > > and what is said in the links, the problem seems to be a bug in libtool, > > not NTL. So a solution would be, either: > > 1) a patch other type of libtool workaround, or > > 2) an alternative to libtool. > > I though the whole point of libtool was to take care of all this > nonsense, > > and if it's not doing that, then > > it seems kind of pointless. > > > > On Tuesday, August 27, 2019 at 1:42:51 PM UTC-4, Antonio Rojas wrote: > >> > >> > >> > >> El martes, 27 de agosto de 2019, 16:25:12 (UTC+2), Victor Shoup > escribió: > >>> > >>> I reviewed some comments which mentioned a problem with ntl and > threads. > >>> I’m happy to fix that, but I don’t think I understand what the issue > is. > >>> Can anyone explain? Thanks. > >> > >> > >> Hi Victor, > >> IIRC I reported this to you about a year ago. The problem is that you > are > >> using libtool as a build command, which calls the compiler with the > >> -nostdlib flag, which in turn overrides the -pthread flag, so the > binaries > >> end up not being linked to libpthread. See eg. [1][2] for more info. > >> > >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=661333 > >> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25460 > >> > > > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/fa916b1e-c62c-d64d-485e-a84b736a4bff%40gmail.com > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAD0p0K4p_t55SP9OmjO-0QO%2BvD1e9rGvrL3%3D2SYJbLdy-CFh8g%40mail.gmail.com.
[sage-devel] Re: inconsistency in computation of differential of a map between manifolds
Hi Simon, Le mercredi 28 août 2019 07:07:03 UTC+2, Simon King a écrit : > > > Is the option really called "verbose=True"? Not "check=True", like in > most other cases? > > You are perfectly right: "check" would be more appropriate than "verbose" in this context. I'll open a ticket for this and make "check=True" the default. 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/766eaa6c-a6e6-4154-b9e3-90635455542e%40googlegroups.com.
Re: [sage-devel] Re: error building barvinok (sage 8.9.beta8 + system NTL)
Victor, as you ship libtool, you can just patch it, essentially as in https://lists.gnu.org/archive/html/libtool-patches/2013-11/msg00015.html It needs to be moved to a slightly different place, but it works, you'd get a properly linked libntl.so with the patch (attached), I checked this on Linux at least. HTH Dima On Wed, Aug 28, 2019 at 4:55 PM Antonio Rojas wrote: > > > > El miércoles, 28 de agosto de 2019, 15:15:18 (UTC+2), Victor Shoup escribió: >> >> Thanks. I guess what I'm asking for is a solution. From what you say here, >> and what is said in the links, the problem seems to be a bug in libtool, not >> NTL. So a solution would be, either: >> 1) a patch other type of libtool workaround, or >> 2) an alternative to libtool. >> I though the whole point of libtool was to take care of all this nonsense, >> and if it's not doing that, then >> it seems kind of pointless. >> > > I'd say the easiest fix would be to treat libpthread just like any other > library and link to it by passing -lpthread to the linker instead of relying > on the -pthread gcc flag (I don't speak perl so I can't help with a patch, > sorry) > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/e48173fb-ec1f-4e69-af58-19dc6035b32d%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2NWxGnhDGFj2g6-xfZ%2Bhfy%2BWKkaFcJyDnMNez3FGchsw%40mail.gmail.com. ltmain.sh.diff Description: Binary data
Re: [sage-devel] Re: error building barvinok (sage 8.9.beta8 + system NTL)
El miércoles, 28 de agosto de 2019, 23:47:43 (UTC+2), Dima Pasechnik escribió: > > Victor, > as you ship libtool, you can just patch it, essentially as in > https://lists.gnu.org/archive/html/libtool-patches/2013-11/msg00015.html > It needs to be moved to a slightly different place, but it works, > you'd get a properly linked libntl.so with the patch (attached), I > checked this on Linux at > least. > > Relying on patched bundled copies of dependencies is very much frowned upon by distros. It would be much preferable to make this work with unmodified libtool, which may be provided by the distribution. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/fe05da99-083f-4283-ab3f-14249d14dc15%40googlegroups.com.
Re: [sage-devel] Re: error building barvinok (sage 8.9.beta8 + system NTL)
On Thu, Aug 29, 2019 at 12:55 AM Antonio Rojas wrote: > > > > El miércoles, 28 de agosto de 2019, 23:47:43 (UTC+2), Dima Pasechnik escribió: >> >> Victor, >> as you ship libtool, you can just patch it, essentially as in >> https://lists.gnu.org/archive/html/libtool-patches/2013-11/msg00015.html >> It needs to be moved to a slightly different place, but it works, >> you'd get a properly linked libntl.so with the patch (attached), I >> checked this on Linux at >> least. >> > > Relying on patched bundled copies of dependencies is very much frowned upon > by distros. It would be much preferable to make this work with unmodified > libtool, which may be provided by the distribution. Well, libtool is just a shell script, more or less. NTL isn't unique in shipping its own version. Does Arch use its own libtool when building NTL, or the bundled 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 view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/fe05da99-083f-4283-ab3f-14249d14dc15%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq10GkawYyn2S%2Bb4QBUJT8KgN%2BN1XVXcimFurLRqmf3T2g%40mail.gmail.com.
