I am working with Elliptic curve in extended field. I tried to get points
/ order in the group. I have copied a small code set results from
notebook. The points obtained are not in the EC; I have checked it using a
Python program I coded for this. Is it a bug / wrong use of codes by me?
Hello,
I do not get the same generators as you, but at least it works
sage: F.f = GF(11^2,'f')
sage: ff2 = EllipticCurve([0+f*0,1+f*0])
sage: ff2
Elliptic Curve defined by y^2 = x^3 + 1 over Finite Field in f of size 11^2
sage: fg =ff2.gens()
sage: fg
[(3*f + 1 : 8*f + 6 : 1), (3 : 5*f + 1 : 1)]
1. In you checking make sure that you have the correct polynomial satisfied
by the field generator f:
sage: F.f = GF(11^2,'f')
sage: f.minpoly()
x^2 + 7*x + 2
2. You can define your curve more simply by
sage: ff2 = EllipticCurve(F,[0,1])
3. The code which computes the generators and group
Hello, I don't know where to post this so redirect me as needed. I believe
I have found a typo in the sage tutorial. Under Sage Tutorial v6.3 A
Guided Tour Some Common Issues with Functions we have the lines
def h(x):
if x2:
return 0
else:
return x-2
The
Hi!
I wonder: How does one access the fields of a record that is defined in
libgap? If R is a record in GAP and f is one of its fields, then it can
be accessed by R.f; however, this does not work in libgap:
sage: R = libgap.eval('rec(a:=1, b:=2)')
sage: R.RecFields() # So, creating the
On 2014-10-01, Simon King simon.k...@uni-jena.de wrote:
Hi!
I wonder: How does one access the fields of a record that is defined in
libgap? If R is a record in GAP and f is one of its fields, then it can
be accessed by R.f; however, this does not work in libgap:
sage: R =
Hi Dima,
On 2014-10-01, Dima Pasechnik dimp...@gmail.com wrote:
sage: R = libgap.eval('rec(a:=1, b:=2)')
sage: R.RecFields() # So, creating the record did work
[ b, a ]
R is a Python dictionary
No, it isn't.
sage: type(R)
type 'sage.libs.gap.element.GapElement_Record'
but...
On Wednesday, October 1, 2014 11:03:18 PM UTC+1, Simon King wrote:
On 2014-10-01, Dima Pasechnik dim...@gmail.com javascript: wrote:
sage: R = libgap.eval('rec(a:=1, b:=2)')
sage: R.RecFields() # So, creating the record did work
[ b, a ]
R is a Python dictionary
No, it
PS: A nicer way to create the libgap record from Python than evaluating
strings is to hand it a Python dict: libgap(dict(a=1, b=2))
On Wednesday, October 1, 2014 11:28:20 PM UTC+1, Volker Braun wrote:
On Wednesday, October 1, 2014 11:03:18 PM UTC+1, Simon King wrote:
On 2014-10-01, Dima
Hi Peter, hi Martin,
somehow both approaches I think don't work for me. For example, the square
(m1^2) is carried in both approaches, even though it can be simplified to
m1 in GF(2). I would like sage to account for the GF(2) in order to
simplify terms. For example I would expect that x * (x +
On 2014-10-01, Volker Braun vbraun.n...@gmail.com wrote:
PS: A nicer way to create the libgap record from Python than evaluating
strings is to hand it a Python dict: libgap(dict(a=1, b=2))
In my applications, I have to read the records from a GAP-readable file.
So, it will be
On Wednesday, October 1, 2014 3:30:16 PM UTC-7, Kim Schoener wrote:
Hi Peter, hi Martin,
somehow both approaches I think don't work for me. For example, the square
(m1^2) is carried in both approaches, even though it can be simplified to
m1 in GF(2). I would like sage to account for the
12 matches
Mail list logo
