| 00:04.00 | *** join/#brlcad cclldqksgqhrthua (~armin@dslb-088-066-138-100.088.066.pools.vodafone-ip.de) |
| 01:42.49 | *** join/#brlcad teepee_ (~teepee@unaffiliated/teepee) |
| 03:20.11 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 03:57.23 | *** join/#brlcad tandoorichick (~Thunderbi@117.222.152.72) |
| 04:39.50 | *** join/#brlcad amarjeet (~amarjeet@202.164.53.117) |
| 06:14.13 | *** join/#brlcad sniok (~sniok@89.252.29.238) |
| 08:30.26 | *** join/#brlcad Shalom (~Shalom@122.169.209.230) |
| 08:32.15 | *** join/#brlcad d_rossberg (~rossberg@104.225.5.10) |
| 09:06.53 | *** join/#brlcad merzo (~merzo@user-94-45-58-141.skif.com.ua) |
| 09:57.12 | *** join/#brlcad tandoorichick (~Thunderbi@117.222.152.72) |
| 10:19.02 | tandoorichick | d_rossberg: i'm making changes in my code according to your suggestions.. |
| 10:41.57 | tandoorichick | d_rossberg: the set functions take information from the CAD-specific structures - which are declared in the derived classes.. |
| 10:47.01 | d_rossberg | tandoorichick: these CAD-specific structures are hidden behind the PolygonialMesh (which is good), so there is no "set" from the user's perspective |
| 10:47.36 | d_rossberg | and this is what the interface's methods are for (i.e. for the user) |
| 10:48.14 | d_rossberg | btw, to speed your development up you should concentrate on one target system |
| 10:48.54 | tandoorichick | yes, that would help me.. |
| 10:49.19 | d_rossberg | i would recommend BRL-CAD: adde your files to a BRL-CAD library (libanalyze?) and use this as your platform |
| 10:49.40 | tandoorichick | ok sure, i will do that |
| 10:50.19 | tandoorichick | so just to be clear, is the code in those set functions ok? is it only the function name that needs to changed? |
| 10:53.53 | d_rossberg | not really, see my third point with the PolygonialMesh (starting with "And,") |
| 10:54.33 | d_rossberg | the vectors are fragile internal data structures which shouldn't be published to the outside |
| 10:55.37 | d_rossberg | maybe it becomes more clear when you write the mesh healing algorithm with the Polygonial mesh |
| 10:56.35 | tandoorichick | you mean, if i'm changing my dcel, those changes should be reflected immediately in the rt_bot_internal structure? |
| 10:57.41 | tandoorichick | ^through the PolygonalMesh class |
| 10:58.25 | d_rossberg | no, if you insert/delete a vertex, edge, or face this requires a series of changes to the vectors |
| 11:00.07 | tandoorichick | okay.. |
| 11:00.07 | d_rossberg | this changes should be done by atomic PolygonialMesh methods which guarantee an always intact data set (not necessaraly in rt_bot_internal, but in the PolygonialMesh internal structures, e.g. DCEL) |
| 11:01.33 | d_rossberg | define a basic set of get- and set-operationd which fulfill the requirements of your healing algorithms |
| 11:02.11 | tandoorichick | okay.. i thought i could add them as and when i needed them while writing the mesh healing algorithms.. |
| 11:02.44 | tandoorichick | as of now, i concentrated on getting information from the CAD-specific structures and putting them in the DCEL |
| 11:02.56 | d_rossberg | e.g. int GetTwin(int edgeId) |
| 11:04.03 | d_rossberg | your vectors are more candidates for private PolygonialMesh data members |
| 11:04.36 | d_rossberg | you could initialize the in the constructor(?) |
| 11:05.01 | d_rossberg | e.g. in BrlcadMesh::BrlcadMesh(rt_bot_internal *bot_mesh) |
| 11:05.56 | tandoorichick | i didn't get you, initialise what in the constructor? |
| 11:06.10 | d_rossberg | DCEL |
| 11:07.53 | tandoorichick | but how would we get all the information as vertex, edge and face records? |
| 11:09.57 | d_rossberg | arene't you vectors (std::vector<DCEL_Vertex>, ...) the structures to hold this information? |
| 11:10.50 | tandoorichick | yeah.. |
| 11:11.50 | d_rossberg | so make them protected members of the PolygonialMesh base class |
| 11:12.22 | d_rossberg | and add access functions to PolygonialMesh to work with them |
| 11:13.22 | d_rossberg | but hesitate to return the whole vectors |
| 11:14.47 | tandoorichick | okay, understood.. |
| 11:15.06 | d_rossberg | btw, you could think about using a map instead of a vector, using the id as index |
| 11:15.33 | tandoorichick | ok, sure.. |
| 11:22.07 | tandoorichick | d_rossberg: one more thing, i had started planning out the zippering gaps algorithm.. i had also proposed a stitching algo. do we decide on the two based on the tolerance values for zippering and stitching (eg: if the dist if <2 units, zipper, else if dist <4 units, stitch? or uniform throughout, based on what the user wants? the first method seems a little tricky |
| 12:10.04 | d_rossberg | sounds like you need a tolerance parameter for your algorithm, with a reasonable default for the libged (TCL) function |
| 12:17.38 | *** join/#brlcad teepee_ (~teepee@unaffiliated/teepee) |
| 12:31.10 | *** join/#brlcad yorik (~yorik@189-46-37-177.dsl.telesp.net.br) |
| 13:51.46 | *** join/#brlcad Shalom_ (~Shalom@122.169.209.230) |
| 14:11.04 | *** join/#brlcad Mathnerd314 (~quassel@supertux/Mathnerd314) |
| 15:17.26 | *** join/#brlcad amarjeet (~amarjeet@101.213.190.18) |
| 15:28.40 | *** join/#brlcad asad_ (~asad00@host10-2.natpool.mwn.de) |
| 17:03.24 | *** join/#brlcad merzo (~merzo@2-2-133-95.pool.ukrtel.net) |
| 17:05.53 | *** join/#brlcad merzo (~merzo@2-2-133-95.pool.ukrtel.net) |
| 17:15.02 | *** join/#brlcad amarjeet (~amarjeet@101.220.156.233) |
| 17:51.06 | *** join/#brlcad ickby (~stefan@x5d84cbd5.dyn.telefonica.de) |
| 17:54.30 | *** join/#brlcad Mandeep_Singh (~mandeep@59.95.82.44) |
| 17:59.35 | *** join/#brlcad ickby_ (~stefan@x5d84cbd5.dyn.telefonica.de) |
| 18:04.53 | *** join/#brlcad merzo (~merzo@2-2-133-95.pool.ukrtel.net) |
| 18:06.54 | *** join/#brlcad merzo (~merzo@2-2-133-95.pool.ukrtel.net) |
| 18:15.44 | *** join/#brlcad ickby (~stefan@x5d84cbd5.dyn.telefonica.de) |
| 18:29.27 | *** join/#brlcad Mandeep_Singh (~mandeep@59.95.82.44) |
| 18:33.48 | maths22 | brlcad: I didn't realize I had buildbot running. Thank you |
| 18:33.53 | maths22 | *jenkins |
| 18:55.32 | *** join/#brlcad ickby (~stefan@x5d84cbd5.dyn.telefonica.de) |
| 18:57.38 | *** join/#brlcad teepee (~teepee@unaffiliated/teepee) |
| 19:27.44 | *** join/#brlcad asad_ (~asad00@host10-2.natpool.mwn.de) |
| 22:05.22 | *** join/#brlcad teepee_ (~teepee@unaffiliated/teepee) |
| 23:10.27 | *** join/#brlcad teepee (~teepee@unaffiliated/teepee) |