Re: [sage-support] Discrete Logarithm

Hi Panos In GF(p) then an element g is primitive if its embedding into ZZ is coprime with p-1. Since Euclidean algorithm is so fast, you can test this: sage: p = Primes().next(2^2048) #long sage: g1 = 3 sage: gcd(g1, p-1) 3 sage: g2 = 5 sage: gcd(g2, p-1) 1 So 3 is not a primitive element in GF(

[sage-support] Re: Sage says pdflatex it not on my path when it definitely is

On Thursday, May 4, 2017 at 5:02:57 PM UTC-7, Dima Pasechnik wrote: > > You can do the usual Linux administration things by logging into the Linux > console on the VM. > See sections 5 and 6 in https://wiki.sagemath.org/SageAppliance/SageMath-7 > for details. > > I think the new version for the

[sage-support] Re: new sagenb pre-release, please test

On Wednesday, May 10, 2017 at 7:12:29 AM UTC-7, Dima Pasechnik wrote: > > Please test ​https://github.com/sagemath/sagenb/tree/1.0.rc0 (copy of the > current master) before I go ahead with making a new Sage package. It works > for me following the instructions in HASKING (updated, to take care

[sage-support] right click plot dropdown dead in Sage for virtualbox

I'm using Sage in virtualbox on win 8.1. When I right-click on a plot I get a dropdown, but it's dead. I can't use File to save the image, for instance. Is this normal in Sage for virtualbox or is there a fix? -- You received this message because you are subscribed to the Google Groups "sage-s

[sage-support] Embedding towers of number fields

Hello, I would like to do this K. = NumberField([x^2-2,x^2-5], embedding = [RR(sqrt(2)), RR(sqrt(5))]) but embedding towers of number fields seems not to be implemented (and fails without any warning). Here https://ask.sagemath.org/question/25312/embeddings-in-numberfieldtower/ it is explain

[sage-support] new sagenb pre-release, please test

Please test ​https://github.com/sagemath/sagenb/tree/1.0.rc0 (copy of the current master) before I go ahead with making a new Sage package. It works for me following the instructions in HASKING (updated, to take care of changed names and of the need to deal with mathjax). Report issues on git

Re: [sage-support] Bounds in coding theory are still a mess

On Wednesday, May 10, 2017 at 12:17:25 PM UTC+1, Johan S. H. Rosenkilde wrote: > > Dima Pasechnik writes: > > Please note that that "completely unrelated" ticket was fixing the work > of > > your and David (?) GSoC mentee. > > (and part of it was David's himself, IIRC). > > Saying that you

Re: [sage-support] Bounds in coding theory are still a mess

Dima Pasechnik writes: > Please note that that "completely unrelated" ticket was fixing the work of > your and David (?) GSoC mentee. > (and part of it was David's himself, IIRC). > Saying that you have nothing to do with it is, hmm, strange to me, sorry. > And you guys just fell totally silent t

[sage-support] Re: Sage crash Report

at the bottom of the report you see ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory You need to install libgfortran in order to fix this. apt-get install libgfortran3 On Wednesday, May 10, 2017 at 9:26:59 AM UTC+1, Abhishek Kesarwani wrote: > > > Hi

[sage-support] Discrete Logarithm

Hello everyone, I am trying to calculate a primitive element (g) of a big Finite Field: GF(p) where p is prime number > 2^2048 So then, i could share a secret integer (r) as: m=g^r, but it seems impossible to calculate it with function primitive_element() Is there another way i can use to calcu

Re: [sage-support] Bounds in coding theory are still a mess

On Wednesday, May 10, 2017 at 8:47:21 AM UTC+1, Johan S. H. Rosenkilde wrote: > > > Not that more recent additions to sage/coding are perfect, I recall > > spending time untangling the mess on > > https://trac.sagemath.org/ticket/20787 >

[sage-support] Sage crash Report

Hi, Whenever i trying to install sagemath on my ubuntu 17.04 it shows the following error: Oops, Sage crashed. We do our best to make it stable, but... A crash report was automatically generated with the following information: - A verbatim copy of the crash traceback. - A copy of your input

Re: [sage-support] Bounds in coding theory are still a mess

> Not that more recent additions to sage/coding are perfect, I recall > spending time untangling the mess on > https://trac.sagemath.org/ticket/20787 > more or less completely on my own, which gives a good example on how not > to re-implement old functionality ;-) Did I personally offend you? B