I am developing a door renumbering script using Clockwork or Rhythm for a large project. The challenge lies in addressing doors that swing both into and out of rooms. I have already updated the door schedule to ensure that outward-swinging doors are correctly associated with their respective room numbers. However, when using the Doors.Rooms node in Dynamo, it still retrieves the original room data instead of reflecting my corrections. How can I make Dynamo recognize and read the updated room associations?
that happens when you run the script the secound time, it still remains the old data. when you open/close dynamo. When you run it, it should work!
Unfortunately, when I try Clockwork, it outputs an empty list. When I use Rhythm, it outputs the incorrect list (old schedule). In the case of Clockwork I’ve been unable to find the reason, might be Ironpython version or Python3. It would be the best option because it outputs both toroom and fromroom. But instead, its null. However Rhythm seems to find a room attribute, but it doesn’t match the schedule.
…that’s why I moved my door numbering and flipping to a pyRevit save/print event. So no one has to think about it ever.
I have created different families for each door. One with the point calculation reversed, so that the schedule would append the “toroom” correctly since the beginning. Nonetheless, Dynamo still outputs the wrong room number
Alternatively, I have troubleshot the Clockwork compatibility problem. I was able to find a version of IronPython that worked with my version. That solved the issue.
can you share the solution?