Activity
From 16 Mar 2016 to 14 Apr 2016
13 Apr 2016
- 17:04 Slug #866: implicit, ImplicitHypersurface: improve output verification
- John Abbott wrote:
> The example below takes about 12s on my computer, but only about 0.25s if the coeff field is @Z... - 15:45 Slug #866 (In Progress): implicit, ImplicitHypersurface: improve output verification
- The example below takes about 12s on my computer, but only about 0.25s if the coeff field is @ZZ/(32003)@. Why is it...
- 13:34 Slug #866 (In Progress): implicit, ImplicitHypersurface: improve output verification
- The current impl of @SliceCoreQQ@ is simple rather than efficient.
It uses modular+CRT to build the answer.
Current... - 15:41 Bug #867: Compilation Error: C++11 and old GMP-Version
- Thanks to Anna (grrrr!) you can build CoCoALib (and CoCoA-5) with an uninstalled version of GMP, _i.e._ a "private" v...
- 15:23 Bug #867 (Closed): Compilation Error: C++11 and old GMP-Version
- I tried to compile CoCoALib at our LinuxCluster with a pretty old GMP version (4.3.1) and C++11 activated (with addit...
07 Apr 2016
- 16:31 Bug #864 (Resolved): Assignment of rings (esp. derived rings such as PolyRing)
- I have commented out the parts which disable the default assignment. Everything compiled fine, and all tests passed....
06 Apr 2016
- 15:39 Bug #864 (In Progress): Assignment of rings (esp. derived rings such as PolyRing)
- Since assignment is allowed for @ring@ (and presumably causes no trouble), I see no reason for blocking it for "speci...
- 15:15 Bug #864 (Closed): Assignment of rings (esp. derived rings such as PolyRing)
- In issue #244 we approved the activation of assignment for objects of type @ring@.
Mario has pointed out that assign...
05 Apr 2016
- 16:50 Bug #860: Check impl of RingTwinFloatImpl::myIsRational
- One possible explanation for @ContFracIter@ being so slow is that its implementation is "very clean" (_e.g._ it uses ...
- 15:04 Bug #860: Check impl of RingTwinFloatImpl::myIsRational
- I have just tried another timing test with a list of about 90000 copies of @fibonacci(400)/fibonacci(401)@ mapped int...
- 14:43 Bug #860: Check impl of RingTwinFloatImpl::myIsRational
- I have just tried a speed test with more complicated rationals (all of the form @p1/p2@ where @p1@ and @p2@ are disti...
- 14:33 Bug #860: Check impl of RingTwinFloatImpl::myIsRational
- I have implemented a variant of @myIsRational@ which uses @SimplestBigRatBetween@. The implementation is certainly m...
04 Apr 2016
- 14:34 Bug #860 (In Progress): Check impl of RingTwinFloatImpl::myIsRational
- I have just read through the code for @RingTwinFloatImpl::myIsRational@ and it looks OK to me.
The only dodgy aspe...
31 Mar 2016
- 13:20 Support #861: Janet basis code: TmpJB files give some problems with C++11 (using CLANG/LLVM)
- JAA tried compiling on a recent Linux box (with recent gcc, version 5.3.1) explicitly setting the flag @-std=c++11@. ...
- 13:11 Support #861: Janet basis code: TmpJB files give some problems with C++11 (using CLANG/LLVM)
- Some notes about Bruns's platform:...
- 13:10 Support #861: Janet basis code: TmpJB files give some problems with C++11 (using CLANG/LLVM)
- Bruns reported the following errors during compilation:...
- 13:08 Support #861 (Closed): Janet basis code: TmpJB files give some problems with C++11 (using CLANG/LLVM)
- Bruns has reported compilation errors in the Janet Basis code (files called @TmpJB...@) when compiling with the flag ...
- 13:05 Feature #840 (In Progress): GINV: alex basis
- Mario has downloaded the GINV source, but has had several problems with compilation -- he has not yet succeeded in co...
30 Mar 2016
- 18:34 Bug #860 (Closed): Check impl of RingTwinFloatImpl::myIsRational
- Since the old impl of @RingTwinFloat::myIsInteger@ simply called @myIsRational@ and then checked that the denominator...
- 18:31 Design #859 (Resolved): Twin-float: comparisons and equality test
- I have added a new "boolean" data member saying whether *@myIsEqualNZIgnoreSign@* should allow the outer intervals to...
- 15:31 Design #859: Twin-float: comparisons and equality test
- One unfortunate aspect of the mem fn @myCmp5@ is who throws @InsuffPrec@ when a comparison operator needs to throw?
... - 15:20 Design #859: Twin-float: comparisons and equality test
- With the impl I have in mind for @op>=@ and @op<=@ via @myCmp5@, it is not possible to have values @X@ and @Y@ such t...
- 18:23 Bug #853: NearestInt can needlessly throw InsufficientPrecision
- I have cleaned the impl considerably; it is now obviously correct (but possibly slower than necessary as a wasteful t...
- 18:15 Bug #858 (Feedback): floor for TwinFloat can produce ERR::SERIOUS
- I am now happy with the impls; they are simple enough that they are "obviously correct" (I hope!). Also I believe th...
29 Mar 2016
- 16:46 Design #859: Twin-float: comparisons and equality test
- The idea of changing @operator>=@ and @operator<=@ is trickier than I had originally thought (or hoped) because they ...
28 Mar 2016
- 23:07 Design #859: Twin-float: comparisons and equality test
- Perhaps I could implement both approaches and let the user choose. If so, should it be a compile-time switch or a ru...
- 22:59 Design #859: Twin-float: comparisons and equality test
- I am still unsure whether it is reasonable for a test such as @Y <= X@ to give @true@ when @Y = X@ throws @InsuffPrec...
- 22:45 Design #859: Twin-float: comparisons and equality test
- *Variant A* is notionally quite simple; I think I prefer it to the other possibilities. I can try implementing it (i...
- 22:25 Design #859: Twin-float: comparisons and equality test
- A simpler idea would be to modify when comparisons throw @InsuffPrec@.
The model I have in mind is a fixed (non-ze... - 22:08 Design #859: Twin-float: comparisons and equality test
- If we want to keep the behaviour of the comparison functions unchanged (esp. regarding when to throw @InsuffPrec@) th...
- 21:39 Design #859: Twin-float: comparisons and equality test
- The critical step is comparing two twin-floats for equality. If the two values are quite different then it is easy t...
- 21:25 Design #859 (In Progress): Twin-float: comparisons and equality test
- Consider the following code excerpt:...
- 21:18 Design #859 (Closed): Twin-float: comparisons and equality test
- I have some philosophical questions about comparisons between twin-floats.
For the equality test there are 3 possi...
26 Mar 2016
- 22:54 Bug #858: floor for TwinFloat can produce ERR::SERIOUS
- I found a bug in @myIsInteger@, so have written a completely new version (it's quite a nightmare debugging code writt...
- 21:23 Bug #858: floor for TwinFloat can produce ERR::SERIOUS
- An ad hoc test behaved as I expected, so I think @myFloor@ (and @myCeil@ are now OK).
Wish I could say the same for ... - 21:21 Bug #858: floor for TwinFloat can produce ERR::SERIOUS
- I am now convinced that @myFloor@ must effectively make a @myIsInteger@ test.
If @myIsInteger@ succeeds then its r... - 11:28 Bug #858: floor for TwinFloat can produce ERR::SERIOUS
- One way out of the problem would simply be to reinstate the test:...
- 11:06 Bug #858 (In Progress): floor for TwinFloat can produce ERR::SERIOUS
- The point is that the candidate value for floor should really be floor of primary component plus a very small epsilon...
- 11:03 Bug #858 (Closed): floor for TwinFloat can produce ERR::SERIOUS
- Fix impl of @RingTwinFloatImpl::myFloor@ so that the following does not happen...
25 Mar 2016
- 22:29 Feature #856 (Feedback): MantissaAndExponent2 for twin-float
- I have implemented the fn. It seems to work more or less as expected.
Note that the fn does reveal some of what g... - 22:22 Feature #856 (In Progress): MantissaAndExponent2 for twin-float
- Here is a summary description of the ideal behaviour of the "exporting" fn:
let @x@ be a (non-zero) twin-float (zero... - 22:15 Feature #856 (Closed): MantissaAndExponent2 for twin-float
- So far the only way to get a "proper value" out of a twin-float was to use @IsRational@, but that works only if the v...
- 22:11 Bug #853 (Feedback): NearestInt can needlessly throw InsufficientPrecision
- I followed design *(B)*; we just have to be careful if we want to change policy about how halves are handled. Perhap...
- 22:04 Bug #853: NearestInt can needlessly throw InsufficientPrecision
- I think I have fixed the problem. I have completely rewritten the code to do with @floor@, @ceil@ and @NearestInt@.
... - 15:12 Bug #853: NearestInt can needlessly throw InsufficientPrecision
- John Abbott wrote:
> Which is the better design?
> * *(A)* A normal C++ fn (as currently implemented), or
> * *(B)... - 14:59 Bug #853: NearestInt can needlessly throw InsufficientPrecision
- I am thinking of making the test for @NearestInt@ of twin float values work as follows:
fix an integer @N@, for ever... - 14:54 Bug #853: NearestInt can needlessly throw InsufficientPrecision
- Currently the only ordered domains are: @RingZZ@, @RingQQ@ (since a @FractionField@ of an ordered domain is an ordere...
- 22:08 Support #696 (Feedback): test-OrderedRing: activate or eliminate?
- The tests pass, of course.
- 22:07 Support #696: test-OrderedRing: activate or eliminate?
- I have now checked in 2 new tests for ordered domains: @test-OrderedDomain1@ and @test-OrderedDomain2@. The first te...
- 14:16 Design #855: Copyright and authorship?
- I have just had a quick look at the Wikipedia page about copyright, and it does seem like a good idea to have a signe...
- 09:43 Design #855 (In Progress): Copyright and authorship?
- First of all: we'll always be free and open source!
There'll always be X-GPL-X (or relatives) versions of cocoalib!
... - 08:58 Design #855: Copyright and authorship?
- As an example: my (small!) contribution to Emacs...
- 08:56 Design #855 (Closed): Copyright and authorship?
- So far we followed the rule "copyright = author".
Indeed almost all files are by Abbott and/or Bigatti.
But there a...
24 Mar 2016
- 18:09 Bug #820 (Closed): NewMatMinimize, NewMatCompleteOrd - a godforsaken mess!
- 18:01 Design #824 (Closed): Fn names: LexMat or MatLex; StdDegRevLexMat or MatStdDegRevLex etc
- 12:51 Design #854: Function MakeTermOrd should be renamed MakeTermOrdMat?
- Unfortunately we have already renamed it once in CoCoA-5 (from CompleteToOrd).
- 12:48 Design #854 (Closed): Function MakeTermOrd should be renamed MakeTermOrdMat?
- 12:47 Design #827 (Feedback): NewPositiveMat also for matrices over QQ? Also NewIntegerOrdMat. (now called MakeTermOrd)
- 12:16 Bug #814: PPOrdering: matrix ordering, what rings are allowed.
- John Abbott wrote:
> Could it be useful to have a pseudo-ctor which accepts just the "grading matrix"? The pseudo-c... - 12:02 Bug #821 (Closed): IsTermOrdering
- 11:58 Design #819 (Closed): GradingMat: does anyone need it?
- 11:50 Feature #215 (Closed): Janet Bases: check and include code in CoCoALib (first prototype)
- Anna Maria Bigatti wrote:
> The general task is fully done.
> Yet to do: add JB field in ideal in cocoalib, and con... - 11:42 Bug #834 (Closed): Fix test failures (after revising MatrixForOrdering)
- All tests pass (no idea how long we have spent on this). Closing.
John Abbott wrote:
> Ignoring the question of ... - 08:04 Feature #762: ExternalLib-GFan: first prototype
- "GFan":https://www.everipedia.com/gfan/
23 Mar 2016
- 17:29 Bug #853: NearestInt can needlessly throw InsufficientPrecision
- Which is the better design?
* *(A)* A normal C++ fn (as currently implemented), or
* *(B)* mem fns for the rings wh... - 17:12 Bug #853 (In Progress): NearestInt can needlessly throw InsufficientPrecision
- What properties should the result of @NearestInt@ have?
* an obvious property is @abs(NearestInt(X) - X) <= 1/2@
... - 16:52 Bug #853 (Closed): NearestInt can needlessly throw InsufficientPrecision
- The current impl of @NearestInt@ with an arg from a @RingTwinFloat@ can throw @InsufficientPrecision@ when it should ...
- 16:54 Support #696: test-OrderedRing: activate or eliminate?
- Well, this test is worthwhile: it has found a bug in the impl of @NearestInt@ (see #853).
- 11:07 Support #696: test-OrderedRing: activate or eliminate?
- I'll try to fix it and add it to CVS.
- 15:31 Design #806 (Closed): AssignZero for matrix
- 15:27 Bug #783 (Closed): abs for MachineInt
- 15:27 Design #311: XelMat, StdDegRevLexMat, ... should be MatrixView
- We must settle the last questions, and then close.
- 15:24 Design #602 (Closed): OrdMat: should it be a reference to a MatrixView in all PPOrderings?
- 15:20 Bug #804 (Closed): ZeroMat and IdentityMat should produce a matrix not a ConstMatrixView
- 15:17 Design #592 (In Progress): Review design of ConstMatrixView
- 15:10 Feature #811 (Closed): Add new fn SimplestBinaryRatBetween
- 15:10 Feature #836 (Closed): SmallFpImpl: export fns for a fixed convention
- 15:00 Slug #773 (Closed): DMPZmerge: make non-recursive
22 Mar 2016
- 18:19 Support #696: test-OrderedRing: activate or eliminate?
- I don't see it in cvs.
- 18:08 Support #618: Instructions for compiling libnormaliz
This is * *OBSOLETE* * -- see next comment!
Here are the notes I have made for myself (compiling using @make@ ...- 17:59 Feature #735 (Closed): Convert a PPMonoidElem to RingElem with coefficient one
- updated calls in BuiltinFunctions-CoCoALib and CoCoALibSupplement.
NOTE: this is only done for SparsePolyRing becaus... - 17:54 Design #819: GradingMat: does anyone need it?
- I think it is a meaningful function (even though it is simply a submat of OrdMat).
It might become more tricky when ... - 17:44 Bug #834: Fix test failures (after revising MatrixForOrdering)
- I think there are no more failures now. Close this issue?
- 17:42 Bug #831 (Closed): primary.cocoa5
- I cannot remember what was done, but it works now.
- 17:10 Design #849 (In Progress): Cleanup MinPoly code
- Implement syntax @MinPolyXX(f, x)@ with f in R/I
(instead of current @MinPolyXX(f, I, x)@)
- 17:07 Feature #848 (Closed): Implement MinPoly in CoCoALib
- 17:07 Feature #848: Implement MinPoly in CoCoALib
- Anna Bigatti + Elisa Palezzato: translated from cocoa-5 to cocoalib.
Tested, works.
Not documented: still needed pr... - 16:47 Feature #848: Implement MinPoly in CoCoALib
- John Abbott: new class IncrLinDep
- 16:44 Feature #848 (Closed): Implement MinPoly in CoCoALib
- Implement all CoCoA-5 versions of MinPoly in CoCoALib
21 Mar 2016
- 16:57 Feature #795 (Closed): Add new fn InvModNoCheck
- No problems have arisen in the last 5 months; closing!
- 16:55 Design #763 (In Progress): GlobalManager: initialization compatible with initialization of external libs
- This is not really a bug... the extant mechanism for cleaning up global variables is likely to cause trouble in the s...
- 14:58 Design #763: GlobalManager: initialization compatible with initialization of external libs
- This looks to be quite a "delicate" matter. Even if I persuade Anders not to use globals for initializing his librar...
- 16:47 Design #815: GlobalManager: Imminent disaster should be a proper error
- I have added a new section to the documentation about the possible error message during destruction of @GlobalManager...
- 16:00 Design #815 (Resolved): GlobalManager: Imminent disaster should be a proper error
- I have changed the "humorous" message *IMMINENT DISASTER* into the possibly more comprehensible *CoCoA: FAILURE DURIN...
- 15:49 Support #774 (In Progress): Rename file PPMonoidEvZZ
- In my source copy it seems that @PPMonoidEvZZ.C@ has already been absorbed into @PPMonoidEv.C@, but the header files ...
- 15:23 Support #847 (Closed): Doc for BigInt, BigIntOps, BigRat -- should there be BigRatOps?
- The doc for @BigInt@ is split into two: @BigInt@ and @IntOperations@ (also some in @NumTheory@).
Currently the doc... - 15:21 Support #810 (Closed): ILogBase: change name?
- 4 months in feedback without problems: closing!
- 14:36 Bug #830 (Closed): Use MachineInt instead of long for params to ZeroMat, IdentityMat, MatByCols, MatByRows
- This has been resolved for 4 months; no problems have arisen, so I'm closing.
- 14:33 Bug #821: IsTermOrdering
- Have we finished this issue? If I recall well, we made some progress, but I no longer recall whether we actually fin...
- 14:05 Design #846: IsIrred: correct design?
- What are the exact semantics of @IsIrred@? Does it apply only to @RingElem@? [JAA: yes]
Wikipedia says that an *i... - 13:46 Design #846 (In Progress): IsIrred: correct design?
- What is the correct way to design/implement @IsIrred@ for a @RingElem@?
I would like a design that does not need u...
Also available in: Atom