Activity
From 04 Mar 2015 to 02 Apr 2015
02 Apr 2015
-
17:55 CoCoA-5 Support #677 (New): Credits to CoCoA-5 contributors
- If we want (and we want) to attract contributions we need to find a proper way to give them credits for their work, a...
-
17:53 CoCoALib Support #676 (In Progress): Credits to CoCoALib contributors
- If we want (and we want) to attract contributions we need to find a proper way to give them credits for their work, a...
28 Mar 2015
-
09:18 CoCoALib Slug #675: Matrix determinant over multivariate poly ring
- In my specific instance the direct algorithm (as alternating sum of products) would be best.
The problem with mult... -
09:16 CoCoALib Slug #675 (In Progress): Matrix determinant over multivariate poly ring
- CoCoA can be too slow and require too much RAM for computing determinant of a matrix of multivariate polynomials.
...
26 Mar 2015
-
11:53 CoCoALib Bug #15: Adjoint of a non-invertible matrix
- I am planning to implement a direct algorithm: each entry in the @adj@ is just a determinant, and each determinant is...
25 Mar 2015
-
15:59 CoCoALib Bug #15: Adjoint of a non-invertible matrix
- Even @AdjByDetOfMinors@ takes too long for a 6x6 matrix of distinct indets. Why?
*2015-03-26 NOTE* I think the prob... -
15:22 CoCoALib Bug #15: Adjoint of a non-invertible matrix
- @adj@ is a very simple function: it chooses between @AdjByDetOfMinors@ and @AdjByInverse@.
What do you think @AdjB... -
14:52 CoCoALib Bug #15 (In Progress): Adjoint of a non-invertible matrix
- I do not recall when, but @adj@ has aleady been added to CoCoALib.
It has a *VERY BAD SLUG*: even after several mi...
13 Mar 2015
-
14:50 CoCoA-5 Feature #674: Ring constructor: allow empty range for indices?
- John Abbott wrote:
> I understand your point.
> Actually, I suppose the correct solution is to use anonymous ind... -
14:35 CoCoA-5 Feature #674 (In Progress): Ring constructor: allow empty range for indices?
- I understand your point. Actually, I suppose the correct solution is to use anonymous indets for the dummies, but we...
-
13:56 CoCoA-5 Feature #674: Ring constructor: allow empty range for indices?
- John Abbott wrote:
> There would be no technical problem allowing a range such as 1..0; perhaps the main question is... -
13:21 CoCoA-5 Feature #674: Ring constructor: allow empty range for indices?
- There would be no technical problem allowing a range such as 1..0; perhaps the main question is whether the gain in e...
-
11:08 CoCoA-5 Feature #674 (Rejected): Ring constructor: allow empty range for indices?
- I am writing a CoCoA-5 program which may need some "dummy" variables. My code looks like this:...
-
13:55 CoCoA-5 Support #654 (Feedback): Rename adjoint to adjugate???
- After speaking to Anna about it on Skype, we decided that it is simplest to call the function @adj@ (in the same way ...
11 Mar 2015
-
13:14 CoCoA-5 Feature #673: Error message: I was expecting...
- The relevant source code is @Parser.H:156@
The following rule may help identify the "type" of a parser token:
* s... -
13:10 CoCoA-5 Feature #673 (Closed): Error message: I was expecting...
- The generic error message...
-
13:07 CoCoA-5 Design #668: Remove keyword "weights"?
- It works... more or less. @A["weights"]@ gives the error I wanted, but @A.weights@ still gives a less helpful error....
10 Mar 2015
-
21:09 CoCoA-5 Design #668: Remove keyword "weights"?
- At the moment I have implemented @setField@ and @setFieldNoCheck@; the latter is just the old fn renamed. The new fn...
-
20:13 CoCoA-5 Design #668: Remove keyword "weights"?
- In @Interpreter.H:718@ the mem fn @setField@ is declared as @virtual@; why??
-
16:27 CoCoA-5 Bug #670: Error column indicator misaligned with non-printing (unprintable) characters
- Relevant source code is @Lexer.C:615@ and following lines.
Already have a prototype; currently prints out # instea... -
11:38 CoCoA-5 Bug #672: Emacs UI: strange string literal causes crash
- The EmacsUI really seems to do strange things when the input contains unprintable chars. I am guessing that it is th...
09 Mar 2015
-
00:45 CoCoA-5 Bug #672: Emacs UI: strange string literal causes crash
- Other chars which give trouble include those with ASCII code 3, ...
[to be completed]
-
21:35 CoCoA-5 Bug #672 (Closed): Emacs UI: strange string literal causes crash
- I created a file (@CRASH.cocoa5@) containing the following:...
-
13:49 CoCoA-5 Bug #671 (New): Emacs UI: swapped splitting
- In some cases emacs splits (top+bottom) swapping the buffers, i.e. *cocoa5* at the bottom.
Investigate and fix. -
13:33 CoCoA-5 Bug #670 (In Progress): Error column indicator misaligned with non-printing (unprintable) characters
- I was thinking that the substitution for unprintable chars would occur only when printing out source code for the pur...
-
11:26 CoCoA-5 Bug #670: Error column indicator misaligned with non-printing (unprintable) characters
- John Abbott wrote:
> A very simple idea would be to replace unprintable characters by a single printable character (...
06 Mar 2015
-
20:31 CoCoA-5 Design #668: Remove keyword "weights"?
- After speaking to Anna by Skype we have decided:
* Anna will remove the keyword @weights@ (from interpreter and UIs)... -
11:21 CoCoA-5 Design #668: Remove keyword "weights"?
- I should also modify @RECORD::setField@ so that it gives an error if the field name is not a valid identifier for CoC...
-
11:10 CoCoA-5 Design #668: Remove keyword "weights"?
- This is trickier than I originally thought.
The way the CoCoA-5 interpreter is designed a keyword is always seen a... -
20:28 CoCoA-5 Bug #670: Error column indicator misaligned with non-printing (unprintable) characters
- A very simple idea would be to replace unprintable characters by a single printable character (_e.g._ @?@) this would...
-
20:24 CoCoA-5 Bug #670 (Closed): Error column indicator misaligned with non-printing (unprintable) characters
- While doing some "fuzz" testing with CoCoA-5 I noticed that error messages seemed to indicate the wrong columns; then...
-
17:26 CoCoA-5 Bug #669 (New): NUL char in input terminates CoCoA-5
- I tried a "fuzzing" test with CoCoA-5 (feeding the executable as input).
CoCoA-5 treats a NUL (ASCII code 0) as end-...
05 Mar 2015
-
18:43 CoCoA-5 Design #668: Remove keyword "weights"?
- The involved lines are:...
-
18:40 CoCoA-5 Design #668 (In Progress): Remove keyword "weights"?
- The problem arose when Claudia Fassino worked with @PreprocessPoint@, and had trouble getting the value of @P.weights...
-
18:26 CoCoA-5 Design #668 (Closed): Remove keyword "weights"?
- In CoCoA-4 "Weights" was used to set weights in a polynomial ring construction.
Now weights are dealt with in a comp...
04 Mar 2015
-
20:08 CoCoALib Feature #667: factor: multivariate + finite characteristic
- Factorizing in @F_q[x]@ is largely the same as factorizing in @F_p[x]@; the algorithm is essentially the same (but co...
-
16:45 CoCoALib Feature #667: factor: multivariate + finite characteristic
- John Abbott wrote:
> The squarefree decomposition is the normal first step, but there are other problematic steps (_... -
13:31 CoCoALib Feature #667: factor: multivariate + finite characteristic
- The squarefree decomposition is the normal first step, but there are other problematic steps (_e.g._ mapping down to ...
Also available in: Atom