Activity
From 13 Oct 2014 to 11 Nov 2014
11 Nov 2014
-
23:20 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...
-
- 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...
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 ...
-
17:24 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... -
- 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...
-
- 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...
22 Oct 2014
-
- Christof reported problems with my one of my shell scripts which uses the @trap@ facility to guarantee proper cleanin...
15 Oct 2014
-
- John Abbott wrote:
> After speaking to Anna by phone, I have changed the name of @rank@ into @rk@.
>
> I'm ready ... -
- John Abbott wrote:
> I now believe the ambiguity would disappear if the entire function were placed inside @namespac...
14 Oct 2014
-
- (see #631 comment 5) I think the problem goes away if the code is put inside @namespace CoCoA@.
-
- Assuming my explanation in the _correction_ in comment 1 is correct, then the STL people could break our code at any ...
-
- John Abbott wrote:
> I think the C++ rules will compel us to change name -- asking the user to write @CoCoA::modulus... -
- I think the C++ rules will compel us to change name -- asking the user to write @CoCoA::modulus@ every time is not ac...
-
- I now believe the ambiguity would disappear if the entire function were placed inside @namespace CoCoA@. We could mo...
-
- Strictly speaking the proper solution to the problem is to put a @using CoCoA::rank;@ inside the function which will ...
-
- 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... -
- John Abbott wrote:
> I think the problem arises because @rank(M)@ entails a user type conversion from @matrix@ to @C... -
- I think the problem arises because @rank(M)@ entails a user type conversion from @matrix@ to @ConstMatrixView@.
@s...
13 Oct 2014
-
- I now think that a good solution would be to put tmpdirs in @configuration/TMP/@. That way they can all be "cleaned"...
-
- 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