Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Skeleton based thickness
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
QIM
Tools
Skeleton based thickness
Commits
82edacf9
Commit
82edacf9
authored
4 years ago
by
vand
Browse files
Options
Downloads
Patches
Plain Diff
Update TODO.md
parent
911343b2
Branches
3d_watershed
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
content/TODO.md
+2
-1
2 additions, 1 deletion
content/TODO.md
with
2 additions
and
1 deletion
content/TODO.md
+
2
−
1
View file @
82edacf9
*
Naming of functions, variables and terms in the text shouls be consistent (and not porosity).
*
Naming of functions, variables and terms in the text shouls be consistent (and not porosity).
*
Content of pdf file should be moved to readme.md
*
Content of pdf file should be moved to readme.md
*
Code for computing thickness should be packed in a function
*
Code for computing thickness should be packed in a function
\ No newline at end of file
*
Make nice figure for QIM homepage.
\ No newline at end of file
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment