CoCoA: Issueshttps://cocoa.dima.unige.it/redmine/https://cocoa.dima.unige.it/redmine/redmine/favicon.ico?15088260392024-03-29T09:37:08ZCoCoA Project
Redmine Bug #1812 (New): Documentation: indexXX.html should be recompiled if version has changedhttps://cocoa.dima.unige.it/redmine/issues/18122024-03-29T09:37:08ZAnna Maria Bigatti
<p>There is no dependency on configuration/version in doc/Makefile for index...html.<br />(on the other hand the pdf manual seems to work fine... maybe).</p> Bug #1811 (Resolved): Check include guardshttps://cocoa.dima.unige.it/redmine/issues/18112024-03-28T22:00:19ZJohn Abbott
<p>Some files have include guards without the <code>CoCoA_</code> prefix<br /><pre>
TmpJBAlgorithm.H:#ifndef TMPJBALGORITHM_H_
TmpMayerVietorisTree.H:#ifndef TmpMVT_H
TmpMonomialFunctions.H:#ifndef TmpMonFun_H
TmpPPVector.H:#ifndef TmpPPVector_H
</pre><br />Rectify</p> Support #1810 (New): Release CoCoALib 0.99900https://cocoa.dima.unige.it/redmine/issues/18102024-03-28T14:11:25ZAnna Maria Bigatti
<p>Everything related to making a CoCoALib release:</p>
<pre><code>Redmine Roadmap: close or postpone issue<br /> Redmine Release issues: check percentages, check timings<br /> Finalize<br /> make veryclean; make (full make, with all tests and examples and CoCoA-5..)<br /> cd src/tests/; make valgrind<br /> cd src/CoCoA-5; make ManExamples (readline may truncate echo lines if too long)<br /> cvs log -d ">2024-03-29" -S -N > LOG-CoCoA.txt<br /> ~/shell-scripts/cocoalib-cvs-snapshot.sh<br /> upload examples<br /> upload manual<br /> update webpage<br /> publish manual (arXiv? ResearchGate?)<br /> close release on Redmine</code></pre>
<p>--> send message to facebook page</p> Feature #1809 (New): Make ex-syz.Chttps://cocoa.dima.unige.it/redmine/issues/18092024-03-28T07:45:24ZAnna Maria Bigatti
<p>Dealing with syzygies is non-trivial, expecially with shifts.<br />There is a dedicated function NewFreeModuleForSyz which is quite handy but tricky to document properly.<br />Thus, make an example file for CoCoALib: probably it's just enough to translate the manual page ?syz for CoCoA-5.</p>
<p>Add a link to this into the CoCoA documentation file submodule.txt, possibly also to ideal.txt.<br />I expect that some refinements to the actual code in submodule.C might follow from making this example file.</p> Feature #1808 (In Progress): New constructor for PolyRing with elimination orderinghttps://cocoa.dima.unige.it/redmine/issues/18082024-03-28T06:31:28ZAnna Maria Bigatti
<p>New syntax <code>NewPolyRingElim(....)</code> would be handy, and also easily transferred to CoCoA-5.<br />Design its interface (eg: vector of long? strings? weights?).</p> Design #1807 (New): Error codes: "Not..." for "blah must be ..." -- change prefixhttps://cocoa.dima.unige.it/redmine/issues/18072024-03-26T13:22:57ZAnna Maria Bigatti
<p>In the general picture of improving the error codes, I suggest a trivial (though extensive) change.<br />Look at these names (just a few)<br /><pre>
NotFreeModule
NotFullRank
NotNonZero
</pre><br />We have many times discussed that from the code/name of the error it's not obvious if you want the object to be, say, full rank or the opposite.<br />I propose to change such codes into<br /><pre>
ReqFreeModule
ReqFullRank
ReqNonZero
</pre></p> Feature #1806 (New): New function ModuleElems? (like RingElems(RING, STRING))https://cocoa.dima.unige.it/redmine/issues/18062024-03-26T12:44:47ZAnna Maria Bigatti
<p>The best shortcut to make a submodule is via <code>SumboduleCols/Rows</code>.</p>
<p>As pointed out in <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: syz: apply to ModuleElem? (Rejected)" href="https://cocoa.dima.unige.it/redmine/issues/1072">#1072</a>-<a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: MachineInteger --> MachineInt (Closed)" href="https://cocoa.dima.unige.it/redmine/issues/1">#1</a>, even for one generator we need the list:<br /><pre>
use P ::= QQ[x,y,z];
M3 := NewFreeModule(P,3);
v := ModuleElem(M3, [0,z,-y]);
submodule(M3, [v]);
</pre><br />I don't think it worth implementing the 1-2-3 generator shortcuts as for ideal, but <strong>maybe</strong> a syntax to read from a string could be handy.</p> Feature #1805 (New): Add CoCoA-5 syntax: syz(<F,> list of ModuleElem)https://cocoa.dima.unige.it/redmine/issues/18052024-03-26T11:16:00ZAnna Maria Bigatti
<p>Currently we can call SyzOfGens(M), but it should also be possibile to call syz(gens(M)).</p>
<p>This is tedious because we have to distinguish (in BuiltinFunctionsVarArg-CoCoALib) if the list is made of RingElem or of ModuleElem.<br />I cannot think of another case as this...</p> Design #1804 (New): Use long long (at least sometimes)?https://cocoa.dima.unige.it/redmine/issues/18042024-03-25T18:29:24ZJohn Abbott
<p>Winfried Bruns suggested in issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Microsoft: cannot compile with signal handling (Closed)" href="https://cocoa.dima.unige.it/redmine/issues/1661">#1661</a> to consider using <strong><code>long long</code></strong> wherever we want more than 32-bits.<br />Investigate, discuss, and implement (if we decide to make the change).</p>
<p>Another option might be <code>int64_t</code> (but there are only optional... not good for portability).</p>
<p><strong>NOTE</strong> mysteriously Brun's comment on issue 1661 is no longer there -- how did that happen??</p> Feature #1803 (New): Improve trivial operations with ideal whose GBasis is [1]https://cocoa.dima.unige.it/redmine/issues/18032024-03-25T18:06:41ZAnna Maria Bigatti
<p>Sum is clever -- if HasGBasis(I) and is ideal(1).<br />Do the same for product and for other similar operations.<br /><pre>
use QQ[x,y,z];
I := ideal(x, x-1); GBasis(I);
ideal(y) + I; ---> gives (1) :-)
ideal(y) * I; ---> uses generators :-(
</pre></p> Design #1802 (New): Tidying ideal generators (for non-polynomial ideals)https://cocoa.dima.unige.it/redmine/issues/18022024-03-25T18:02:06ZJohn Abbott
<p>Generalize the ideas of issue <a class="issue tracker-7 status-5 priority-4 priority-default closed" title="Design: Suppress zero from ideal generators? Detect 1 and simplify generators? (Closed)" href="https://cocoa.dima.unige.it/redmine/issues/1647">#1647</a> to other types of ideal (and modules?)</p> Design #1801 (New): BuildInfohttps://cocoa.dima.unige.it/redmine/issues/18012024-03-25T17:47:07ZJohn Abbott
Three things:
<ul>
<li>why do some preprocessor flags have prefix <strong><code>COCOA_</code></strong> while others have <strong><code>CoCoA_</code></strong> ?</li>
<li>for whom are the messages printed by <code>BuildInfo</code> intended?</li>
<li>would it be more sensible/coherent for <code>BuildInfo</code> just to print out the name of the macro followed by its value?</li>
</ul> Design #1800 (New): Conversion from SmallPrime to UNSIGNED long?https://cocoa.dima.unige.it/redmine/issues/18002024-03-25T16:47:41ZJohn Abbott
<p>Currently there is an "implicit" conversion from <code>SmallPrime</code> to <code>signed long</code>.<br />Should the conversion instead be to <strong><code>unsigned long</code></strong>?<br /><code>SmallPrime</code> can never produce a negative value. One or two places in the code may be a little neater if the conversion were to <code>unsigned long</code>.<br />This does mean relaxing the refusal to use unsigned values...</p> Design #1799 (New): Clean out OLD CODE?https://cocoa.dima.unige.it/redmine/issues/17992024-03-24T09:50:00ZJohn Abbott
<p>The sources contain some quite old code which is likely no longer used.<br />We should identify the code and consider removing it.<br />This came up because Nico has been testing compilation on M$, and found<br />problems with some of the old files.</p> Design #1798 (New): Computing in sub polyringhttps://cocoa.dima.unige.it/redmine/issues/17982024-03-22T08:23:57ZJohn Abbott
<p>Investigate whether it is a good idea to adapt certain operations to compute in a sub polyring (without unnecessary indets)<br />Which functions would benefit?<br />How to specify the sub polyring and mapping back and forth.</p>