- Oct 18, 2016
-
-
Christian Engwer authored
Feature/deprecate external ug See merge request !94
-
- Oct 14, 2016
-
-
Oliver Sander authored
[test] add static check for higher codimension information on grid views Until now, the static part of the grid check only check on codim 0 structures, e.g., on the index set. This patch also performs these checks on higher codimensions. For the IndexSet::subIndex method, it will only check whether the method compiles. If codim > 0, it will silently ignore a Dune::NotImplemented exception, so that grids are not forced to implement the method; it simply has to compile. Note: This check is able to detect the error fix in !86. This merge request is basically !89 , but with Martin's initial implementation removed. As it only lived to be completely replaced 24h later, I didn't see the point in keeping it in the history. See merge request !96
-
Oliver Sander authored
Implement the subIndex method for entities of all dimensions Previously, it was available only for elements. The following question appears: what does the codim-parameter in template<int cc> unsigned int subIndex (const Codim<cc>::Entity& e, int i, unsigned int codim) const mean? Is it the codimension wrt to the grid, or wrt to the entity e? I did not find this documented anywhere, and therefore made my own choice. The 'codim' in this patch is the codimension with respect to the *grid*. See merge request !95
-
Until now, the static part of the grid check only check on codim 0 structures, e.g., on the index set. This patch also performs these checks on higher codimensions. For the IndexSet::subIndex method, it will only check whether the method compiles. If codim > 0, it will silently ignore a Dune::NotImplemented exception, so that grids are not forced to implement the method; it simply has to compile. Note: This check is able to detect the error fix in !86.
-
- Oct 13, 2016
-
-
Oliver Sander authored
Previously, it was available only for elements. The following question appears: what does the codim-parameter in template<int cc> unsigned int subIndex (const Codim<cc>::Entity& e, int i, unsigned int codim) const mean? Is it the codimension wrt to the grid, or wrt to the entity e? I did not find this documented anywhere, and therefore made my own choice. The 'codim' in this patch is the codimension with respect to the *grid*.
-
Robert K authored
-
Robert K authored
-
Robert K authored
on it's own.
-
Robert K authored
-
- Oct 08, 2016
-
-
Christoph Grüninger authored
-
Christoph Grüninger authored
-
Christoph Grüninger authored
-
Christoph Grüninger authored
-
- Sep 30, 2016
-
-
Oliver Sander authored
Various OneDGrid cleanup patches See merge request !91
-
- Sep 29, 2016
-
-
Oliver Sander authored
They are already deprecated in the interface class. Since few people actually use the interface class, let's deprecate the methods on the implementation class OneDGrid as well.
-
Oliver Sander authored
-
Oliver Sander authored
-
- Sep 27, 2016
-
-
Oliver Sander authored
This is a preparatory step, to be able to remove the leafbegin/end and levelbegin/end methods from the OneDGrid class.
-
Oliver Sander authored
-
Oliver Sander authored
-
- Sep 20, 2016
-
-
Christoph Grüninger authored
Cleanup gitignore and old autotool doc See merge request !88
-
- Sep 19, 2016
-
-
Marco Agnese authored
-
Marco Agnese authored
-
Marco Agnese authored
-
- Sep 16, 2016
-
-
Martin Nolte authored
[bugfix] make subIndex method for OneDGrid compile for all codimension The index sets of OneDGrid support the subIndex method for entities of all codimensions. However, while the code was semantically correct for the case "cc != 0", the compiler would try to compile the "cc == 0" branch, too. This caused a compile-time error. This patch fixes the issue by calling a separate method for each codimension. See merge request !86
-
Oliver Sander authored
-
- Sep 14, 2016
-
-
Martin Nolte authored
The index sets of OneDGrid support the subIndex method for entities of all codimensions. However, while the code was semantically correct for the case "cc != 0", the compiler would try to compile the "cc == 0" branch, too. This caused a compile-time error. This patch fixes the issue by calling a separate method for each codimension.
-
- Sep 06, 2016
-
-
Oliver Sander authored
CommDataHandleIF: Introduce method 'fixedSize', which does the same as 'fixedsize', but has camel-case naming The CommDataHandleIF interface class has a member 'fixedsize'. This is one of the few in dune-grid that does not comply with the official naming rules: the name should be 'fixedSize'. This patch introduces a new method 'fixedSize', to allow a gradual transition from the old spelling to the new one. The make the transition as painless as possible, but methods implement the following behavior (remember that CommDataHandleIF is the base class in a CRTP pattern): - If the derived/implementation class has a method 'fixedSize', then that method is called. - Otherwise, the method 'fixedsize' is called. This approach allows both implementors of grids and implementors of data handles to switch their code from 'fixedsize' to 'fixedSize' at their convenience. Finally, I have come across a usecase for CRTP. :-) See merge request !82
-
- Sep 05, 2016
-
-
Oliver Sander authored
But the deprecation happens only in the doxygen documentation. Frankly I don't really know how to get a compiler warning here.
-
Oliver Sander authored
Fix uggrid entityseeds Previously, entity seeds only worked for elements and vertices. See merge request !84
-
- Aug 31, 2016
-
-
Oliver Sander authored
Due to unclear semantics of the hasEntity capability, these case are not currently tested by the checkentityseed.hh grid test.
-
Oliver Sander authored
That's what the getter is for, and the target_ member is protected in some of the specializations of UGGridEntity.
-
Oliver Sander authored
Previously, the implementation of UGGrid entities for facets of 3d elements consisted of two classes: UGGridEntity<1,3>, a specialization of the generic implementation class for UGGrid entities, and UGFaceEntity, a special implementation class for the codim-1 case in 3d. There was never a real reason for this separation into two classes, and this patch does away with it. This leads to a minor code simplification. Note: The same separation into two classes holds for grid edges, and there is a reason. The UGEdgeEntity class, which contains the actual implementation, serves for *two* cases: UGGridEntity<1,2> and UGGridEntity<2,3>. C++ partial specialization rules apparently do not allow to merge all of this into one class.
-
- Aug 18, 2016
-
-
Oliver Sander authored
[uggrid] remove methods lbegin, lend, leafbegin, leafend from UGGrid The methods aren't part of the API anymore. Implement the functionality in the begin/end methods of the corresponding GridViews. Replace internal use of the old methods by range-based for loops. See merge request !83
-
Christoph Grüninger authored
-
- Aug 17, 2016
-
-
Bernd Flemisch authored
The methods aren't part of the API anymore. Implement the functionality in the begin/end methods of the corresponding GridViews. Replace internal use of the old methods by range-based for loops.
-
- Aug 15, 2016
-
-
Oliver Sander authored
-
Oliver Sander authored
The CommDataHandleIF interface class has a member 'fixedsize'. This is one of the few in dune-grid that does not comply with the official naming rules: the name should be 'fixedSize'. This patch introduces a new method 'fixedSize', to allow a gradual transition from the old spelling to the new one. The make the transition as painless as possible, but methods implement the following behavior (remember that CommDataHandleIF is the base class in a CRTP pattern): - If the derived/implementation class has a method 'fixedSize', then that method is called. - Otherwise, the method 'fixedsize' is called. This approach allows both implementors of grids and implementors of data handles to switch their code from 'fixedsize' to 'fixedSize' at their convenience. Finally, I have come across a usecase for CRTP. :-)
-
- Aug 12, 2016
-
-
Oliver Sander authored
-
Oliver Sander authored
The gather and scatter methods of a DataHandle should only be called for a particular codimension, if the 'contains' method of the DataHandle returns true for that codimension. Previously they were always called.
-