Thanks! I can try to investigate, but in the meantime I will open a ticket
for this on trac.
On Sunday, June 20, 2021 at 7:32:47 AM UTC-4 Kwankyu wrote:
> Hi,
>
> On Sunday, June 20, 2021 at 10:18:50 AM UTC+9 zsc...@gmail.com wrote:
>
>> I have reason to believe that the point P is not torsion
Hi,
I believe that I found a disagreement between Sage and Magma in the
following calculations:
Sage:
R. = QQ[]
f = 144*x^6 - 240*x^5 + 148*x^4 + 16*x^3 - 16*x^2 - 4*x + 1
H = HyperellipticCurve(f)
J = Jacobian(H)
P = J(H(0,1))-J(H(0,-1))
(5*P).is_zero()
returns True
Magma:
R :=
Glad I can help. This is another reason why these virtual environments are
really useful! I have one environment for sage which I never try to update
since I know that everything works. Separately, I have my "main"
environment that I update regularly, which will occasionally break things.
I
1. Did you by any chance accidentally update the jedi package? This is not
really a sage problem, but ipython 7.19.0 is incompatible with the most
recent version of jedi 0.18.0. In your sage environment you can run "conda
list" to see what packages you have installed. If jedi 0.18.0 is
Are you sure it's the inverse function which is slow? Just looking at the
command
f = prod((1 - x^n)^a(n) for n in (1..size)) + O(x^size)
I would guess that first the gigantic product is computed, and only then
would the resulting polynomial be truncated by the O(x^size) part.
Maybe try to
Dima is the expert on this and can correct me if I'm wrong, but I think
Xcode 12 broke sage 9.1. Fortunately this is being fixed for 9.2 which is
already on a release candidate but has not been released in the wild yet.
Probably the easiest thing to do would be to clone the git repository and
Can you post the config.log file that was generated by running ./configure
before running make?
On Friday, October 16, 2020 at 3:19:27 PM UTC-4 Douglas Hulbert wrote:
> Dear Member of the SAGE-DEVEL team:
>
>
>1. My latest attempt to use MAKE to install sage is unsuccessful.
>2. I'm
