Activity
From 10 Oct 2014 to 08 Nov 2014
04 Nov 2014
-
19:02 0.25 hour (Bug #232 (New): No test for QBGenerator)
- Change name?
-
17:46 0.25 hour (Feature #645 (Rejected): Automatic mapping of RingElem: user selectable at run-time (GlobalManager?))
- initial comments
-
11:34 0.25 hour (Feature #645 (Rejected): Automatic mapping of RingElem: user selectable at run-time (GlobalManager?))
- initial comments
30 Oct 2014
-
15:50 0.10 hour (Design #642 (Closed): Move code in test file into namespace CoCoA)
- An idea
-
15:48 1.00 hour (Design #642 (Closed): Move code in test file into namespace CoCoA)
- An idea
-
14:22 0.75 hour (Design #642 (Closed): Move code in test file into namespace CoCoA)
- Progress
29 Oct 2014
-
13:38 0.25 hour (Feature #644 (New): Buchberger-Moeller: add option to stop as soon as 1 poly has been found)
- Is this what we really want?
-
11:58 0.50 hour (Design #641 (Closed): Clean test-FreeModule1)
-
11:44 0.25 hour (Design #641 (Closed): Clean test-FreeModule1)
- Also...
-
11:30 0.25 hour (Bug #640 (New): What is test-Dynamic1.C)
- Ignored
28 Oct 2014
-
16:11 0.50 hour (Design #619 (Closed): Modulus (for CRTMill) ambiguous)
- Impl'ed
-
15:44 0.25 hour (Design #619 (Closed): Modulus (for CRTMill) ambiguous)
- New names
-
15:34 0.25 hour (Feature #639 (New): Shadow CoCoA namespace to help guarantee portability (without ambiguity))
- Perhaps not so important
-
15:26 0.50 hour (Feature #639 (New): Shadow CoCoA namespace to help guarantee portability (without ambiguity))
- Is it worth it?
27 Oct 2014
-
12:44 0.10 hour (Feature #638 (Closed): Time limit: let user specify time limit for a computation)
- TimeOut
-
12:39 0.25 hour (Feature #638 (Closed): Time limit: let user specify time limit for a computation)
- UI
-
11:34 0.25 hour (Feature #638 (Closed): Time limit: let user specify time limit for a computation)
-
11:08 0.10 hour (Feature #638 (Closed): Time limit: let user specify time limit for a computation)
- KISS
-
11:02 0.10 hour (Feature #638 (Closed): Time limit: let user specify time limit for a computation)
- Technical issues
-
10:51 0.50 hour (Feature #638 (Closed): Time limit: let user specify time limit for a computation)
- Clarification
-
10:03 0.25 hour (Bug #631 (Closed): Ambiguous: rank for matrix (in ex-matrix1.C))
- CoCoALib tests
22 Oct 2014
-
14:39 0.50 hour (Bug #593 (Closed): Temporary directories used during configuration)
- More convincing
14 Oct 2014
-
21:34 0.10 hour (Design #619 (Closed): Modulus (for CRTMill) ambiguous)
- Put code in namespace CoCoA
-
18:26 0.25 hour (Design #619 (Closed): Modulus (for CRTMill) ambiguous)
- Trouble ahead?
-
18:18 0.50 hour (Design #619 (Closed): Modulus (for CRTMill) ambiguous)
- Change name?
-
21:32 0.25 hour (Bug #631 (Closed): Ambiguous: rank for matrix (in ex-matrix1.C))
- Another idea
-
21:25 0.25 hour (Bug #631 (Closed): Ambiguous: rank for matrix (in ex-matrix1.C))
- Proper solution
-
20:03 1.50 hour (Bug #631 (Closed): Ambiguous: rank for matrix (in ex-matrix1.C))
- Changed name
-
18:23 0.25 hour (Bug #631 (Closed): Ambiguous: rank for matrix (in ex-matrix1.C))
- Explanation
13 Oct 2014
-
23:00 0.25 hour (Bug #593 (Closed): Temporary directories used during configuration)
- Suggestion
-
20:47 0.25 hour (Feature #630 (Closed): Add graeffe function?)
- For polynomial systems
Also available in: Atom