On 2018-09-29, Simon King <simon.k...@uni-jena.de> wrote: > Too bad: When the error occurs and I adjust the pool size then > afterwards the previously defined objects in gap are gone.
Additional problem: Even when I increase the memory limit sufficiently, gap-via-pexpect takes substantially longer than libgap to compute the double cosets. Why is that? There shouldn't be big traffic in the interface whan just doing DC = G.DoubleCosetRepsAndSizes(N,N). Cheers, Simon -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
