Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Miscellaneous details #1181

Open
isivigno opened this issue May 23, 2016 · 2 comments
Open

Miscellaneous details #1181

isivigno opened this issue May 23, 2016 · 2 comments
Assignees

Comments

@isivigno
Copy link
Member

Dear all,

When preparing a lab session for DGtal (and digital geometry) beginners, I made a list of a bunch of details that could make the first steps in DGtal easier.
Thus, here they are… It concerns very basic stuff, and I could do the modifications with your approval.

See you,
Isabelle.

Uniformization

  • different names are used here and there to refer to a digital set, for instance :
    • « set » in the function SetFromImage
    • « PointSet » as an attribute of a Digital Object
    • « DigitalSet » most of the time
      This is confusing where searching digital set related functionalities in the doc. I think it would be nice to use DigitalSet everywhere
  • lowerBound() vs. getLowerBound()
    • in HyperRectDomain, DigitalSetDomain, and KhalimskySpaceND, the method is called « lowerBound »
    • seems to be « getLowerBound » everywhere else
  • order of the arguments: in the three following methods
    extractAll2DSCellContours
    extractAllConnectedSCell
    extractAllPointContours4C
    put the arguments in the same order, for instance : result, KSpace, surfelAdjacency, point predicate. (extractAllPointContours4C is not consistent with the other two)

Miscellaneous

  • The methods extractAll2DSCellContours and extractAllConnectedSCell output a vector< vector ..> but in order to fill a contour using the uFillInterior method, a set of surfels is required (need of a « find » member function). It could be nice to be able to output directly a vector < set ….> from the extraction.
  • It would also be since to have a method to fill a closed contour and get a digital set as a result instead of an image.
@dcoeurjo
Copy link
Member

dcoeurjo commented Jun 6, 2016

thanks a lot isabelle for the feedbacks.

@kerautret kerautret added this to the 1.0 milestone Jan 24, 2017
@kerautret
Copy link
Member

thanks, I will look it but more after 0.9.3 ;)

@kerautret kerautret self-assigned this Jan 24, 2017
@dcoeurjo dcoeurjo removed this from the 1.0 milestone Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants