Re: [sage-devel] memory problem

Yes, but should't that be released once the poset is thrown away? Am Sonntag, 25. November 2018 08:41:50 UTC+1 schrieb Jori Mäntysalo: > > On Sat, 24 Nov 2018, 'Martin R' via sage-devel wrote: > > > I am running a big, but simple computation and running out of memory, > but do > > not understan

Re: [sage-devel] memory problem

On Sat, 24 Nov 2018, 'Martin R' via sage-devel wrote: I am running a big, but simple computation and running out of memory, but do not understand why.  I am pretty sure that the problem is in the computation of the moebius function. moebius_function() uses _moebius_function_values, which means

[sage-devel] memory problem

Dear memory experts! I am running a big, but simple computation and running out of memory, but do not understand why. I am pretty sure that the problem is in the computation of the moebius function. Below is a silly minimal example, together with some checks to make sure it's in moebius_functi

Re: [sage-devel] A Sage interface for FGb (Gröbner bases)

Le vendredi 23 novembre 2018 11:46:07 UTC+1, Martin Albrecht a écrit : > > Hi, > > speaking of Giac (sorry, if this should rather be on sage-support or > off-list): > > Can I get the degree reached during the computation and the sizes of the > matrices considered out somehow? > export GIAC_

[sage-devel] Re: A Sage interface for FGb (Gröbner bases)

Le vendredi 23 novembre 2018 23:53:51 UTC+1, Markus Wageringel a écrit : > > Thanks for the feedback everyone. > > Am Donnerstag, 22. November 2018 09:53:43 UTC+1 schrieb parisse: >> >> Did you make some comparisons with Giac ? >> >> Some benchmarks from Roman Pearce and my own tests, about 2 yea

Re: [sage-devel] Re: A Sage interface for FGb (Gröbner bases)

On Sat, 24 Nov 2018 at 19:25, john_perry_usm wrote: > I walk into this discussion with some hesitancy, but Christian Eder has > developed a rather efficient F4 algorithm. [1] I know it works and is quite > fast, though I haven't compared it to the implementations mentioned above. > Unfortunately,

[sage-devel] Re: A Sage interface for FGb (Gröbner bases)

I walk into this discussion with some hesitancy, but Christian Eder has developed a rather efficient F4 algorithm. [1] I know it works and is quite fast, though I haven't compared it to the implementations mentioned above. Unfortunately, I haven't heard from him in a while after he went off to

[sage-devel] Re: Accidentally merged and pushed other tickets branch

Thanks to all for the quick help! -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sag

[sage-devel] Re: Accidentally merged and pushed other tickets branch

I think the git reset way is conceptually the easiest, just combine it with cherrypick if needed: git reset --hard [last-good-sha1]# go back in history git cherry-pick [sha1-of-commit-to-add]# apply commit that you want to preserve ... repeat as needed ... git push --force# overwrite

[sage-devel] Re: Accidentally merged and pushed other tickets branch

Another (more destructive) way is to use `git reset --hard ` to reset the current branch to a particular commit and then `git push --force` it to trac. Another option is `git rebase --interactive`. Am Samstag, 24. November 2018 12:41:36 UTC+1 schrieb Friedrich Wiemer: > > In https://trac.sagemat

Re: [sage-devel] Accidentally merged and pushed other tickets branch

An easy way is to create another branch and replace the branch on the ticket with a correct one. On Sat, 24 Nov 2018 11:41 Friedrich Wiemer In https://trac.sagemath.org/ticket/25742#comment:13 I accidentally > merged the ticket branch forom #25766 > . > Can

[sage-devel] Re: Accidentally merged and pushed other tickets branch

If I see this correctly, the commit history should be like this: 1b724d6 - worked on Jeroens comments e8cd46b - Merge branch 'develop' into t/25742/change_c_variables_to_64bit_in_booleanfunction_cython_code so the merge commit 2d7915a - Merge branch 'u/asante/sbox_boomerang_uniformity' of git://

[sage-devel] Accidentally merged and pushed other tickets branch

In https://trac.sagemath.org/ticket/25742#comment:13 I accidentally merged the ticket branch forom #25766 . Can someone help and tell me how to undo this? :/ -- You received this message because you are subscribed to the Google Groups "sage-devel" group.