Activity
From 30 Nov 2015 to 29 Dec 2015
23 Dec 2015
- 12:25 Bug #784: threadsafety: Scott Meyers's advice about cached values
- I read a bit in Stroustrup C++ book. There I found a method @std::call_once@ (in @<mutex>@). This method could be a n...
18 Dec 2015
- 16:26 Feature #664 (Resolved): Impl small non-prime finite fields (using logs)
- I have checked in the code I currently have. no doc, no examples, no tests.
An unofficial, simple example (@Fq4.C@ ...
17 Dec 2015
- 16:25 Design #64: submat takes only vector<long>
- John Abbott wrote:
> If we were to adopt the idea of @RowSelect@ and @ColSelect@ then we could offer several signatu... - 16:07 Design #64: submat takes only vector<long>
- If we were to adopt the idea of @RowSelect@ and @ColSelect@ then we could offer several signatures for @submat@:
* @... - 14:33 Design #64: submat takes only vector<long>
- John Abbott wrote:
> Here are some other possible suggestions:
I think that's too many, and I think it's not wort... - 16:19 Feature #664: Impl small non-prime finite fields (using logs)
- JAA now has a prototype impl which still needs lots of cleaning, but some simple tests pass :-)
I'm hoping to clea...
16 Dec 2015
- 18:23 Design #64: submat takes only vector<long>
- Scott Meyers advises making interfaces which are "easy to use correctly and hard to use incorrectly"; I think this is...
- 18:11 Design #64 (In Progress): submat takes only vector<long>
- Here are some other possible suggestions:
* @submat(M, AllRows, ...)@ to select just certain columns
* @submat(M, .... - 11:42 Design #64: submat takes only vector<long>
- I don't think we should allow other integer types, after all we want to discourage other integer types.
One think I ... - 11:52 Design #825: IsPositiveGrading -- really need 2 signatures?
- -- fixed test anna.cocoa5
-- updated CoCoA-5 manual
-- made suggestion for submat ;-)
10 Dec 2015
- 18:19 Feature #836 (Feedback): SmallFpImpl: export fns for a fixed convention
- It was quite trivial to add the new fns. I have updated the doc too.
Should there be a specific test?
Should imp... - 18:16 Feature #836 (Closed): SmallFpImpl: export fns for a fixed convention
- I found a case where I needed to obtain the least non-negative residue from a @SmallFpImpl::value@. Doing this via @...
- 15:59 Bug #834: Fix test failures (after revising MatrixForOrdering)
- Ignoring the question of the name for @ColCheck@, is it better to have a single fn with a flag to say whether or not ...
- 15:03 Bug #834: Fix test failures (after revising MatrixForOrdering)
- I'm also writing *@IsUpperTriangular@*.
*Addendum* (JAA) also @IsLowerTriangular@? Will these go into a "matrix" so... - 14:36 Bug #834: Fix test failures (after revising MatrixForOrdering)
- I'm writing another function *HasNegEntry* which checks whether there is a negative entry.
(then we can think of a be... - 13:11 Bug #834: Fix test failures (after revising MatrixForOrdering)
- lines 304 and following (@#ifdef@) in @PPOrdering.C@ should be deleted:
we do non require to have a PositiveGrading f... - 10:17 Bug #834: Fix test failures (after revising MatrixForOrdering)
- I have just checked in a modified version of @MatrixForOrdering.C@ following Anna's suggestion in comment 2.
Now "...
09 Dec 2015
- 22:08 Bug #834 (In Progress): Fix test failures (after revising MatrixForOrdering)
- First bug trapped:
IsPositiveOrd wants @rk(M) == NumRows(M)@.
This function is called when making a term ordering o... - 13:41 Bug #834: Fix test failures (after revising MatrixForOrdering)
- JAA believes the root cause is the check that a grading is strictly positive when weakly positive is sufficient.
- 13:40 Bug #834 (Closed): Fix test failures (after revising MatrixForOrdering)
- The current CVS produces 3 failed CoCoALib tests:
@test-MatrixForOrdering1, test-RingWeyl1, test-SparsePolyRing1@
a... - 17:02 Feature #664: Impl small non-prime finite fields (using logs)
- JAA will try to implement this before xmas (2015!)
But first some Gluehwein ;-) - 17:00 Feature #142: Improve threadsafety
- I wonder whether @CoCoA_THREADSAFE@ is to be just a temporary measure. Presumably at some point practically all comp...
- 13:09 Feature #142: Improve threadsafety
- I spoke to Mario this morning about threadsafety in CoCoALib (also thinking about Mario's new code which has just bee...
- 16:55 Bug #784 (In Progress): threadsafety: Scott Meyers's advice about cached values
- Bearing in mind the suggestion in issue #142 about using a compile-time switch to indicate whether we want threadsafe...
- 16:48 Feature #835: Make Mario's new code threadsafe
- See the examples in issue #784; I think this should cover many cases.
- 14:03 Feature #835 (New): Make Mario's new code threadsafe
- Adapt Mario's new code so that it is threadsafe (when @CoCoA_THEADSAFE@ is set).
- 13:54 Feature #828: MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- Currently a @MachineInt@ is converted to a @long@ using the function @AsSignedLong@ which includes a check for overfl...
08 Dec 2015
- 15:06 Bug #833: UIBC: need include file in RingWeyl.C
- The fact that UIBC needs to be visible in @RingWeyl.C@ is "unfortunate". John and Mario think this may be a symptom ...
- 15:04 Bug #833 (New): UIBC: need include file in RingWeyl.C
- With Mario's new code the file @RingWeyl.C@ must include @TmpUIBC.H@ otherwise it does not compile.
This is likely... - 14:01 Design #824: Fn names: LexMat or MatLex; StdDegRevLexMat or MatStdDegRevLex etc
- I have renamed the fns and changed all calls -- well, everything compiles.
Will check doc, then check-in.
- 13:03 Feature #665: Integrate Janet/Pommaret basis code
- A simple interface is: a function which forces computation of a GBasis (without copying the result), and a function w...
- 12:32 Feature #665: Integrate Janet/Pommaret basis code
- Here is a brief "one-way discussion" about some function interfaces: I shall consider just @IsMonomial@, but it is a ...
- 11:42 Feature #665 (In Progress): Integrate Janet/Pommaret basis code
- With Mario's help we have integrated his code into (my copy of) the CoCoA sources.
Some questions have arisen whic...
04 Dec 2015
- 15:18 Design #824: Fn names: LexMat or MatLex; StdDegRevLexMat or MatStdDegRevLex etc
- After skype with Anna: we prefer the nicer sounding names.
So I'll change the names in CoCoALib so that *@Mat@* is a ... - 15:11 Bug #820: NewMatMinimize, NewMatCompleteOrd - a godforsaken mess!
- John Abbott wrote:
> Perhaps @MakeTermOrd@ or @MakePositiveTermOrdering@, or something similar?
@MakeTermOrd@! - 15:03 Bug #820: NewMatMinimize, NewMatCompleteOrd - a godforsaken mess!
- I do not much like the names @CompleteToOrd@ and @NewMatCompleteOrd@.
Perhaps @MakeTermOrd@ or @MakePositiveTermO... - 15:08 Design #832 (New): Generalize grading matrix
- Currently matrices for gradings must be full rank and have no negative entries.
In princicple we could accept negati...
03 Dec 2015
- 10:09 Feature #664: Impl small non-prime finite fields (using logs)
- Given the cost of converting between a "compressed" format and a "vector" format, it is probably better to represent ...
02 Dec 2015
- 18:24 Feature #826: Sparse matrices
- I had a quick look on Wikipedia for information about sparse matrices. There they distinguished between representati...
- 17:17 Feature #664: Impl small non-prime finite fields (using logs)
- A very simple speed test: compute the order of the field/group generator by naive repeated multiplication.
Prototype ... - 15:50 Feature #664: Impl small non-prime finite fields (using logs)
- Here are some options for implementing extensions of (prime) finite fields:
* *(A)* use a CoCoALib quotient ring
* ... - 15:13 Feature #664: Impl small non-prime finite fields (using logs)
- I have just tried a simplistic speed test (on the "new" computer here in Kassel). The aim was to see how costly it i...
- 15:08 Feature #664: Impl small non-prime finite fields (using logs)
- Certainly an explicit quotient ring which is a finite field will be isomorphic to one of "my" finite fields. It migh...
- 15:01 Feature #797: SmallFpImpl: make it faster
- Some (more or less) obvious comments:
* the advantage of having log/exp tables is that some computations can be noti... - 14:55 Bug #804 (Feedback): ZeroMat and IdentityMat should produce a matrix not a ConstMatrixView
- @IdentityMat@ and @ZeroMat@ are now in @matrix.H@ -- Anna's suggestion.
The args are now @MachineInt@ instead of jus...
01 Dec 2015
- 22:39 Bug #831: primary.cocoa5
- I did remember doing something like this.
This was because of a problem in cocoa 4 about 0 in the first row.
I th... - 19:00 Bug #831: primary.cocoa5
- I have put this under CoCoALib even though the example comes from the C5 tests, because I think that te real problem ...
- 18:59 Bug #831 (Closed): primary.cocoa5
- The C5 test @primary.cocoa5@ fails because it calls @CompleteToOrd@ on the following matrix:...
- 15:39 Bug #814: PPOrdering: matrix ordering, what rings are allowed.
- Refering to comment 4: I have now removed the signature with 3 args (after speaking to Anna about it).
- 15:34 Bug #820: NewMatMinimize, NewMatCompleteOrd - a godforsaken mess!
- I shall shortly try to implement the semantics given in comment 4 above.
After speaking to Anna, the idea is that ... - 15:29 Feature #828: MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- I'm mostly interested in a solution which will make most code easy to read (without significant run-time overhead).
... - 15:26 Feature #828: MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- I've just spoken to Mario about this issue (even though he wasn't on the watchers list).
He made some suggestions:
*... - 11:28 Feature #828: MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- It might make sense to allow other types of "condition":
@RangeCheck(arg, PositiveLong)@ or perhaps simply @RangeCh... - 11:25 Feature #828: MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- Mmm, I guess Scott Meyers would not be impressed by a fn @IsInRange@ which takes 3 integer args -- one could guess th...
- 14:31 Design #822: Should ElimMat return a ConstMatrix
- Checked in the updated code.
Still need: decide fn names, write proper doc!
- 14:29 Design #822: Should ElimMat return a ConstMatrix
- The documentation for @ElimMat@ and @HomogElimMat@ is largely missing; and the names given in the doc are different f...
- 14:19 Design #822: Should ElimMat return a ConstMatrix
- I suppose strictly the fns should be called @ElimOrdMat@ and @HomogElimOrdMat@.
Is that a good idea or a not-so-good... - 14:09 Design #822: Should ElimMat return a ConstMatrix
- Anna suggested change the arg order for @ElimMat@ and @HomogElimMat@ so that the list of indets to elim is the first ...
- 14:04 Design #829: PPOrderingCtor: name of mem fn which actually constructs?
- There are two ways to create a "lex" ordering for @N@ indets:
@NewLexOrdering(N)@ or @lex(N)@.
I wonder whether... - 13:55 Design #829 (Resolved): PPOrderingCtor: name of mem fn which actually constructs?
- I've made the change (plus some very minor cleaning), incl changing the arg names!
Also made the analogous chang... - 13:14 Bug #830 (Resolved): Use MachineInt instead of long for params to ZeroMat, IdentityMat, MatByCols, MatByRows
- Implemented. No need to change doc (I believe).
A few minor consequential changes.
Will check in shortly.
- 11:08 Bug #830: Use MachineInt instead of long for params to ZeroMat, IdentityMat, MatByCols, MatByRows
- The same applies to @SetEntry@, @SwapRows@, @SwapCols@, @DeleteRow@, @DeleteCol@.
- 11:07 Bug #830 (Closed): Use MachineInt instead of long for params to ZeroMat, IdentityMat, MatByCols, MatByRows
- The pseudo-ctors @ZeroMat@, @IdentityMat@, @MatByCols@, @MatByRows@ have params of type @long@; these should be of ty...
- 11:01 Design #806 (Resolved): AssignZero for matrix
- Since the fn @AssignZero@ (for matrices) was no longer used anywhere, and especially since its semantics were rather ...
- 10:41 Design #824: Fn names: LexMat or MatLex; StdDegRevLexMat or MatStdDegRevLex etc
- Here are some other names.
With *SUFFIX* @Mat@:
@ZeroMat@, @IdentityMat@, @BlockMat@, @DiagMat@, @ColMat@, @RowMa...
30 Nov 2015
- 18:54 Feature #828: MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- @IsGreaterThan@?
Or just overwrite @operator>@? - 18:50 Feature #828: MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- Ok, for the Check function (with the function name).
But I 'd rather have (n, lo, hi)... Am I too late to notice ... - 18:12 Feature #828: MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- In prima battuta farei solo @MaxLong@ perche' voglio "scoraggiare" l'uso di @unsigned long@.
Non ti viene i mente ... - 17:56 Feature #828: MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- John Abbott wrote:
> Perhaps the existing @IsInRange@ is not too far from what I want; the real hitch is that an upp... - 17:42 Feature #828 (In Progress): MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- Perhaps the existing @IsInRange@ is not too far from what I want; the real hitch is that an upperbound has to be spec...
- 17:38 Feature #828 (In Progress): MachineInt: function for checking that value is greater than some lower limit (and below MAXLONG)
- Many fns accepting a @MachineInt@ actually want a positive (or non-negative) value.
There is a fn called @IsInRang... - 18:27 Design #829: PPOrderingCtor: name of mem fn which actually constructs?
- Ok, good for operator()!
Still I 'd call the variable @OrdCtor@ ;-) - 18:23 Design #829: PPOrderingCtor: name of mem fn which actually constructs?
- Yes, it should be possible to write @lex(NumIndets)@, but normally it would be enough to write just @lex@ and let the...
- 18:06 Design #829: PPOrderingCtor: name of mem fn which actually constructs?
- Would it be possible to write @PPOrdering O = lex(NumIndets);@?
If not, I fear it might be more confusing.
In fact... - 17:52 Design #829: PPOrderingCtor: name of mem fn which actually constructs?
- We could also have both, but I do not usually like to offer two ways of achieving the same thing... a user might be p...
- 17:48 Design #829 (Closed): PPOrderingCtor: name of mem fn which actually constructs?
- Currently @PPOrderingCtor@ has a mem fn called @myCtor@ which accepts an integer arg and returns the ordering for tha...
- 14:54 Design #819: GradingMat: does anyone need it?
- John Abbott wrote:
> @GradingMat@ is used in @hp.cpkg5@ but just for testing whether the grading is "standard"; Ann... - 11:40 Bug #821: IsTermOrdering
- John Abbott wrote:
> Does the 0x0 matrix define a term-ordering?
> Do we want to allow users to make a term-orderin... - 11:20 Bug #821: IsTermOrdering
- Does the 0x0 matrix define a term-ordering?
Do we want to allow users to make a term-ordering on 0 indets?
JAA think...
Also available in: Atom