Just a quick note: The 'normaliz' backend is currently not used by default. 
It needs to be requested explicitly using backend='normaliz'.

On Thursday, June 20, 2019 at 8:13:57 AM UTC-7, vdelecroix wrote:
>
> Salut Sébastien, 
>
> - Is it with or without PyNormaliz installed? 
> - You should run a profiler on both versions and give a more complete 
>    report than a timing difference. 
>
> Best 
> Vincent 
>
> Le 20/06/2019 à 16:59, Sébastien Labbé a écrit : 
> > Dear sage-devel, 
> > 
> > The proof of the main result of my last preprint 
> > [https://arxiv.org/abs/1906.01104] can be reproduced in Sage-8.7 + my 
> > optional slabbe package. The code is provided in appendix and is also 
> > available at 
> > 
> https://github.com/seblabbe/slabbe/blob/develop/demos/arXiv_1906_01104.rst. 
>
> > 
> > With sage-8.7 + slabbe-0.5.1, I can reproduce the computations and it 
> takes 
> > less than 15 seconds: 
> > 
> > $ ~/GitBox/sage-8.7/sage -t arXiv_1906_01104.rst 
> > Using --optional=dochtml,memlimit,mpir,python2,sage 
> > Doctesting 1 file. 
> > sage -t arXiv_1906_01104.rst 
> >      [41 tests, 14.66 s] 
> > ---------------------------------------------------------------------- 
> > All tests passed! 
> > ---------------------------------------------------------------------- 
> > Total time for all tests: 14.7 seconds 
> >      cpu time: 14.7 seconds 
> >      cumulative wall time: 14.7 seconds 
> > 
> > With sage-8.8.rc1 + slabbe-0.5.1, the first operations takes much longer 
> > and eventually dies with 
> > 
> > ---------------------------------------------------------------------- 
> > sage -t arXiv_1906_01104.rst  # Timed out 
> > ---------------------------------------------------------------------- 
> > Total time for all tests: 304.9 seconds 
> >      cpu time: 0.0 seconds 
> >      cumulative wall time: 0.0 seconds 
> > 
> > The operations that I perform are essentially translations and 
> > intersections of polygons with vertices in the Number Field in phi with 
> > defining polynomial z^2 - z - 1. I am using the default backend 'field'. 
> I 
> > know that some progress has been done with respect to polyhedron 
> recently. 
> > Therefore, I was expecting to gain some efficiency by defining 
> explicitly 
> > the polyhedron backend (like normaliz), but I was not expecting such a 
> > regression for the default with no backend provided. 
> > 
> > I also noticed the following modification for the base ring (nb field 
> > *with* embedding) I am using (see below). Can this be an explanation for 
> > operations to be slower? 
> > 
> > ┌────────────────────────────────────────────────────────────────────┐ 
> > │ SageMath version 8.7, Release Date: 2019-03-23                     │ 
> > │ Using Python 2.7.15. Type "help()" for help.                       │ 
> > └────────────────────────────────────────────────────────────────────┘ 
> > sage: z = polygen(QQ, 'z') 
> > sage: K = NumberField(z**2-z-1, 'phi', embedding=RR(1.6)) 
> > sage: K 
> > Number Field in phi with defining polynomial z^2 - z - 1 
> > 
> > ┌────────────────────────────────────────────────────────────────────┐ 
> > │ SageMath version 8.8.rc1, Release Date: 2019-06-13                 │ 
> > │ Using Python 2.7.15. Type "help()" for help.                       │ 
> > └────────────────────────────────────────────────────────────────────┘ 
> > sage: z = polygen(QQ, 'z') 
> > sage: K = NumberField(z**2-z-1, 'phi', embedding=RR(1.6)) 
> > sage: K 
> > Number Field in phi with defining polynomial z^2 - z - 1 with phi = 
> > 1.618033988749895? 
> > 
> > 
> > Thanks for any pointers, 
> > 
> > Sébastien 
> > 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-devel.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7a04e33b-2805-4498-a0c6-bd408ef3be42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to