Debugging Hops / rhino.compute processes

Grasshopper Hops
, , ,
1

Hi,

I’m currently trying to understand the debugging options I have when running elements locally through Hops / rhino.compute. As it stands, I can ask for a .json export of the last IO and Solver request/response, but I’m finding that to be of limited usefulness. I’ve also set up the system locally as a cluster, so I can do a manual/visual inspection of the expected I/O, but without being able to “look” into the hops element, as you would a cluster, I’m finding it difficult to trace where elements are falling over (as the cluster variation is performing to expectations). I also understand that there is a RHINO_COMPUTE_DEBUG* variable that can be enabled within a VM environment, but I’m assuming that isn’t available for those of us running locally (or if they are, where can I enable it and view the output / log)?

Are there any additional things I’ve overlooked, and what, if any, advice can folks provide?

Thanks,

J

*Edit: I’ve checked this guide: Rhino - Frequently Asked Questions and will enable and see what happens.

Edit 2: After enabling the RHINO_COMPUTE_DEBUG EV, things are going a lot smoother, didn’t realise I could enable it locally. Also creating temporary outputs at intermediate stages of the contained scripts is helping. If anyone else ever comes across this issue, enabling this EV and outputting intermediate stages are useful things to do.

3

Yes, I was just going to say that you can enable the RHINO_COMPUTE_DEBUG environment variable on a local machine and it should begin adding more information to the output console. I’m glad this is helping.

1 Like
4

It very much is, after days of banging my head against a wall, I’m finally starting to understand where things are going wrong :grinning_face_with_smiling_eyes: .