Activity
From 02 Oct 2014 to 31 Oct 2014
30 Oct 2014
- 15:50 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 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 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 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...
- 11:58 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 Design #641: Clean test-FreeModule1
- Similar comment applies to @test-FreeModule2.C@
- 11:28 Design #641 (Closed): Clean test-FreeModule1
- @test-FreeModule1@ prints out many values rather than checking that the result is as expected.
- 11:47 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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...
22 Oct 2014
- 14:39 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 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 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 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 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 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 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 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 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 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 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 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 Oct 2014
- 23:00 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 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