On Monday, February 27, 2017 at 9:50:45 PM UTC+1, parisse wrote:
>
> I have myself implemented symbolic integration in Giac/Xcas in a spirit
> similar to Maxima or Axiom that is a few dozens *algorithms* for some
> classes of integrands, then the Risch algorithm in the rational case, like
> Maxi
On 02/27/2017 09:25 PM, Nils Bruin wrote:
>
> But only after you've declared f to be a function. If you want to do it in
> one line, you'd have to spell out:
>
> f(x) = function('f')(x)
>
> ...
>
> f=function('f')(x).function(x)
Well that's no fun.
> which would probably not fill you with j
On Monday, February 27, 2017 at 5:56:44 PM UTC-8, Michael Orlitzky wrote:
>
> But it fills my heart with
> joy that I can fix things by doing
>
> sage: f(x) = f(x)
> sage: f
> x |--> f(x)
>
> But only after you've declared f to be a function. If you want to do it in
one line, you'd ha
On 02/27/2017 06:18 PM, Nils Bruin wrote:
>
> Michael Orlitzky wrote:
>>
>> I tried the thing that makes more semantic sense,
>>
>> sage: f = function('f',x)
>>
>> ...
>
> Ah, OK. And this made more semantic sense to you because you wanted f to be
> a function called 'f' in the variable x? O
(split from original thread because this is a separate topic)
On Monday, February 27, 2017 at 5:38:17 AM UTC-8, Michael Orlitzky wrote:
>
> I tried the thing that makes more semantic sense,
>
> sage: f = function('f',x)
>
> and it told me to
>
> DeprecationWarning... Use function('f')(x) in
>
>
>
> I think that it might be possible to wrile (in Python ?) a "Ruby rules
> compiler" that could use our (rudimentary) wildcard facility to effect
> those substitutions. A possible companion would be a "Mathematica compiler"
> able to translate a Mathematica Integrate statement and transla
I have myself implemented symbolic integration in Giac/Xcas in a spirit
similar to Maxima or Axiom that is a few dozens *algorithms* for some
classes of integrands, then the Risch algorithm in the rational case, like
Maxima while it seems that Axiom implements the more general algebraic
Risch a
Sorry : I've been interrupted at the wrong omment...
Le lundi 27 février 2017 18:13:33 UTC+1, Emmanuel Charpentier a écrit :
>
> A few points :
>
>1. Sympy has interesting answers in some cases. But :
> 1. It often offers responses as conditional expressions (akin to
> Mathematica
Just got word:
> Congratulations! Sage Mathematical Software System has been selected as a
> Google Summer of Code 2017 mentor organization.
Further steps:
Starting now: mentors and students should get in contact, exchange
ideas about which project can be done, are there projects from the
past
Sorry for the mess, I just read the procedure on the developer's manual. I'll
be creating a new ticket for the stopgap in a second.
S.
* Travis Scrimshaw [2017-02-27 09:01:03]:
Hey Salvatore,
The typical approach is to put a stopgap, but it is best to do it in
such a way that is as minimal
Rubi should rather be seen as a useful collection of knowledge that can be
implemented in different ways. I encourage the Maxima authors to e.g. have
a look at Rubi's chapter 1.2.1. They seem to have completely missed that
the integral of (a+bx+cx^2)^p, p rational, has a general solution in terms
o
Hi Travis,
thank you for the info.
Could you please check that the branch public/ticket/22381 currently attached
to the ticket is acceptable? Issues arise with any kind of input but only
when there are frozen variables so I added the stopgap any time they are
present.
Is there a fast lane to
A few points :
1. Sympy has interesting answers in some cases. But :
1. It often offers responses as conditional expressions (akin to
Mathematica's lists of tuples (expression, rule)), whic we don't (yet ?)
know how to handle ;
2. It often uses special functions not (y
Hey Salvatore,
The typical approach is to put a stopgap, but it is best to do it in
such a way that is as minimal as possible (i.e., hopefully not every
ClusterQuiver from a matrix will have this stopgap pop up, or at worst only
when the input is a matrix).
Best,
Travis
On Monday, February
On Mon, Feb 27, 2017 at 3:34 PM, asutosh hota wrote:
>
>
> On Monday, 27 February 2017 19:15:25 UTC+5:30, Erik Bray wrote:
>>
>> On Mon, Feb 27, 2017 at 2:27 PM, Vincent Delecroix
>> <20100.d...@gmail.com> wrote:
>> > This kind of discussion belong to sage-devel. Please continue the
>> > discussio
Dear all,
some time ago I reported a bug in the implementation of `ClusterQuiver` which
yields wrong answers. The relevant ticket is #22381. To give you an idea
things like this happen:
{{{
sage: B = Matrix([[0,1,0],[-1,0,1],[0,-1,0],[2,0,0]])
sage: Q = ClusterQuiver(B)
On 2017-02-27 16:48, William Stein wrote:
while trying to install Sage 7.5.1 from source on my machine
(Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz, Debian GNU/Linux 9.0 (stretch),
gcc 6.3.0) I got a failure in mpir-2.7.2 (log file attached).
Any advice?
Fixed in https://trac.sagemath.org/ticket/2
For what it is worth, the SageMathCloud docker image includes
sage-7.5, built from source:
https://github.com/sagemathinc/smc/blob/master/src/dev/docker/README.md
It's bigger, since it also contains latex, sagetex, a local
sagemathcloud, etc. But maybe that is a good thing.
-- William
On Mon
On Monday, 27 February 2017 19:15:25 UTC+5:30, Erik Bray wrote:
>
> On Mon, Feb 27, 2017 at 2:27 PM, Vincent Delecroix
> <20100.d...@gmail.com > wrote:
> > This kind of discussion belong to sage-devel. Please continue the
> discussion
> > there.
>
> The latest Docker image for Sage is based
On Mon, Feb 27, 2017 at 2:27 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> This kind of discussion belong to sage-devel. Please continue the discussion
> there.
The latest Docker image for Sage is based on Sage 7.4. The old one
based on 6.x has been deleted so I'm not sure how you're
On 02/26/2017 04:59 PM, Nils Bruin wrote:
> On Sunday, February 26, 2017 at 8:17:05 AM UTC-8, Michael Orlitzky wrote:
>>
>>
>> sage: f = function('f')(x)
>
>
> Please consider to stop using such assignments. It propagates a confusion
> between the *function* f and the *expression* f(x). The di
This kind of discussion belong to sage-devel. Please continue the
discussion there.
Vincent
On 27/02/2017 13:27, asutosh hota wrote:
Installing sage and building it from scratch can be difficult for complete
newbies. However, building and running the project from the docker image is
comparativ
On 2017-02-26 16:52, John Cremona wrote:
@ cells with %gp and %magma were not recognised as being different. I
could put %magma followed by a magma command on the same line, but it
was useful to put %magma just once at the top of a cell and have the
whole cell interpreted using magma.
Right. J
23 matches
Mail list logo