I was trying to come up with a simple example of how this integration
program claim
was bogus. Here it is.
Take one of your favorite prime-testing programs and generate
a list of 10,000 Largish Primes. I don't know how large, but
say 50 decimal digits or more.
Make 10^8 factorization problem
I was unclear. Davis disagrees with Lample and Charton in their claim of
neural nets being somehow superior to established CAS.
(And yes, the review is by Davis, not Lample.)
On Tuesday, December 17, 2019 at 4:21:07 PM UTC-8, rjf wrote:
>
> disagrees with me? or Emmanuel?
> Lample's abstract (
oops, the review is by Davis; the paper is by Lample and Charton, both of
Facebook.
On Tuesday, December 17, 2019 at 4:21:07 PM UTC-8, rjf wrote:
>
> disagrees with me? or Emmanuel?
> Lample's abstract (of the review) concluded with
>
> The claim that this outperforms Mathematica on symbolic i
disagrees with me? or Emmanuel?
Lample's abstract (of the review) concluded with
The claim that this outperforms Mathematica on symbolic integration needs
to be very much qualified.
I glanced at the full review and I don't see that I disagree with it.
Generating 80 million randomly generated e
On 12/17/19 1:11 PM, Dima Pasechnik wrote:
>
>
>
> Axel is no longer with us. Here is a death notice from 2013.
>
> https://images.app.goo.gl/iLwwbzF1YyB7qLev9
>
A spectacularly poor choice of words on my part, in that case =(
--
You received this message because you are subscribed to the G
On Tue, 17 Dec 2019, 18:38 Michael Orlitzky, wrote:
> SageMath uses a few packages that appear to have been abandoned
> upstream. The most recent example I have in mind is Symmetrica:
>
> http://www.algorithm.uni-bayreuth.de/en/research/SYMMETRICA/
>
> The package's website (symmetrica.de) and
SageMath uses a few packages that appear to have been abandoned
upstream. The most recent example I have in mind is Symmetrica:
http://www.algorithm.uni-bayreuth.de/en/research/SYMMETRICA/
The package's website (symmetrica.de) and contact address are both dead.
The upstream contact (Axel Kohner
Apparenlty, the # symbol was (at least part of) the problem. I pushed a fix
a few minutes ago, not yet tested. You can git pull the latest patchbot
sources.
F
Le mardi 17 décembre 2019 16:55:27 UTC+1, mmarco a écrit :
>
>
>> The second may be a bug in the patchbot server itself. I have no time
>
>
> The second may be a bug in the patchbot server itself. I have no time to
> investigate. Maybe the # in the patchbot name is not a good idea (random
> guess) ?
>
>
It looks like that could be the culprit, since It also happens in other
machines. Any idea on how it could be solved?
--
Yo
