New package: Feature graph#9465
Conversation
Feature graph is now an VertexAndEdgeListGraph Lowercase in passive form in --> on regularization isthmus distance parameter Element type is now CGAL::Dimension_tag
albert-github
left a comment
There was a problem hiding this comment.
should be /// @{ instead of // @{
occurs in multiple files.
(I didn't really review it but this caught my eye)
|
/build:doc-wip |
It will be placed back once the API is validated
|
There was an error while building the doc: |
|
/build:doc-wip |
|
The documentation is built. It will be available, after a few minutes, here: https://cgal.github.io/9465/doc/Manual/index.html |
|
/build:doc-wip |
|
The documentation is built. It will be available, after a few minutes, here: https://cgal.github.io/9465/doc/Manual/index.html |
|
The CI says that the file |
Ok, I didn't understand because the package creation script only generate the file |
The API will be templeted internally for the images, but this will stay undocumented until a more suitable location for this concept is created.
|
/build:doc-wip |
|
There was an error while building the doc: |
|
I saw this problem regarding the PR's documentation now a couple of times and I have the suspicion that this might have to do with the recent change to a newer version of doxygen 1.9.6 to 1.17.0) probably somewhere some logic is not working as expected. |
|
/build:doc-wip |
|
There was an error while building the doc: |
|
/build:doc-wip |
|
There was an error while building the doc: |
|
/force-build:doc-wip |
|
The documentation is built. It will be available, after a few minutes, here: https://cgal.github.io/9465/doc/Manual/index.html |
|
@ange-clement est-ce que tu peux repondre aux remarques que j'ai fait. |
|
There is Reference Manual inside Reference Manual |
Renamed ..._on_X to X_..._estimator Changed Sharpness_value_type to Sharpness_number_type
Add example CMakeLists + added typename
|
/force-build:doc-wip |
|
The documentation is built. It will be available, after a few minutes, here: https://cgal.github.io/9465/doc-wip/Manual/index.html |
| * | ||
| * \cgalParamSectionBegin{point_to_element_output_map} | ||
| * \cgalParamDescription{an output property map that will be filled if supplied. | ||
| * It allow retrieving of the surface element where a feature graph point is embedded. |
There was a problem hiding this comment.
| * It allow retrieving of the surface element where a feature graph point is embedded. | |
| * It enables retrieving of the surface element where a feature graph point is embedded. |
| * and must implement `put(output_pmap, feature_vertex_descriptor, facet_descriptor)` | ||
| * where the key type is the `vertex_descriptor` of the feature graph, and the value type is | ||
| * a descriptor of an element of the surface, with type `std::size_t`. | ||
| * The facet descriptor correspond to a facet element with the tag `CGAL::DimensionTag<2>`} |
There was a problem hiding this comment.
Is that on purpose "facet" instead of "face"?
| * </UL> | ||
| * <LI> The type `DimensionTag` represents the element type, it can either be `CGAL::Dimension_tag<0>`, `CGAL::Dimension_tag<1>` or `CGAL::Dimension_tag<2>`, | ||
| * which represent either a vertex element, an edge element, or a facet element respectively. | ||
| * <LI> The type `Descriptor` is either a `vertex_descriptor`, `halfedge_descriptor` or `face_descriptor` and |
There was a problem hiding this comment.
Coming back to "facet", even if was the correct mathematical term, I suggest to call it face, as we use a face_descriptor for it.
| * If it is a scalar field, it must implement | ||
| * <UL> | ||
| * <LI> `template <typename DimensionTag, typename Descriptor>` | ||
| * <BR> `FT operator()(const Point_3& point_in_space, const Descriptor& element_descriptor, const PolygonMesh& pmesh) const` |
| if (MSVC) | ||
| add_compile_options(/bigobj) | ||
| else () | ||
| add_compile_options(-Wa,-mbig-obj) |
There was a problem hiding this comment.
Is this really needed ? It gives error messages in the testsuite
| @@ -0,0 +1,127 @@ | |||
| // WARNING : non-functioning example. This exmaple is to understand how to create and use the feature graph for tetrahedral mesh creation. | |||
There was a problem hiding this comment.
What do you mean with "non-functionning"??


Summary of Changes
New package "Feature graph" that contains methods to extract sharp features from 3D images.
Tasks
Release Management