Activity

From 10 Nov 2014 to 09 Dec 2014

23:02 Feature #651: Optimized algorithms for implicitization (slicing algorithm, elim, subalgebra..): One problem with @ImpliciDirectWithCond@ is that the normal form computations take too long. Here is an idea which _... John Abbott
16:22 Feature #437: MemPool: order free blocks?: It seems the correct (portable) way to sort a @vector<void*>@ is to use @sort(v.begin(), v.end(), std::less)@.
Apa... John Abbott

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... Anna Maria Bigatti
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@*. ... John Abbott
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... John Abbott

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... John Abbott
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... John Abbott
11:38 Bug #648 (Closed): QBGenerator crashes: John Abbott

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... Anna Maria Bigatti

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... John Abbott
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... John Abbott

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... John Abbott
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... John Abbott
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... John Abbott
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... John Abbott
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... John Abbott
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... John Abbott
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 ... John Abbott

21:43 Bug #648: QBGenerator crashes: Trying to find a simple program which produces the bug; first attempts failed.
Also trying @valgrind@.
John Abbott
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:
... John Abbott
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... John Abbott
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... John Abbott
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... John Abbott
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... John Abbott

Also available in: Atom

CoCoA » CoCoALib