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

Tutorial reorganization #44

Open
alecjacobson opened this issue Sep 27, 2020 · 5 comments
Open

Tutorial reorganization #44

alecjacobson opened this issue Sep 27, 2020 · 5 comments

Comments

@alecjacobson
Copy link
Contributor

Chapter 7 is getting a bit out of control. Meanwhile, Chapter 1 is simultaneously an intro chapter and a "viewer features" chapter. Let's use this issue to discuss some reorganization. For reference, here're the current tutorial entries (that we have code for; so this includes ones that have missing documentation):

Tetgen
FastAutomaticSkinningTransformations
SignedDistance
MeshImplicitFunction
SweptVolume
BiharmonicDeformation
Boolean
GaussianCurvature
ExplodedView
SLIM
HarmonicParam
NRosyDesign
ViewerMenu
CSGTree
AsRigidAsPossible
Events
ScreenCapture
BoundedBiharmonicWeights
CurvatureDirections
MarchingCubes
LaplaceEquation
Decimation
LSCMParam
MEX
ShapeUp
Planarization
AmbientOcclusion
Laplacian
WindingNumber
Statistics
Gradient
GeodesicDistance
BiharmonicCoordinates
Kelvinlets
SCAF
MultipleViews
Triangle
DirectDeltaMush
FileIO
IterativeClosestPoint
FastWindingNumber
MIQ
DualQuaternionSkinning
Picking
MultipleMeshes
MarchingTets
DrawMesh
ARAPParam
Colors
EigenDecomposition
Matlab
Slice
QuadraticProgramming
FacetOrientation
Overlays
Sort
FrameField
BlueNoise
LinearEqualityConstraints
Normals
Subdivision
DataSmoothing
HeatGeodesics
ImGuizmo
PolyharmonicDeformation
Serialization
@jdumas
Copy link
Collaborator

jdumas commented Sep 27, 2020

+1 for this. How would you name chapters 2 to 6 under the current classification? I think chapter 1 is fine as it, since there isn't much to introduce without the viewer (101_FileIO is really short). Chapter 7 is becoming a bit of a potpourri for sure...

@alecjacobson
Copy link
Contributor Author

Here's one possible reorganization. This is based on putting like topics together (many chapters are the same). There are few odd ducks (e.g., AmbientOcclusion, IterativeClosestPoint).

I left FileIO on its own because I think we could add a couple more really basic entries that demonstrate the V,F data structure even without invoking the Viewer. I also think we don't need to do a deep dive on the Viewer before more basic things like introducing the solvers, etc.

# Basics
 - FileIO

# Linear algebra / Solvers
 - Slice
 - Sort
 - LinearEqualityConstraints
 - LaplaceEquation
 - EigenDecomposition
 - QuadraticProgramming

# Viewer
 - DrawMesh
 - Events
 - MultipleMeshes
 - Colors
 - ExplodedView
 - Picking
 - MultipleViews
 - ScreenCapture
 - Overlays
 - ViewerMenu
 - ImGuizmo

# Deformation
 - BiharmonicDeformation
 - PolyharmonicDeformation
 - BoundedBiharmonicWeights
 - DualQuaternionSkinning
 - DirectDeltaMush
 - AsRigidAsPossible
 - FastAutomaticSkinningTransformations
 - BiharmonicCoordinates
 - ShapeUp
 - Planarization
 - Kelvinlets

# Solid Geometry
 - SignedDistance
 - WindingNumber
 - FastWindingNumber
 - FacetOrientation
 - SweptVolume
 - MarchingCubes
 - MeshImplicitFunction
 - MarchingTets
 - Boolean
 - CSGTree
 - AmbientOcclusion

# Differential Geometry
 - Normals
 - GaussianCurvature
 - CurvatureDirections
 - Gradient
 - Laplacian
 - DataSmoothing
 - HeatGeodesics
 - GeodesicDistance

# Parameterization
 - HarmonicParam
 - LSCMParam
 - ARAPParam
 - NRosyDesign
 - SLIM
 - SCAF
 - MIQ
 - FrameField

# Mesh operations
 - Subdivision
 - Decimation
 - BlueNoise
 - Statistics
 - IterativeClosestPoint

# External
 - Serialization
 - Tetgen
 - Matlab
 - Triangle
 - MEX

@jdumas
Copy link
Collaborator

jdumas commented Sep 27, 2020

Looks good to me. Ambient occlusion could really also go into the viewer part, since its main application is data visualization.

@sooryan
Copy link
Contributor

sooryan commented Oct 3, 2020

Piggybacking on this, I was wondering if it made sense to split the tutorial entries into separate markdown files. The tutorial file is already quite large now. Could potentially use something like markdown-include which mkdocs seems to support.

@alecjacobson
Copy link
Contributor Author

alecjacobson commented Oct 3, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants