Hi Arie!Thanks for your efforts!I looked in grasshopper3d website and found this:http://www.grasshopper3d.com/f...I tried to play around with this but couldn't get it to work.(see screen captures) https://uploads.disquscdn.com/... https://uploads.disquscdn.com/...I hope that at some point you'll be able to overcome this and incorporate the python script in the GH solution. it would make it a more elegant solution and help using this powerful script for other projects.Thanks again!

Hi Shalom!Here is the definition with the code in the GhPython component. It is quite heavy to run, it took 1.1 minute to calculate on an Intel i7, 4Gb RAM, 8 core - 2.0 GHz, so be careful when you switch the Boolean toggle to True.https://mega.nz/#!sZE2hRjC!FpT...Cheers!

Hi Shalom!Here is the definition with the code in the GhPython component. It is quite heavy to run, it took 1.1 minute to calculate on an Intel i7, 4Gb RAM, 8 core - 2.0 GHz, so be careful when you switch the Boolean toggle to True.https://mega.nz/#!sZE2hRjC!FpT...Cheers!

Hi Arie!Thanks so much for the updated GH, it works great, but there is one weird thing, I don't know if it's just with me.please check it out.when I run it I also get small artifacts: 22 surfaces and 14 curves that shouldn't be there.see screen grabs, Any ideas why, and how to avoid that?Thanks again, I think having the Python script inside the GH def and then combining the definition with the laying down and tagging is totally worth the extra computing time.Cheers!!

You're right Shalom, I'm also experiencing some weird artifacts. Somehow it doesn't delete those line pieces and surfaces. It also fails to do the Boolean Split operation at those points. Let me take a closer look, Cheers!

Hi Shalom, I think I managed to get the script running without these artifacts:https://mega.nz/#!0B1VVJhI!5OM...Cheers!P.S. takes again around 2 min to run the definition, as it is quite heavy

Hi Arie,Thank you! It works great.But, I'm sorry to say;)There are still 9 very small curves that are created from the operation, that indicate a little problem.at 9 points, the tips of the criss cross surfaces, intersect each other, but not enough to create the groove, so in reality they would bump into each other.Thank you!

Ah yes this might happen sometimes, when the strips barely touch each other, it is hard to get around this. It has to do with a tolerance setting inside the script. If you want, you could change this value yourself. Open the script and put "Rhino.RhinoDoc.ActiveDoc.ModelAbsoluteTolerance = 0.001" below "scriptcontext.doc=Rhino.RhinoDoc.ActiveDoc" to make sure the document tolerance is set accurately.The next thing you might want to change is the line "if intline and not checkint and leng>0.1:". You could change the number 0.1 to 0.05 or 0.001 depending on how much of the small lines you want to allow.In my case these settings worked without generating any artifacts, good luck!Cheers!

That worked great!Thank you,Cheers!!

Hi Shalom!Unfortunately you can't simply paste your Rhino Python script into the Grasshopper Python add on. This has to do with the active document the Python engine is using. The scriptcontext.doc stands for the active document Python is using, this can either be the Rhino.RhinoDoc.ActiveDoc (the Rhino document) or ghdoc (Grasshopper document). Rodrigo wrote this Python script for the Rhinodocument this is why it doesn't run within the Grasshopper environment. It can be done by rewriting the script for the Grasshopper environment, I tried all day but I get some weird errors. If I figure it out I'll post the def, but for now it is advised to use the script as described in the video.Good luckArie