Comments (3)
I don't really understand what you mean, could you clarify ?
from marchingcubes.jl.
"example.jl" implies a file that stores a simple example, and in fact this is the case (i.e. scenario()). However, the file also contains the following crucial functions, which aren't even used in the example. It seems like they should be in MarchingCubes.jl
output(PlyIO::Module, m::MC, fn::AbstractString = "test.ply") = begin
ply = PlyIO.Ply()
push!(
ply,
PlyIO.PlyElement(
"vertex",
PlyIO.ArrayProperty("x", map(v -> Float32(v[1]), m.vertices)),
PlyIO.ArrayProperty("y", map(v -> Float32(v[2]), m.vertices)),
PlyIO.ArrayProperty("z", map(v -> Float32(v[3]), m.vertices)),
PlyIO.ArrayProperty("nx", map(n -> Float32(n[1]), m.normals)),
PlyIO.ArrayProperty("ny", map(n -> Float32(n[2]), m.normals)),
PlyIO.ArrayProperty("nz", map(n -> Float32(n[3]), m.normals)),
),
)
vertex_indices = PlyIO.ListProperty("vertex_indices", UInt8, Int32)
for i ∈ eachindex(m.triangles)
push!(vertex_indices, m.triangles[i] .- 1)
end
push!(ply, PlyIO.PlyElement("face", vertex_indices))
PlyIO.save_ply(ply, fn, ascii = true)
nothing
end
makemesh_Meshes(Meshes::Module, m::MC) = begin
points = map(Meshes.Point3 ∘ Tuple, m.vertices)
tris = Meshes.connect.(map(Tuple, m.triangles), Meshes.Triangle)
Meshes.SimpleMesh(points, [tris;])
end
makemesh_GeometryBasics(GeometryBasics::Module, m::MC) = begin
vertices = map(GeometryBasics.Point3f, m.vertices)
normals = map(GeometryBasics.Vec3f, m.normals)
triangles = map(t -> GeometryBasics.TriangleFace(t...), m.triangles)
GeometryBasics.Mesh(GeometryBasics.meta(vertices; normals), triangles)
end
makemesh(mod::Module, m::MC) =
if (mod_str = string(mod)) == "Meshes"
makemesh_Meshes(mod, m)
elseif mod_str == "GeometryBasics"
makemesh_GeometryBasics(mod, m)
else
throw(ArgumentError("un-supported module `$mod`"))
end
from marchingcubes.jl.
Those functions were solely added to show an example of using the MarchingCubes
algorithm as a library.
Furthermore, they use modules arguments (e.g. PlyIO
), without specifying any version constraints, and are hence not guaranteed to work in the future.
They are also related to how you visualize your computations, and since everyone has its own preferred graphics / plotting library, they are not universal.
This is why I don't think they should be part of the library.
from marchingcubes.jl.
Related Issues (6)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from marchingcubes.jl.