petz

did you have a look at the file i've attached above? it doesn't use loops but ad hoc groups in the xyzdist() function as well as a max search radius to speed up the search. even though xyzdist() is slower when using groups it shouldn't take ages for 100000 lines ...

you can exclude the current prim in the xyzdist() function by using groups. i've attached an example. hth. petz xyzdist_1.hipnc

it's easy, just reference the original geo. split_curve1.hipnc hth. petz

here's another one: split_curve.hipnc

the attached file shoud do the trick. hth. petz blerp_1.hiplc

not sure if that's what you're after but take a look at the attached file ... connect_points_unique.hipnc

please take a look at the attached file. i've slightly modified the old example and now it should work without problems. hth, petz human1.hiplc

there are a number of different ways how you could do this. for high polycount meshes, however, python might be fairly slow ... please take a look at the attached file. hth. petz landscape_slice_export_1.hiplc

here's another one which might be faster by avoiding the foreachLoop. hth. petz isolines.hipnc

1) the chopnet is used to procedurally adjust the “flowing” speed of the animated point (droplet). on flatter areas it simply gets slowed down. 2a) the curve (following the animated point) uses pscale as an attribute for fading out the size of droplets towards the tail of the curve. 2b) it’s used to delete all points which distance to the curve is above a given threshold 2c) xyzdist() returns the closest position on the prim in parametric coordinates (primuv). in our case it’s a curve and so it returns just one useful value which is u. in other words, it’s the position along the curve. hth. petz

please take a look at the attached file. hth. petz geo_flatten.hipnc

not exactly sure what you're after but if you want to calculate the gradient of curvature there is no better and easier way than what toadstorm already mentioned ... curv_gradient.hipnc

can't you use triangulate2d for this?

calculating the edge vector is not a problem but you can't store it on edges since houdini doesn't support edges as regular geometry elements. what you could do instead is to use convertLine and do all the computations on prims which you could then lookup by points from the actual mesh. or you could just write all the edge vectors into a detail array. please take a look at the attached file. hth. petz edge_vec.hipnc

due to the use of "remove shared edges" in the divideSop you got always two coincident polygons for every section. you need to delete duplicates and then make sure the normals of remaining prims are pointing into the same direction. instead, you could also set the output of the booleanSop to "seam" and check the curve direction based on point neighbours ... hth. petz