FS issueshttps://gitlab.dune-project.org/flyspray/FS/-/issues2015-11-19T11:29:07Zhttps://gitlab.dune-project.org/flyspray/FS/-/issues/1319FS#1319 Update documentation of virtual refinement2015-11-19T11:29:07ZChristoph GrüningerFS#1319 Update documentation of virtual refinement# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
| Reported at | Jul 9, 2013 05:35 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
|...# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
| Reported at | Jul 9, 2013 05:35 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
# Description
dune-geometry's documentation is outdated. It misses some past changes. An example is that the class `StaticRefinement` replaced the class `Refinement`.
This is a replacement task to the remaining stuff of FS#1102.
https://gitlab.dune-project.org/flyspray/FS/-/issues/1015FS#1015 Matrix<T> operator*(Matrix<T>,Matrix<T>) docu inaccurate2015-11-19T11:50:22ZFlyspray ImporterFS#1015 Matrix<T> operator*(Matrix<T>,Matrix<T>) docu inaccurate# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Uli Sack (usack@math.fu-berlin.de) |
| Reported at | Jan 9, 2012 11:08 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating S...# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Uli Sack (usack@math.fu-berlin.de) |
| Reported at | Jan 9, 2012 11:08 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
# Description
For a quick and dirty test I wanted to use
Matrix<T> operator*(Matrix<T>,Matrix<T>)
but had to realize that it won't work for any T with block_size other than one due to the row_type of Matrix and the operator* in block_vector_unmanaged.
In general this came as a surprise, as I would expect a method for a block matrix to be able handle block matrices of arbitrary block sizes.
Therefore my question is, is there any reasonable way to use that method? Why is it there at all? Up to now I thought that ISTL-philosophy was "do not provide methods that are very costly (here:copying around matrices) or [cannot be | are not] implemented generically". Should it not be removed maybe?
In any case I think that this shortcoming should be documented, now documentation says "Generic matrix multiplication." I don't have to argue that 'generic' doesn't quite hit the mark. Anyway, there is a patch attached that slightly enhances documentation in that respect.
# Attachments
* [matrix.patch](/uploads/0566aeb5cedb3cfb92e4f123d373935e/matrix.patch)
https://gitlab.dune-project.org/flyspray/FS/-/issues/909FS#909 Method 'infinity_norm' does not actually compute the infinity norm2015-11-19T11:50:42ZOliver Sanderoliver.sander@tu-dresden.deFS#909 Method 'infinity_norm' does not actually compute the infinity norm# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Reported at | Apr 26, 2011 21:01 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operat...# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Reported at | Apr 26, 2011 21:01 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
# Description
I would expect a method called 'infinity_norm' of a matrix to compute the infinity norm: the maximum of the absolute values of all entries. However at least the implementations in DenseMatrix, BCRSMatrix, and Matrix compute something else, namely the maximum over the 1-norms of the matrix rows. This is a flagrant violation of the principle of least surprise.
The fix is easy, however apparently the behavior is intentional. At least it is mentioned in the documentation. Why would I need such a strange norm? And isn't there a better name for it?
https://gitlab.dune-project.org/flyspray/FS/-/issues/898FS#898 Easy access to detailed description of grid implementations2015-11-16T17:13:38ZChristoph GersbacherFS#898 Easy access to detailed description of grid implementations# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Christoph Gersbacher (gersbach@mathematik.uni-freiburg.de) |
| Reported at | Mar 30, 2011 09:20 |
| Type | Feature Request |
| Version | Git (pre2.4) [au...# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Christoph Gersbacher (gersbach@mathematik.uni-freiburg.de) |
| Reported at | Mar 30, 2011 09:20 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
# Description
Detailed descriptions of the grid implementations should be accessible directly through the "modules" page of the doxygen documentation. Currently, this is only the case for GeometryGrid. The documentation is already there, on the class documentation.
https://gitlab.dune-project.org/flyspray/FS/-/issues/781FS#781 Documentation missing in localfunctions/utility/2015-11-19T11:44:10ZChristian EngwerFS#781 Documentation missing in localfunctions/utility/# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Reported at | Apr 23, 2010 18:23 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] ...# Metadata
| Property | Value |
| -------- | ----- |
| Reported by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Reported at | Apr 23, 2010 18:23 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Oct 5, 2012 14:54 |
# Description
Most the files are in localfunctions/utility/ are barely documented. Please add the documentation. It is really hard to debug this code if there is no documentation.