Hi @Erikbeeren ,
Thanks for letting me know. I wasn’t able to recreate the issue on my end and everything is working fine with OpenStudio 3.3:
It’s odd behavior like this that has made me recommend that people write measures in Ruby rather than trying to interact with them directly using IronPython as we are here. Invariably, editing the OSM like this is going to be a solution that doesn’t work on all machines and it’s really meant to be a stepping stone for people to write real Ruby measures.
Still, I think I know of a change that might solve this particular case for you. I just pushed it here:
You should be able to get the change on your end with the LB Versioner in an hour or so. Let me know if this solves the issue.