Benjamin Lorenz

> 10:24:38 Cone | 72 72 > 10:26:16 Test Summary: | Pass Total > > 10:26:16 Group | 9 9 > 10:26:58 Test Summary: | Pass Total The extra empty...

The output is really confusing yes. > Test Summary: | Pass Total Duration > Group | 9 9 2.7 s > Test Summary: | Pass Total Duration > Polyhedron |...

Latest nightly test runs will show timings by default: https://github.com/oscar-system/Oscar.jl/runs/4424684401?check_suite_focus=true#step:5:139

It might be because of wrappers the polymake needs to compile, these will be stored below `.julia/polymake_user` (and very soon in a scratchspace). You could run `rm -rf ~/.julia/polymake_user/wrappers.*` and...

Thanks for confirming. We should keep at least one test-case that triggers one wrapper compilation to make sure that still works, as we previously had some cases where this failed...

As discussed in the Friday-meeting the runtime of the `Ring interface for localized polynomial rings` does jump up quite a bit from time to time. I let this group run...

Some more timings (top 20): ``` Number of iterations: 200 Sorted by median, max shown if max >= median*1.05, in seconds: Polyhedron{nf_elem}: median 70.2 Ring interface for localized polynomial rings:...

Why can't we seed these random-elements such that the testsuite will run on exactly the same random elements every time? (Or at least add in an environment variable that forces...

Some simplifications for the matrix conversions: ```julia #(2) Form point set to be triangulated f = convex_hull( [-1 -1 -1; 2 -1 -1; -1 2 -1]) points = lattice_points(f) V...

I had another look, this time more on the performance side: most of the time seems to be spent in the redundancy elimination of the fan in the loop. This...