Activity
From 13 Oct 2014 to 11 Nov 2014
11 Nov 2014
- 23:20 CoCoALib Bug #593: Temporary directories used during configuration
- I have had further problems with @trap@ in the script @gmp-try-default.sh@ on some Linux boxes. This is further moti...
- 23:13 CoCoALib Design #649 (In Progress): Make SmallFpImpl safer to use
- Here are 2 candidate solutions:
# use a new type for the values (_e.g._ a class or struct containing the currently us... - 23:03 CoCoALib Design #649: Make SmallFpImpl safer to use
- The problem is that all the member functions accept any integral type, but most should accept only @SmallFpImpl::valu...
- 22:58 CoCoALib Design #649 (Closed): Make SmallFpImpl safer to use
- After having wasted an hour or two tracking down a bug (in code which looked "obviously correct"), I want to make @Sm...
- 14:13 CoCoALib Bug #648 (Resolved): QBGenerator crashes
- I think I may have solved the issue: my code wrote one place beyond the end of a vector (and presumably this overwrot...
- 12:09 CoCoALib Bug #648: QBGenerator crashes
- The bug did not show up on a (32-bit) Linux VM; nor on a 32-bit Linux netbook.
The bug does not arise when compile... - 09:50 CoCoALib Bug #648: QBGenerator crashes
- Still not tracked down the bug :-(
The bug vanishes when I use @valgrind@ -- how can that be?
The bug persists ...
10 Nov 2014
- 21:43 CoCoALib Bug #648: QBGenerator crashes
- Trying to find a simple program which produces the bug; first attempts failed.
Also trying @valgrind@.
- 21:22 CoCoALib Bug #648 (Closed): QBGenerator crashes
- I have a program which causes @QBGenerator@ to produce a SEGV.
Even just printing the @QBGenerator@ causes a SEGV:
... - 16:55 CoCoALib Design #647: Unique copies of free modules?
- Are the concepts of *free module with shifts* and *free module without shifts* distinct?
Note that the notion of s... - 16:51 CoCoALib Design #647: Unique copies of free modules?
- Currently I'm considering offer two ways of "creating" a free module:
# "create" a unique free module (of dim @n@ ov... - 16:45 CoCoALib Design #647: Unique copies of free modules?
- After speaking to Anna... here are some aspects to consider:
* a major use of modules in CoCoA is for syzygy modules... - 16:36 CoCoALib Design #647 (New): Unique copies of free modules?
- Discuss having unique copies of free modules; or at least that the default creation mechanism should not produce dist...
- 16:42 CoCoA-5 Design #646: Unique copies of free modules?
- I propose putting all the technical discussion in #647, a parallel issue to this one (since practically all the real ...
- 16:33 CoCoA-5 Design #646 (New): Unique copies of free modules?
- A recent bug report from Oneto suggests that it is surprising/unnatural that @NewFreeModule@ should create distinct (...
07 Nov 2014
- 16:49 CoCoA-5 Design #637: Undesirable consequence of automatic mapping of RingElems?
- While talking to Anna the following idea came up. Non-simple elements of coefficient rings are printed inside bracke...
04 Nov 2014
- 19:02 CoCoALib Bug #232: No test for QBGenerator
- I notice that there are two mem fns with the following names: @myCornerPPIntoQB@ and @myCornerIntoAvoidSet@. Shouldn...
- 17:46 CoCoALib Feature #645: Automatic mapping of RingElem: user selectable at run-time (GlobalManager?)
- What I should have said originally is: *if* _we decide to do automatic mapping of @RingElem@ in CoCoALib_ *then* _we ...
- 17:24 CoCoALib Feature #645: Automatic mapping of RingElem: user selectable at run-time (GlobalManager?)
- I'm a bit uneasy about this....
Making the automatic mapping working generally would involve a lot of code.... or ar... - 11:34 CoCoALib Feature #645: Automatic mapping of RingElem: user selectable at run-time (GlobalManager?)
- Since the flag would have to be global, it makes sense to put it inside the @GlobalManager@.
If the flag is simply... - 11:28 CoCoALib Feature #645 (Rejected): Automatic mapping of RingElem: user selectable at run-time (GlobalManager?)
- I suggest that in CoCoALib we give the user the option to have automatic mapping of @RingElem@ values.
For instanc...
30 Oct 2014
- 15:50 CoCoALib Design #642: Move code in test file into namespace CoCoA
- I'm wondering whether it may be better/cleaner/clearer to move @using std::cerr@ to inside @main@. It's not importan...
- 14:22 CoCoALib Design #642 (In Progress): Move code in test file into namespace CoCoA
- 20141030 JAA has done @test-[A-I]*.C@
29 Oct 2014
- 13:38 CoCoALib Feature #644: Buchberger-Moeller: add option to stop as soon as 1 poly has been found
- I wonder whether this proposal is actually what we want.
I imagine that the intended use is:
# generate (conceptu... - 12:43 CoCoALib Feature #644 (New): Buchberger-Moeller: add option to stop as soon as 1 poly has been found
- Add option to compute just the first gen of an ideal of points. This may be useful for computing implicitizations (f...
- 12:39 CoCoA-5 Bug #643 (Closed): GenRepr fails if there are zero generators
- @GenRepr@ should not give error in this instance:...
- 11:58 CoCoALib Design #641 (Feedback): Clean test-FreeModule1
- done:
test-FreeModule1 does not print
test-FreeModule2 prints because it calls the same functions with different co... - 11:44 CoCoALib Design #641: Clean test-FreeModule1
- Similar comment applies to @test-FreeModule2.C@
- 11:28 CoCoALib Design #641 (Closed): Clean test-FreeModule1
- @test-FreeModule1@ prints out many values rather than checking that the result is as expected.
- 11:47 CoCoALib Design #642 (Closed): Move code in test file into namespace CoCoA
- For improved portability/robustness, move all code (except @main@) in test files into @namespace CoCoA@.
- 11:30 CoCoALib Bug #640: What is test-Dynamic1.C
- Note that @test-Dynamic1.C@ is not listed in the @Makefile@, and in its current form does not compile. Also its name...
- 11:27 CoCoALib Bug #640: What is test-Dynamic1.C
- It is a test for "dynamic-Groebner" written by Massimo Caboara a long time ago.
It is worth maintaining it because I... - 11:10 CoCoALib Bug #640 (New): What is test-Dynamic1.C
- I'm updating the tests manually.
What is the file @test-Dynamic1.C@?
Who wrote it? When?
If we want to keep i...
28 Oct 2014
- 16:11 CoCoALib Design #619 (Feedback): Modulus (for CRTMill) ambiguous
- Implemented; all tests pass. Updated doc.
Oddly, no tests called these fns; nor any examples -- rectify?
Check... - 15:44 CoCoALib Design #619: Modulus (for CRTMill) ambiguous
- As Anna pointed out the names *@CombinedModulus@* and *@CombinedResidue@* are very clear (though long). Since it see...
- 15:34 CoCoALib Feature #639: Shadow CoCoA namespace to help guarantee portability (without ambiguity)
- Perhaps it is not so crucial to do this; or, at least, there may be a good compromise.
It is irritating when an am... - 15:26 CoCoALib Feature #639: Shadow CoCoA namespace to help guarantee portability (without ambiguity)
- I don't know if this would really be worth the trouble.
I'm not even entirely sure that it would give the guarante... - 15:21 CoCoALib Feature #639 (New): Shadow CoCoA namespace to help guarantee portability (without ambiguity)
- Some problems of ambiguity in the CoCoALib source code have recently arisen. They have appeared because recent versi...
27 Oct 2014
- 12:44 CoCoALib Feature #638: Time limit: let user specify time limit for a computation
- I'm not sure about your @TimeOut@ proposal. We should talk about details before making any decision. I'm inclined t...
- 12:39 CoCoALib Feature #638 (In Progress): Time limit: let user specify time limit for a computation
- I agree that GBasis computation is the obvious candidate (are there any others?).
I am unclear about whether the tim... - 11:34 CoCoALib Feature #638: Time limit: let user specify time limit for a computation
- John Abbott wrote:
> I believe it would be simplest to start with time limits being allowed only for certain functio... - 11:08 CoCoALib Feature #638: Time limit: let user specify time limit for a computation
- I believe it would be simplest to start with time limits being allowed only for certain functions. Amongst other thi...
- 11:02 CoCoALib Feature #638: Time limit: let user specify time limit for a computation
- There is a built-in system "timer/alarm" mechanism which works via signals; I do not know much about this (incl. how...
- 10:51 CoCoALib Feature #638: Time limit: let user specify time limit for a computation
- What exactly does Robbiano want?
* setting a time limit should be accessible from CoCoA-5
* should it be a general ... - 10:45 CoCoALib Feature #638 (Closed): Time limit: let user specify time limit for a computation
- Robbiano asked whether it would be possible to allow a user to specify a (CPU) time limit for a computation.
Discuss! - 10:03 CoCoALib Bug #631: Ambiguous: rank for matrix (in ex-matrix1.C)
- In comment 5 I suggesting putting all code in namespace @CoCoA@; perhaps we should try doing this for some CoCoALib t...
25 Oct 2014
- 17:06 CoCoA-5 Design #637: Undesirable consequence of automatic mapping of RingElems?
- Here is a short session valid with the current version of CoCoA-5...
23 Oct 2014
- 22:23 CoCoA-5 Design #637 (In Progress): Undesirable consequence of automatic mapping of RingElems?
- I think the values of @deg(A)@ and @deg(B)@ are well defined.
If we have @not(deg(A) = deg(B))@ then it would be q... - 22:12 CoCoA-5 Design #637 (Closed): Undesirable consequence of automatic mapping of RingElems?
- Suppose we allow automatic mapping of ringelems into superrings.
Consider the following scenario:... - 22:05 CoCoA-5 Design #636: Distinguish indets from symbols in coeffring in Use command
- Consider the following scenario:...
- 18:42 CoCoA-5 Design #636 (Rejected): Distinguish indets from symbols in coeffring in Use command
- The @use@ command assigns the top-level variables whose names match those of the symbols in the ring. The assigned v...
- 18:37 CoCoA-5 Design #635: Automatic mapping of RingElem (in operation with a compound value)
- At the moment the idea of automatically "mapping down" ring elements makes me feel uneasy (perhaps solely because I h...
- 12:57 CoCoA-5 Design #635: Automatic mapping of RingElem (in operation with a compound value)
- The description says it all, but I prefer phrase it also like this:...
- 12:32 CoCoA-5 Design #635 (In Progress): Automatic mapping of RingElem (in operation with a compound value)
- I note that this proposal would still produce an error if one tries to compute:...
- 12:21 CoCoA-5 Support #548: Printing rings with ID
- I think it has just been forgotten; it seems like a good idea to me. Indeed now that direct printing produces a very...
- 11:08 CoCoA-5 Support #548: Printing rings with ID
- I have implemented in CoCoALib ...
22 Oct 2014
- 20:11 CoCoA-5 Design #635: Automatic mapping of RingElem (in operation with a compound value)
- Robbiano's scenario was the following... a bit simplified:...
- 20:07 CoCoA-5 Design #635 (Closed): Automatic mapping of RingElem (in operation with a compound value)
- If we decide to allow automatic mapping of @RingElem@ values, Anna suggests that only simple/single values can be aut...
- 20:02 CoCoA-5 Design #634 (Rejected): Symbol in the coeff ring
- My previous comment convinces me that it is not feasible to make @a@ have the value of the symbol @a@ in the smallest...
- 18:35 CoCoA-5 Design #634: Symbol in the coeff ring
- There is a potential problem with my suggestion of symbols being mapped into the smallest containing subring. In the...
- 16:11 CoCoA-5 Design #634: Symbol in the coeff ring
- The problem was highlighted when Robbiano wanted to multiply a matrix (over @K@) by @a@; CoCoA-5 gave a _mixed rings_...
- 16:08 CoCoA-5 Design #634 (Rejected): Symbol in the coeff ring
- Consider the following mini-session...
- 14:39 CoCoALib Bug #593: Temporary directories used during configuration
- Christof reported problems with my one of my shell scripts which uses the @trap@ facility to guarantee proper cleanin...
15 Oct 2014
- 12:13 CoCoALib Bug #631: Ambiguous: rank for matrix (in ex-matrix1.C)
- John Abbott wrote:
> After speaking to Anna by phone, I have changed the name of @rank@ into @rk@.
>
> I'm ready ... - 12:06 CoCoALib Bug #631: Ambiguous: rank for matrix (in ex-matrix1.C)
- John Abbott wrote:
> I now believe the ambiguity would disappear if the entire function were placed inside @namespac...
14 Oct 2014
- 21:34 CoCoALib Design #619: Modulus (for CRTMill) ambiguous
- (see #631 comment 5) I think the problem goes away if the code is put inside @namespace CoCoA@.
- 18:26 CoCoALib Design #619: Modulus (for CRTMill) ambiguous
- Assuming my explanation in the _correction_ in comment 1 is correct, then the STL people could break our code at any ...
- 18:22 CoCoALib Design #619: Modulus (for CRTMill) ambiguous
- John Abbott wrote:
> I think the C++ rules will compel us to change name -- asking the user to write @CoCoA::modulus... - 18:18 CoCoALib Design #619 (In Progress): Modulus (for CRTMill) ambiguous
- I think the C++ rules will compel us to change name -- asking the user to write @CoCoA::modulus@ every time is not ac...
- 21:32 CoCoALib Bug #631: Ambiguous: rank for matrix (in ex-matrix1.C)
- I now believe the ambiguity would disappear if the entire function were placed inside @namespace CoCoA@. We could mo...
- 21:25 CoCoALib Bug #631: Ambiguous: rank for matrix (in ex-matrix1.C)
- Strictly speaking the proper solution to the problem is to put a @using CoCoA::rank;@ inside the function which will ...
- 20:03 CoCoALib Bug #631: Ambiguous: rank for matrix (in ex-matrix1.C)
- After speaking to Anna by phone, I have changed the name of @rank@ into @rk@.
I'm ready to do CVS check in, but fi... - 18:26 CoCoALib Bug #631: Ambiguous: rank for matrix (in ex-matrix1.C)
- John Abbott wrote:
> I think the problem arises because @rank(M)@ entails a user type conversion from @matrix@ to @C... - 18:23 CoCoALib Bug #631 (In Progress): Ambiguous: rank for matrix (in ex-matrix1.C)
- I think the problem arises because @rank(M)@ entails a user type conversion from @matrix@ to @ConstMatrixView@.
@s... - 13:05 CoCoA-5 Feature #633 (New): New operations? ScalarProduct(MODULELEM,LIST), MATRIX * MODULELEM
- I think that ScalarProduct(MODULELEM,LIST) is OK
but MATRIX * MODULELEM may be ambiguous (row or col?)
For sure we ...
13 Oct 2014
- 23:00 CoCoALib Bug #593 (In Progress): Temporary directories used during configuration
- I now think that a good solution would be to put tmpdirs in @configuration/TMP/@. That way they can all be "cleaned"...
- 20:47 CoCoALib Feature #630: Add graeffe function?
- If I recall correctly, Bini said that graeffe can also be done for polynomial systems. Right now I cannot see when i...
Also available in: Atom