Activity
From 07 Jul 2014 to 05 Aug 2014
01 Aug 2014
-
16:25 CoCoALib Feature #62 (Closed): polynomial coefficient extraction w.r.t. single variable -- dense output
- This has already been done: it is the function *@CoeffVecWRT@*.
Closing.
-
10:56 CoCoA-5 Feature #484: Evaluate in other ring (was called :: in CoCoA-4)
- the CoCoA-4 operator "::" is now in another specific issue.
For the time being I think that *ReadExpr* may be good e... -
-
- CoCoA-4 has the *@::@* operator which evaluated expressions in a given ring:...
-
- Everything for the release
finalize cvs
make
make doc
make ManExamples
in snapshot dir:
cd src/CoCoA-5/re... -
- fixed ManExamples (and fixed code for checking ;-)
-
-
- Everything related to making a CoCoALib release:
finalize
make veryclean; make (full make, with all tests and ex... -
- Done, tested, documented
Different from the cocoa-4 version: more flexible (see manual) -
- Redesign CoCoA-4 function CheckArgTypes (for checking argument types, of course...)
31 Jul 2014
-
finalize: done
tests - make valgrind: OK
create snapshot: not yet (just missing VectorOperations.txt)
updated we...-
-
- Renaming done: OrdMat, GradingMat (2014-07)
Moving the MatrixView proposal into another issue -
- Postponing to after Seoul as there are some unresolved aspects.
-
- We have chosen the name *@OrdMat@* (and mem fn called *@myOrdMatCopy@*). Also added this fn for @PPMonoid@ and @Spar...
-
- The function *OrdMat* needs to create a new copy of the ordering matrix because not all @PPOrdering@ objects actually...
-
- Even though I had closed this issue saying:
> Even though CoCoAHelp.xml isn't all written like that (too dangerous t... -
- @Christof: you've done a good job, I think this issue can be closed now. Closing!
-
-
-
- Time is tight. Since it is just a name change, no real need to stay in feedback for any length of time. Closing.
-
- The final (hasty?) decision is the call the file *@VectorOperations.H@* (even though most functions in it apply to ot...
-
- Duplicates #169: "Font for parameters in manual".
Design is all set there.
Closing this issue. -
- As said in another issue:
- parameters should have the same name as in <syntax>
- <syntax> should be moved before <... -
- Is the new approach in BuiltInFunctions good enough?
I think so: it is not a one-liner but it's very readable (look f... -
- Now all functions work. A proper clean-up and re-design is in another issue.
-
- I think it is all done (naive resolutions work).
If some wrong aspect arises it'll become a new specific issue. -
- Christof has a valid point about the mnemonic value of including *@view@* in the name, but Anna points out that none ...
-
- Currently @LongRange@ resides in @utils.H@; it is the only function there that requires inclusion of the standard hea...
-
- Christof! we should talk about this in Seoul.
-
-
-
- Most of the information is already in the documentation for @PPOrdering@.
So it is mainly a matter of redesigning it...
30 Jul 2014
-
- We are also working an efficient algorithm for implicitization.
Keep that in mind for this issue, or make a new issue. -
- There are many tools to deal with subalgebras (see @toric@ and @normaliz@), so it would make sense to design a nice i...
-
- Resumed package (slight design change, documented)
It will be imrpoved, but that's beyond this task scope.
-
- The function in CoCoA-5 is already done and called @RingSet@ (see manual) but I'm not happy with the name: should I c...
-
- I note that I have just(20140730) checked in an update which introduces @RingOf@ for matrices, modules and ideals.
-
- Checked in. Updated documentation. Everything works --> feedback.
-
- I have now changed the name @BaseRing@ into @RingOf@ for matrices and modules.
I have changed @AmbientRing@ into @Ri... -
- Everything related to making a CoCoALib release:
finalize
make veryclean; make (full make, with all tests and ex... -
29 Jul 2014
-
- the error message was indeed a bit puzzling in some cases now it is:...
-
- Giulia's problem could be neatly resolved by allowing the following syntax *@L[2..4]@* to mean @[L[k] | k in 2..4]@. ...
-
- My main concern is the (possibly) unexpected behaviour illustrated in example *@(B)@* in comment 1. However, for a l...
-
- The main action taken was to clarify the manual entry for ".."; it is now quite clear, and even mentions Giulia's inc...
-
- I suggest to reject this issue.
@A..B@ works for A and B integers or indeterminates in the order of their definition... -
- Christof has reported no problems, so closing.
-
- tested also...
-
-
28 Jul 2014
-
- This is no longer a problem (after resolving issue #190). Closing.
PS I have added the example to @exbugs.cocoa5@. -
- Anna confirmed that it works fine on her machine, so I have checked in (incl 2 new tests)
Still need to update the... -
-
17:45 CoCoALib Feature #554: CoCoALib-Normaliz interface: cannot print a cone
- Yes.
-
- *@Christof:* can we close this issue now?
-
- Almost certainly part of the problem is that @ar ru@ on Mac OS X updates the mtime of the archive even when the archi...
-
-
- Compilations flags are given by @VersionInfo()@
-
- The clean solution would be to have @intersect@ doing what @Intersection@ used to do.
Problem is @intersect@ for IDE... -
- Documented as obsolescent
-
- It is now officially documented as OBSOLETE, so I close this issue.
-
- the general @init@ file now works well.
I don't think there is a particular need for a user init file.
I regard thi... -
-
-
- Syz for modules with non-homogeneous input.
Maybe the CoCoALib code works, but....
needs proper testing.... -
- I don't think we should eliminate it.
In time, we can see what can be useful and advertized (low priority) -
- Undecided, needs more thinking. Not urgent
-
-
- There are a few more @WrongTypeException@ left in @Interpreter.C@.
Those are of a slightly different nature and shou... -
- Changed also also PtrCast into RefTo<..>
cvs-ed
27 Jul 2014
-
- No complaints from anyone after checking in, so I regard the idea as safe and sound.
Postponing to "after Seoul" b... -
- I have implemented the changes suggested in my previous comment (_i.e._ rings no longer store cached copies of their ...
25 Jul 2014
-
- added templates for @RefTo<..>@.
-
- Now all @switch@ following @EvalArgAsT1or...@ have a default case giving and error.
This is good for maintenance: if... -
- Another possible name is *@UnwrapBigInt@*. I think it conveys the idea that the @BigInt@ is hidden inside the object...
-
- First pass is mostly done (BigIntValue --> INT, and similar).
I'm a bit undecided about a few other types like @OSTR... -
- John Abbott wrote:
> I'm not entirely convinced by the names @PtrCastIDEAL@ etc.
> It is true that the arg is a "po... -
- I started the change: there is no name clash problem with the class @INT@ :-)
... at least with gcc :-/
Anyway: in ca... -
- I think the real problem is that some rings store certain @RingHom@ values inside themselves (thus creating an indire...
-
- John Abbott wrote:
> I'd like a name which more clearly expresses that it is for converting "old" C4 code to C5.
Ind...
24 Jul 2014
-
- Certainly the excerpt from @BuiltinOneLiners@ is very clear.
We have already spoken about the use of @default@ in ... -
- I'd like a name which more clearly expresses that it is for converting "old" C4 code to C5. We may even need some hi...
-
- I went through the translation table and I updated it (almost complete now :-)
.... I was just wondering: should w... -
- I found where (I looked for @TT_FOR@, in @Parse.C@) to give a proper error (if we decide to disable it) or to enable ...
-
- From Alexandru Costantinescu (who used @source@ in loops in cocoa-4)
> I am using a data base of Hilbert functions, ... -
- A few more details: I ran this line...
-
- First functions 2014-07-23
(MinMult, AlgMult, GeoMult, ...) -
- all done
-
- implement function "packages" for list of loaded packages.
23 Jul 2014
-
- This is how some lines in @BuiltinOneLiners@ would look...
-
- In the interpreter (@AST.H@) we have the definition of the classes @BlahValue@, for example
@BigIntValue@, @IdealVal...
22 Jul 2014
-
- all done (also documented)
-
- They should both work both with M in K or in Kx (but not dependent on x)...
-
- Now I'm incline to say "no" and reject the issue: too much hassle for very little use.
@NewSymbol()/NewSymbols(n)@ a... -
- John Abbott wrote:
> This should be easy (but you never know!).
> Moving to after Easter as it is unimportant.
I... -
- This task will never be closed (when would we ever be able to say that? ;-)
So, let's say that we start deleting obs... -
- It should be easy enough to implement if we can get the path of the tests.
This works for me (as an example)... -
- I think it is possible, but tedious work. Is it worth the effort?
-
- now works in some cases, e.g. the one in the description ;-)
More precisely it works if the coefficient ring (of the... -
- At the moment it is only exporting @format@ (which I find quite useful).
I updated @Format/format@ and checked the m... -
- It was easy to fix it for @ideal([x,0,y]);@.
I re-designed the function for @ideal@ a bit.
I renamed @evalArgAsRing... -
- All done (I think).
If/when we make += it'll be easy to search for incr/decr
21 Jul 2014
-
- found the bug: usual ref-count bug on RINGHOM.
Found a few more little bugs in the way ;-)
20 Jul 2014
-
- Improvements needed for the TMP_DIRs used during configuration:
* perhaps use std prefix so that they can all be rem...
18 Jul 2014
-
- John Abbott wrote:
> "incr" is most used in @list.cpkg5@ for @QuickSort1@ and @QuickSortBy1@.
I updated the code ... -
- John Abbott wrote:
> Or maybe a @MemPool@ could count how many new/deletes, and reorder every 65536 calls...
I ha... -
- done
-
- Seems ok on @round@ and @indets@.
(code in @OnlineHelp@ is pretty horrible, but it works) -
- All done (@ascii@, @apply@, @ContentWRT@, @CoefficientWRT@).
Changed priority to high because I'm presenting this in...
17 Jul 2014
-
- After having trouble trying to implement @MatXel@ as a @ConstMatrixView@, I think the design of @ConstMatrixView@ nee...
-
- I have cobbled together a quick impl (practically copied from @IdentityMatImpl@).
It compiles, but I have commented ... -
- The impl for @MatByCols@ was missing; it is there now (quick cut-and-paste job).
Also added an example.
Not closi... -
- The code already checks that the indices are distinct -- no idea when this was impl'd (must have been ages ago).
Clo... -
- No problems after 1 week, so closing.
-
- No problems have appeared. Closing.
-
- Christof made some interesting suggestions:
# copy the free list (or first part of it) into a @vector@, sort the vec... -
- Moving this to after Seoul -- it's too risky to try implementing it in a rush (and then pass sleepless nights trying ...
16 Jul 2014
-
- Done BaseRing. I'll do the rest tomorrow
-
- Not yet entirely convinced about renaming @MakeMatByRows@. It is very similar to @MatByRows@ *but* there is an impor...
-
- should we rename the CoCoA-5 functions -Make-@MatByRows@?
(and move the "Make.." into obsolescent?) -
- The code is already there (and has been for how long?) Fns are @MatByRows@ and @MatByCols@.
I added some documentat... -
- Yes, obsolescent functions should give some warning that they are going to disappear (and presumably what to do inste...
-
- Remember that obsolescent functions should be moved to the package @obsolescent.cpkg5@.
Now they all works silently.... -
- Done. Rule for maintaining it.
(1) Add [OBSOLETE] or [OBSOLESCENT] in the title of obsolete/obsolescent functions, ... -
- I set a manual chapter for these kind of information.
It is called <title>Migrating from CoCoA-4 and keeping up-to... -
- OK
-
- John Abbott wrote:
> I have added a manual page entitled *@updating CoCoA-4 code@*; and another entitled *@CoCoA-4 m... -
- This seems to be *very similar* to the issue #591; I believe they are occurrences of the same phenomenon. Added #591...
-
- Now that I have added checks for new files in @include/CoCoA/@ and in @src/AlgebraicCore/@, it may be less important ...
-
- Clang 3.0 on my computer gives no error.
-
- JAA failed to find anything helpful on the internet.
I'm just hoping that the solution of moving the @#include@ wi... -
- Some versions of g++ (v4.3.2, v4.4.7, v4.6.3) and intel C++ compiler gave errors when compiling @ex-UtilsVector1.C@ i...
-
-
- In cocoa-4 there was a package to compute with subalgebras.
Restore it.
15 Jul 2014
-
- available now for cocoa-5 in package.
Implement it in cocoalib
-
- Done in package.
Implemented only using twin-floats with range [-10^6, 10^6].
No point in offering more flexibility... -
- Resurrect code for "gin", and implement it in cocoalib
-
- John Abbott wrote:
> Christof does not like the name @UtilsTemplates.H@; he suggested @UtilsContainers.H@ or @UtilsVe... -
- Christof does not like the name @UtilsTemplates.H@; he suggested @UtilsContainers.H@ or @UtilsVector.H@ saying that i...
-
- Just not to lose it in a mountain of archived emails, here is the decisive message:...
-
- John Abbott wrote:
> I propose adding @OBSOLETE@ (in capitals) as the first word of the title;
I made it all capi... -
- I think your suggestion is a good one.
I propose adding @OBSOLETE@ (in capitals) as the first word of the title; t... -
- Anna Maria Bigatti wrote:
> I added the key "obsolete".
> now
> [...]
> gives the list of obsolete commands (whi... -
- There were no objections (in the last 24 hours), so I'll check in. If any problems arise, it's trivial to revert the...
-
- cvs-ed
-
- We agreed that it would be handy to have the same interface for
*evalArgAsT1orT2* and *evalArgAsT1orT2orT3*.
The la...
14 Jul 2014
-
- I made some tests (and checked with Hilbert series) and it seems that shifts are done and OK. Added some documentation.
-
- I did this work a long time ago, but never got to deal with the GUI for windows.
No longer makes sense now: going fo... -
- If we use the definition I gave in comment 1 then some twin-float numbers will be recognized as rationals and should ...
-
- resurrected and documented functions *HilbertSeriesShifts* and *HilbertSeriesMultiDeg*
they are just shortcuts to av... -
- @HasUniqueOwner@ should now work with any container. Checked in.
[I haven't actually made any specific tests, but t... -
- I suppose it makes sense to move them... perhaps I'll think about it overnight before acting.
-
- Should also << for vector/list be here?
(now it is in io.H)
-
- Renamed file to *@UtilsTemplate.H@*.
Moved @LexCmp3@ into the file (from @utils.H@).
Added doc (& moved doc for @Le... -
- nice! :-)
some builtin functions are now oneliners
(cvs-ed) -
- After further thought it seemed to make more sense to output the twin-float value as a @MantExp2@ structure, which be...
-
- not final, but much improved (cvs-ed)
-
- I suggest that I check in the version of @BigInt.H@ that I have (with the ctor from @MachineInt@ being implicit). Th...
-
- Implemented; tested; documented; checked in. So status-->FEEDBACK!
-
- I have done a little tidying in @ex-PPVector1.C@.
-
-
- Translate the package @HomomorphismFns.cpkg5@ into CoCoALib.
The related "utility representation" of a homomorphism ... -
- checked in documentation.
Next step (new issue): port it into cocoalib.
-
- *ReadExpr* documented, cvs-ed
(updated entry for RingElem) -
- In CoCoALib we can read expressions from strings with *ReadExpr(RING, STRING)*.
I'm going to add it to cocoa-5 so you...
11 Jul 2014
-
- Advantages:
* in @IntOperations@ and @NumTheory@ we can reduce the number of signatures to some functions (_e.g._ @Is... -
- I've just removed the @explicit@ keyword from the @BigInt@ ctor. CoCoALib compiled fine (no problems with ambiguity)...
-
- Christof asks why the ctor for a @BigInt@ from a machine integer is @explicit@ rather than implicit.
He also suggest... -
- - cleaned up into a package
- tests included in Makefile
- documentation still missing (should be just a minor fix ... -
- Last night I had this idea, does it work?
The problem is:
*RingHom* 's are refcounted objects, many actually "live" i... -
- Here's the conclusion:
* currently FrF only of true GCD domain allowed
* the fn *@IsFractionFieldOfGCDDomain@* has ...
10 Jul 2014
-
- John Abbott wrote:
> Of those two I have a preference for *@WantNonZero@* -- I can "say" it more easily in my mind t... -
- Of those two I have a preference for *@WantNonZero@* -- I can "say" it more easily in my mind than @ExpectNonZero@.
... -
- I have just noticed that the function which says over which a ring a matrix lies is called *@BaseRing@*. I'm not so ...
-
-
- Implemented some printing. A newly created cone now is printed like:...
-
- I've updated the documentation (removed references to @AsPolyRing@ etc.)
tests: I can't really test a function I'v... -
- No problems have come up, so closing.
-
-
- For objects (cones, algebras,..) which are not generated in degree 1 the Hilbert function is not a polynomial anymore...
-
- Closing this issue, but leaving #7 open. This is fine as far as it goes.
-
- Essentially everything listed has been done --> closing.
-
-
- Closing.
09 Jul 2014
-
- *WantNonZero* or
*ExpectNonZero* -
- Here are some other candidate names:
*RequireNonZero*
*ReqNonZero*
*NeedNonZero*
*MustBeNonZero*
*WantNonZero*
-
- Well, this is actually a sub-task.
I think we can make a quick decision about the names (we have already talked abou... -
- This task is really already covered by the proposed radical restructuring and renaming of the error codes #427. As a...
-
- I think we'd better be conservative, i.e. only for true GCDRings.
If someone ever asks for the general case then we ... -
- Can this be closed in the near future? (i.e. before Seoul)
-
- No problem has ever occurred to anyone in the last year.
Have we fixed it? can't remember.
Has the compiler changed... -
- *@Anna* Is this still a problem? I hope not; then we can just terminate the issue.
-
- Maybe we can resolve this issue while I'm in Osnabrueck?
-
- I have removed @AsDenseUPolyRing@, @AsFreeModule@ and @AsFGModule@.
The code compiles and all tests pass, so I have ...
08 Jul 2014
-
- I've now removed @AsQuotientRing@, and revised the imple of @BaseRing@ (see #584)
-
- I've removed @AsPolyRing@, @AsSparsePolyRing@ and @AsFractionField@.
So far so good. Some bits of code have becom... -
- I've implemented it, and it seems to work. Currently the impl does *(B)*, but it'd be easy to change to *(A)*.
(2014... -
- Not sure what @BaseRing(ZZ)@ should produce:
*(A)* either @ZZ@ itself
*(B)* an error
My current preference (afte... -
- One problem with this approach is that we would exclude product rings, since a product ring could have several "paren...
-
- I'm considering implementing @BaseRing@ for all rings (except perhaps @ZZ@).
With our current design every ring ha...
07 Jul 2014
-
- In CoCoA-5 we have the command *@Describe@* for printing a detailed description of an object.
It would be useful to ... -
- John Abbott wrote:
> (A) @Expected (element of) PolyRing@
this one!
-
- See also emails exchanged on 20140704 with subject "Opinion".
We need suitable wording for the combined error: how... -
- Proposal: merge the two error codes @NotPolyRing@ and @NotElemPolyRing@.
Reasons:
(1) the distinction is really q...
Also available in: Atom