Hello everybody,
I hope this is not a stupid question. I traverse across my OpenMesh trimesh object and mark certain edges / faces based on some filtering criterion.
Now if i want to build a new Trimesh / Polymesh object out of these faces (for example), what is the best way to do this ?
Any help / hints would be appreciated.
Thanks in advance.
Kind regards,
S Vijai Kumar
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Dear developers,
I contact you because I get the compilation error below when I try to build the Core Library with Xcode (9.4), after I created an Xcode project with "cmake -G Xcode .."
Curiously, the compilation works when I build the packages with cmake in the terminal without creating a Xcode project: "cmake .."
PhaseScriptExecution CMake\ PostBuild\ Rules build/src/OpenMesh/Core/OpenMesh.build/Debug/OpenMeshCore.build/Script-DD82B41B19DA4A22A63FE961.sh
cd /Users/Turlier/Dropbox/git/OpenMesh-7.1
/bin/sh -c /Users/Turlier/Dropbox/git/OpenMesh-7.1/build/src/OpenMesh/Core/OpenMesh.build/Debug/OpenMeshCore.build/Script-DD82B41B19DA4A22A63FE961.sh
/usr/local/Cellar/cmake/3.12.1/bin/cmake -E copy_if_different /Users/Turlier/Dropbox/git/OpenMesh-7.1/build/src/OpenMesh/Core/Debug/libOpenMeshCored.7.1.dylib /Users/Turlier/Dropbox/git/OpenMesh-7.1/build/Build/lib/libOpenMeshCored.7.1.dylib
/usr/local/Cellar/cmake/3.12.1/bin/cmake -E copy_if_different /Users/Turlier/Dropbox/git/OpenMesh-7.1/build/src/OpenMesh/Core/Debug/libOpenMeshCored.dylib /Users/Turlier/Dropbox/git/OpenMesh-7.1/build/Build/lib/libOpenMeshCored.dylib
Error copying file (if different) from "/Users/Turlier/Dropbox/git/OpenMesh-7.1/build/src/OpenMesh/Core/Debug/libOpenMeshCored.dylib" to "/Users/Turlier/Dropbox/git/OpenMesh-7.1/build/Build/lib/libOpenMeshCored.dylib".
make: *** [OpenMeshCore_buildpart_1] Error 1
Command /bin/sh failed with exit code 2
I’m not sure what I would need to modify in the CMakeLists.txt to avoid this compilation error on Xcode.
Many thanks in advance for your help.
Best,
---
Hervé Turlier, PhD
Team Multiscale Physics of Morphogenesis,
Center for Interdisciplinary Research in Biology
Collège de France / CNRS UMR7241 / INSERM U1050
11, place Marcelin Berthelot
75231 Paris Cedex 05, FRANCE
Tel: +33 (0)144271410
www.virtual-embryo.com
Dear OpenMesh creators,
First of all, thank you so much for creating this nice library. I've just
started using your library, but it seems to have lots of functionalities to
handle meshes.
I have some troubles when I add faces. add_face() function generally works
fine, but when the face vertices violate the add_face internal rules, it
just skips adding faces or sometimes it crashes. Is it possible to have
error code and have a chance to record this information for future
correction? I think I may need to modify add_face() and recompile for my
purpose, but I wanted to ask if there is built-in method to address this
issue.
A popular 3D print model (3DBenchy.stl) gives crash when I add faces into
OpenMesh data structure.
Thanks in advance.
Best,
Yun
Hello,
I have a question about the mesh traits included with OpenMesh.
When I want to use a (Tri)Mesh with double precision, it seems that I
need to copy DefaultTraits from traits.hh to define my own mesh traits.
The default traits are mostly fine, but single precision.
Are there somewhere official double precision traits? Currently I define
my own traits by copying default traits and changing the vector types to
Vec3d, but this requires careful handling when linking libraries to use
the same mesh structure, making the build system and includes more
complicated.
It would be nice, if something like
template<typedef Scalar>
struct DefaultTraits { typedef OpenMesh::VectorT<Scalar, 3> Point; ... }
could be added to a future OpenMesh release, so the same standard data
structure could be reused from OpenMesh instead of bundling an own
traits struct with the code.
Please CC me in answers, as I am currently no member of the list.
with kind regards,
Alexander Schier
No worries. Glad it’s back up!
On Sun, Aug 5, 2018 at 12:13 PM Jan Möbius <moebius(a)cs.rwth-aachen.de>
wrote:
> Hi,
>
> sorry, the server crashed. Should be back online now.
>
> Best,
> Jan Möbius
>
> Am 04.08.2018 um 18:44 schrieb Jan-Michael Tressler:
> > Is OpenMesh.org down for others as well? I couldn't open the site or
> > access the svn.
> >
> > Thanks,
> > Jan-Michael
> >
> >
> > _______________________________________________
> > OpenMesh mailing list -- openmesh(a)lists.rwth-aachen.de
> > To unsubscribe send an email to openmesh-leave(a)lists.rwth-aachen.de
> >
> https://lists.rwth-aachen.de/postorius/lists/openmesh.lists.rwth-aachen.de
>
>
> --
> Jan Möbius
> Department of Computer Science 8
> Aachen University of Technology (RWTH)
> Ahornstrasse 55, 52074 Aachen, Germany
>
> Phone ++49 (0)241 80-21802
> Fax ++49 (0)241 80-22899
> mailto:moebius@cs.rwth-aachen.de
> http://www.rwth-graphics.de
>
>
Dear OpenMesh maintainers,
When assigning a mesh as follows
meshB.assign_connectivity(meshA);
with meshA comprising a vertex status property,
meshB.release_vertex_status();
makes OpenMesh crash. The reason seems to be that meshB has a "valid"
vertex status property handle, but not a vertex status property. I
attached a minimal example to reproduce.
I suspect this bug to have been introduced by this commit
https://graphics.rwth-aachen.de:9000/OpenMesh/OpenMesh/commit/29cbe82048474…
best regards,
Simon
--
Dr. Simon Flöry
Rechenraum e.U.
Stutterheimstraße 16-18/2/20a, 1150 Wien, Austria
phone: +43 (0)1 789061269
mobile: +43 (0)681 81502316
skype: simon.floery
Commercial Register No. FN 385715d (Handelsgericht Wien)
This e-mail contains confidential information. If you are not the
intended recipient, you must not disclose nor use the contents of
this e-mail. In case you have received this e-mail in error, we
ask you to inform us and delete this e-mail.
I'm an undergraduate studying in ZJU, China.
Apologize for my awful English.
I am working on an academic project which refers to OpenMesh, it's given by my instructor.
The project was originally built on VS2010(x86)-addin-Qt4, referring OpenMesh2.3.
But I got a compile error after setting the path and other configures, the error as follows:it's an error in specialization: cannot convert from overload function to iterator template
Here are some tries that I made to solve this problem problem but failed:
add _USE_MATH_DEFINES and _SCL_SECURE_NO_WARNINGS to preprocessor (still error)
change the reference of OpenMesh to V6.3(2015 x64) (unresolved external symbols)
For the entire project is based on 32-bit, using other libraries such as opencv and eigen etc, i may not try to convert the project into 64-bit, so is there any way to solve( or ignore) this specializaion error? I'm almost stressed myself out.
Hoping and thanks for any reply!
Best wishes!
--
周洋 Zhou Yang
Zhejiang University | 浙江大学
Chu Kochen Honor College | 竺可桢学院
Computer Science and Technology | 计算机科学与技术
Tel: +86 18867153005
Email:
3150104024(a)zju.edu.cn
Hello everybody,
First, thanks a lot for your neat work on openmesh! I am creating meshes
for 3D modelling as a part of my masters thesis and I am glad to use a well
written library.
I am able to build many things and play with it thanks to openmesh,
however I encounter some troubles from time to time. I asked some
communities (stackoverflow for instance) but the subject does not seem to
be hot right now, and experts are hard to find, so I am asking you.
I use openmesh with Python 3.6. Openmesh was installed with a 'pip install
openmesh' :
*1/ First*, I wanted to add custom propetries to vertices of the mesh, it
does work but does not write in the file, or it is not read when the file
is re-opened, here is my code :
import openmesh as OM import numpy as np
mesh = OM.TriMesh()
#Add some vertices
vh0 = mesh.add_vertex(np.array([0,0,0]));
vh1 = mesh.add_vertex(np.array([1,0,0]));
vh2 = mesh.add_vertex(np.array([1,1,0]));
vh3 = mesh.add_vertex(np.array([0,1,0]));
#Create some data
data = np.arange(mesh.n_vertices)
#Add custom property for vh in mesh.vertices():
mesh.set_vertex_property('prop1', vh, data[vh.idx()])
#Check properties have been added correctly
print(mesh.vertex_property('prop1'))
#prints data matrix
OM.write_mesh('mesh.om',mesh)
#Re-load mesh in another instance :
mesh1 = OM.TriMesh()
mesh1 = OM.read_trimesh('mesh.om')
#Check property is still there print(mesh1.vertex_property('prop1'))
#Prints a matrix of 'None'...
So, I cannot save then read a custom property. (So far, I save custom
properties into a csv file, which is okay but not convienient.)
*2/ Another issue* I encounter is when I want to save a mesh into a vtk
file. The writter writes nothing . Here is my code :
import openmesh as OM
mesh = OM.TriMesh()
#Add some vertices
vh0 = mesh.add_vertex([0,0,0])
vh1 = mesh.add_vertex([0,1,1])
vh2 = mesh.add_vertex([1,0,1])
vh3 = mesh.add_vertex([1,1,0])
#Add some faces (we are building a tetrahedron here)
mesh.add_face(vh0,vh1,vh2)
mesh.add_face(vh0,vh2,vh3)
mesh.add_face(vh0,vh3,vh1)
mesh.add_face(vh1,vh3,vh2)
OM.write_mesh('TEST_MESH.vtk',mesh)
Nothing is written. (When I put .ply or .om ... instead of .vtk, it
works just fine)
According to the documentation, it should work, so I don't know what I am
doing wrong. If you have any tips or advices, it would be very appreciated,
Thank you for your time, thank you for your help,
Charles Duvert.
