Activity
From 01 Nov 2014 to 30 Nov 2014
21 Nov 2014
- 16:15 Feature #651: Optimized algorithms for implicitization (slicing algorithm, elim, subalgebra..)
- John Abbott wrote:
> Anna did report disappointing performance from the initial implementation -- she will investiga... - 11:32 Feature #651: Optimized algorithms for implicitization (slicing algorithm, elim, subalgebra..)
- At a meeting yesterday it was decided that effort should be put into developing/refining *@ImplicitDirectWithCond@*. ...
- 11:30 Feature #651: Optimized algorithms for implicitization (slicing algorithm, elim, subalgebra..)
- The very latest version of @ImplicitByPoints3@ does occasionally go a little faster than @ImplicitDirectLPP2@, but it...
17 Nov 2014
- 16:04 Design #649: Make SmallFpImpl safer to use
- I've just wasted a good hour trying to figure out why my new code was about 10% slower than the old code.
The reason... - 11:54 Feature #651: Optimized algorithms for implicitization (slicing algorithm, elim, subalgebra..)
- JAA has implemented in C++/CoCoALib (first prototypes of): @ImplicitDirect@ (with variants @LPP@ and @WithCond@), als...
- 11:38 Bug #648 (Closed): QBGenerator crashes
13 Nov 2014
- 13:44 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 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...
- 11:30 Design #649: Make SmallFpImpl safer to use
- 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...
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...
- 23:13 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 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 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 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 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 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 Bug #648: QBGenerator crashes
- Trying to find a simple program which produces the bug; first attempts failed.
Also trying @valgrind@.
- 21:22 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 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 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 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 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...
04 Nov 2014
- 19:02 Bug #232: No test for QBGenerator
- I notice that there are two mem fns with the following names: @myCornerPPIntoQB@ and @myCornerIntoAvoidSet@. Shouldn...
- 17:46 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 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 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 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...
Also available in: Atom