Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
| 2022-10-15 21:06:39 +0200 | received badge | ● Famous Question (source) |
| 2020-01-09 22:46:45 +0200 | received badge | ● Notable Question (source) |
| 2019-05-20 03:25:10 +0200 | received badge | ● Popular Question (source) |
| 2019-02-09 00:40:18 +0200 | received badge | ● Nice Question (source) |
| 2019-02-08 10:55:38 +0200 | asked a question | Jupyter-Python3 notebooks. Jupyter interface creates and works with Python2 notebooks. It is possible configure it to work also with Python3? (If present in the system obviously) |
| 2019-02-04 16:56:45 +0200 | commented answer | why gives a wrong result? I know the track. And the question has been placed bearing in mind that the error is already known. But the true question is: does anyone know what is the problem in the pipe between SageMath and Maxima that produces this type of "obviously" incorrect results? What are the types of integrals that are known to suffer from this problem? With this information I can try to avoid the problem (in fact, teach my students). Not fixing the problem (I do not know enough about the involved algorithms/programation) but retouching the math to get a more "friendly" (or hard enough) expression to work. |
| 2019-01-31 15:33:53 +0200 | asked a question | why gives a wrong result? integrate(sqrt(2+sin(x)^2),x) |
| 2018-02-17 01:58:14 +0200 | received badge | ● Student (source) |
| 2018-02-17 01:53:32 +0200 | received badge | ● Famous Question (source) |
| 2015-11-20 10:44:09 +0200 | received badge | ● Notable Question (source) |
| 2015-10-28 16:03:45 +0200 | commented answer | After upgrade to 6.9 we obtain SIGILL ... I'm testing if appears any "evident" problem (not at this time, but I'm a "basic user"). Any chance to avoid this kind of problem on 6.10? |
| 2015-10-28 15:56:30 +0200 | received badge | ● Popular Question (source) |
| 2015-10-23 09:03:27 +0200 | commented answer | After upgrade to 6.9 we obtain SIGILL ... Correct, the compilation has no finished. But I have obtained a working Sage (notebook included). |
| 2015-10-22 09:29:32 +0200 | commented answer | After upgrade to 6.9 we obtain SIGILL ... After 6 o 7 h. compilation finishes with error on r-3.2.2.p0 (some part of R?). Sage itself seems to work OK!!! The log finnishes with: make[7]: * [sysdata] Error 133 make[6]: * [all] Error 2 make[5]: * [R] Error 1 make[4]: * [R] Error 1 make[3]: * [R] Error 1 Error building R. real 6m16.079s user 4m7.538s sys 0m52.003s Error installing package r-3.2.2.p0 |
| 2015-10-21 10:16:10 +0200 | commented answer | After upgrade to 6.9 we obtain SIGILL ... sage-6.6-x86_64-Darwin-OSX_10.7_x86_64-app fails (also) Something is broken in my system? |
| 2015-10-20 09:40:51 +0200 | commented question | After upgrade to 6.9 we obtain SIGILL ... I dowloaded the new binary (sage-6.9-x86_64-Darwin-OSX_10.10_x86_64-app.dmg 2015-10-14). Using MacOS 10.10.5 (Yosemite). In fact, I think the problem appears yet in 6.8 . |
| 2015-10-19 11:32:29 +0200 | asked a question | After upgrade to 6.9 we obtain SIGILL ... After upgrding to 6.9 version I obtain Unhandled SIGILL: An illegal instruction occurred in Sage. This probably occurred because a compiled component of Sage has a bug in it and is not properly wrapped with sig_on(), sig_off(). Sage will now terminate.as response to use of float 1.2 but 12/10. works fine. iMac (2008) Intel Core 2 Duo. |
Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.