Activity
From 16 Oct 2014 to 14 Nov 2014
13 Nov 2014
-
13:44 CoCoALib Feature #651 (In Progress): Optimized algorithms for implicitization (slicing algorithm, elim, subalgebra..)
- (may keywords in the title to simplify future searches ;-)
Investigate new algorithms for implicitization, i.e. fi...
12 Nov 2014
-
19:03 CoCoALib Design #649: Make SmallFpImpl safer to use
- I have implemented both (1) and (2). A quick comparison suggests that they are roughly equal in speed (but I'm still...
-
- It is not true that approach (1) allows the user to use 0 and 1 as arguments to the memfns. In fact, the only use in...
-
- I have already reported by phone that there is a problem (with @SourceAnna@) on 32-bit Linux.
On my 64-bit MacOSX ... -
- Sometimes the CoCoA-5 test @SourceAnna@ fails (on 64-bit MacOSX).
The problem appears when executing the line:
<p...
11 Nov 2014
-
- I have had further problems with @trap@ in the script @gmp-try-default.sh@ on some Linux boxes. This is further moti...
-
- Here are 2 candidate solutions:
# use a new type for the values (_e.g._ a class or struct containing the currently us... -
- The problem is that all the member functions accept any integral type, but most should accept only @SmallFpImpl::valu...
-
- After having wasted an hour or two tracking down a bug (in code which looked "obviously correct"), I want to make @Sm...
-
- I think I may have solved the issue: my code wrote one place beyond the end of a vector (and presumably this overwrot...
-
- 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... -
- Still not tracked down the bug :-(
The bug vanishes when I use @valgrind@ -- how can that be?
The bug persists ...
10 Nov 2014
-
- Trying to find a simple program which produces the bug; first attempts failed.
Also trying @valgrind@.
-
- I have a program which causes @QBGenerator@ to produce a SEGV.
Even just printing the @QBGenerator@ causes a SEGV:
... -
- Are the concepts of *free module with shifts* and *free module without shifts* distinct?
Note that the notion of s... -
- Currently I'm considering offer two ways of "creating" a free module:
# "create" a unique free module (of dim @n@ ov... -
- After speaking to Anna... here are some aspects to consider:
* a major use of modules in CoCoA is for syzygy modules... -
- Discuss having unique copies of free modules; or at least that the default creation mechanism should not produce dist...
-
- I propose putting all the technical discussion in #647, a parallel issue to this one (since practically all the real ...
-
- A recent bug report from Oneto suggests that it is surprising/unnatural that @NewFreeModule@ should create distinct (...
07 Nov 2014
-
- While talking to Anna the following idea came up. Non-simple elements of coefficient rings are printed inside bracke...
04 Nov 2014
-
- I notice that there are two mem fns with the following names: @myCornerPPIntoQB@ and @myCornerIntoAvoidSet@. Shouldn...
-
- What I should have said originally is: *if* _we decide to do automatic mapping of @RingElem@ in CoCoALib_ *then* _we ...
-
- I'm a bit uneasy about this....
Making the automatic mapping working generally would involve a lot of code.... or ar... -
- Since the flag would have to be global, it makes sense to put it inside the @GlobalManager@.
If the flag is simply... -
- I suggest that in CoCoALib we give the user the option to have automatic mapping of @RingElem@ values.
For instanc...
30 Oct 2014
-
- I'm wondering whether it may be better/cleaner/clearer to move @using std::cerr@ to inside @main@. It's not importan...
-
- 20141030 JAA has done @test-[A-I]*.C@
29 Oct 2014
-
- I wonder whether this proposal is actually what we want.
I imagine that the intended use is:
# generate (conceptu... -
- Add option to compute just the first gen of an ideal of points. This may be useful for computing implicitizations (f...
-
- @GenRepr@ should not give error in this instance:...
-
- done:
test-FreeModule1 does not print
test-FreeModule2 prints because it calls the same functions with different co... -
- Similar comment applies to @test-FreeModule2.C@
-
- @test-FreeModule1@ prints out many values rather than checking that the result is as expected.
-
- For improved portability/robustness, move all code (except @main@) in test files into @namespace CoCoA@.
-
- Note that @test-Dynamic1.C@ is not listed in the @Makefile@, and in its current form does not compile. Also its name...
-
- It is a test for "dynamic-Groebner" written by Massimo Caboara a long time ago.
It is worth maintaining it because I... -
- 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
-
- Implemented; all tests pass. Updated doc.
Oddly, no tests called these fns; nor any examples -- rectify?
Check... -
- As Anna pointed out the names *@CombinedModulus@* and *@CombinedResidue@* are very clear (though long). Since it see...
-
- Perhaps it is not so crucial to do this; or, at least, there may be a good compromise.
It is irritating when an am... -
- I don't know if this would really be worth the trouble.
I'm not even entirely sure that it would give the guarante... -
- Some problems of ambiguity in the CoCoALib source code have recently arisen. They have appeared because recent versi...
27 Oct 2014
-
- I'm not sure about your @TimeOut@ proposal. We should talk about details before making any decision. I'm inclined t...
-
- I agree that GBasis computation is the obvious candidate (are there any others?).
I am unclear about whether the tim... -
- John Abbott wrote:
> I believe it would be simplest to start with time limits being allowed only for certain functio... -
- I believe it would be simplest to start with time limits being allowed only for certain functions. Amongst other thi...
-
- There is a built-in system "timer/alarm" mechanism which works via signals; I do not know much about this (incl. how...
-
- What exactly does Robbiano want?
* setting a time limit should be accessible from CoCoA-5
* should it be a general ... -
- Robbiano asked whether it would be possible to allow a user to specify a (CPU) time limit for a computation.
Discuss! -
- In comment 5 I suggesting putting all code in namespace @CoCoA@; perhaps we should try doing this for some CoCoALib t...
25 Oct 2014
-
- Here is a short session valid with the current version of CoCoA-5...
23 Oct 2014
-
- 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... -
- Suppose we allow automatic mapping of ringelems into superrings.
Consider the following scenario:... -
- Consider the following scenario:...
-
- The @use@ command assigns the top-level variables whose names match those of the symbols in the ring. The assigned v...
-
- At the moment the idea of automatically "mapping down" ring elements makes me feel uneasy (perhaps solely because I h...
-
- The description says it all, but I prefer phrase it also like this:...
-
- I note that this proposal would still produce an error if one tries to compute:...
-
- I think it has just been forgotten; it seems like a good idea to me. Indeed now that direct printing produces a very...
-
- I have implemented in CoCoALib ...
22 Oct 2014
-
- Robbiano's scenario was the following... a bit simplified:...
-
- If we decide to allow automatic mapping of @RingElem@ values, Anna suggests that only simple/single values can be aut...
-
- My previous comment convinces me that it is not feasible to make @a@ have the value of the symbol @a@ in the smallest...
-
- There is a potential problem with my suggestion of symbols being mapped into the smallest containing subring. In the...
-
- The problem was highlighted when Robbiano wanted to multiply a matrix (over @K@) by @a@; CoCoA-5 gave a _mixed rings_...
-
- Consider the following mini-session...
-
- Christof reported problems with my one of my shell scripts which uses the @trap@ facility to guarantee proper cleanin...
Also available in: Atom