Dear Sage developers,
in order to update the underlying machine, the *trac web server will be
turned off this sunday*, from 7.00 (Paris time) to 23:00 (Paris time ;
https://time.is/Paris).
PLEASE take a short break and resume using trac next week!
Hopefully, the update will go smoothly and tak
Do keep in mind that there is a basic command-driven interface behind
Geogebra as well. You can actually literally enter the following into their
"3D Calculator":
A=(1,2,3)
B=(4,5,6)
L=Segment(A, B)
P=Midpoint(L)
r=Length(L)
C=Circle(P, r)
where the system automatically translates the last comm
On Friday, August 26, 2022 at 8:04:02 AM UTC+9 Kwankyu Lee wrote:
> On Friday, August 26, 2022 at 2:57:15 AM UTC+9 Nils Bruin wrote:
>
>> On Thursday, 25 August 2022 at 07:23:41 UTC-7 Kwankyu Lee wrote:
>>
>>> But an intuitive way (or an object-oriented way ?) is to get the
>>> necessary informat
Short version: no but with implementation caveats.
Longer version: It gores through generic tensor product code:
sage: s = SymmetricFunctions(QQ).s()
sage: s2 = tensor([s, s])
sage: s2.__class__
In order to have it return partition tuples (which didn't exist at the time
this was written either
Is there any good reason that the basis keys in tensor products of
symmetric functions are tuples of partitions and not `PartitionTuples`?
Martin
sage: h = SymmetricFunctions(QQ).h()
sage: t = tensor([3*h[3], 11*h[1,1]+2*h[2]])
sage: t
33*h[3] # h[1, 1] + 6*h[3] # h[2]
sage: [(mu, c) for mu, c
