Input A is organized in a certain way, then Output B has it reorganized.
Where is that coming from ? It’s a big problem. I can officially report it, where’s the best place ?
Github
Input A is organized in a certain way, then Output B has it reorganized.
Where is that coming from ? It’s a big problem. I can officially report it, where’s the best place ?
Github
No one else is experiencing this problem ? Just me ?
Might be? It appears that this behavior might be related to the new by_zone option?
It appears like this component now iterates over a dictionary of the rooms keyed by their ‘identifier’,
which is not guaranteed to be in any specific order in python 2.x
Do the sensor grid outputs need to be in the same order of the input _rooms for your workflow? Seems like your graft hack works of for the moment?
It works but it will confuse users in the future. Could that be treated as a bug ? I could log an error report if necessary.
Could be. I’m not sure what the correct behavior would be for this component. I would say it definitely appears to be different behavior than previous versions, which I agree is always a bummer when it happens. @chris would know the intended behavior though.
Is it critical for some workflow that the output grids are in the same order as the input rooms?
That is the correct explanation, @edpmay .
Dictionaries in Python 2 are unordered. So the order can change each time. If the change in order is bothersome, we can replace the use of the native Python dictionary with an OrderedDict object from the collections module. You’ll find that some of the other components do this. Here is an example:
I’ll try to implement this on the sensor grid component in the next few days. Alternatively, if someone wants this feature earlier and can send our github repo a PR with the change using the “LB Export User Object” component, I’ll review and merge it.
I made the tweak to ensure the order is preserved:
You should be able to get it with the LB Versioner in an hour or so.
Hell, yeah community power