On Sun, 2 Sep 2018, 17:53 Simon King, <simon.k...@uni-jena.de> wrote:
> Hi Dima, > > On 2018-09-02, Dima Pasechnik <dimp...@gmail.com> wrote: > > It would be good to submit a Singular bug report with an example at > > https://github.com/Singular/Sources > > I guess I should rather file it in the Singular trac. Well, I'll wait to > see > if a post in the Singular forum helps :-) > my experience is that their trac tickets more or less get transferred to github, before anything happens. So github is just faster. > > It's silly to see an overflow in such a case. > > Yes and no. A simple failing example is > > ring R = 0,(x(1..35)),dp; > > hilb(maxideal(1),1); > ? int overflow in hilb 1 > ? error occurred in or before STDIN line 31: > `hilb(maxideal(1),1);` > > > Do you understand where exactly you are hitting intvec limitations: > > https://www.singular.uni-kl.de/Manual/4-0-3/sing_455.htm#SEC494 > > In the above example, the first Hilbert series *would* be > -t^35 + 35*t^34 - 595*t^33 + 6545*t^32 - 52360*t^31 + 324632*t^30 - > 1623160*t^29 + 6724520*t^28 - 23535820*t^27 + 70607460*t^26 - > 183579396*t^25 + 417225900*t^24 - 834451800*t^23 + 1476337800*t^22 - > 2319959400*t^21 + 3247943160*t^20 - 4059928950*t^19 + 4537567650*t^18 - > 4537567650*t^17 + 4059928950*t^16 - 3247943160*t^15 + 2319959400*t^14 - > 1476337800*t^13 + 834451800*t^12 - 417225900*t^11 + 183579396*t^10 - > 70607460*t^9 + 23535820*t^8 - 6724520*t^7 + 1623160*t^6 - 324632*t^5 + > 52360*t^4 - 6545*t^3 + 595*t^2 - 35*t + 1 > > And since at some of the coefficients simply exceed the permitted range > (the maximal int is 2147483647), Singular won't be able to compute it -- > unless the Singular devs decide to use bigint vectors (don't exist in > Singular yet) or another suitable data format. > 32-bit intvec (instead of 64-bit vectors) is pointless to use on 64-bit systems, it saves no memory or CPU cycles. And this will go far enough in your case, I gather... > > yep, frobby is not maintained, too... > > Ouch. > > > CoCoAlib is essentially a two-person project. > > I know John Abbott, one of the two, reasonably well, could we get him > > involved? > > Worth trying. I don't know how John and Anna stand on Sage. > > > The core of M2 is essentially a two-person project. They are very > > approachable, but often busy. Try their github... > > (I have mixed experience with building M2. IMHO they make it harder by > not > > using automake...) > > I *did* use their github, and they *do* use automake - in a strange way. > they use autoconf, but no automake, I think. The first step was to run "make" -- which resulted in invoking autotools! > > The second step was to run "./configure". It failed, until I deleted the > MAKE environment variable. > > The third step was to run "make" again, which now used another makefile > than the first "make". > > The next step was to deal with the dependencies that are forgotten to be > mentioned in the INSTALL file, and try "make" again. > > The last step was to observe strange errors related with openblas. > > Best regards, > Simon > > -- > 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 sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- 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 sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
