Hi all,
I observed that data.remember node is capturing data while running through GD engine while its placed right after Revit depended node, in this case solid.geometry. If I could place it after boundingbox.cuboid my whole execution speed will increase significantly but, by placing it like that, the graph is not working properly. @jacob.small can you please help me with this?
You have wires from the Element.Solids into List.Flatten and then into bounding box nodes which eventually get serialized. However you keep using the flattened list of complete solids (not the bounding box) in the ListShuffle.SeededShuffle, and as there isn’t a proceeding remember it’ll shuffle ‘null’, and the results from it will be null, likely all the way to your final output.
If you wire the Data.Remember into the upper shuffle as well you might be all set, but you might have also removed necessary data.
Initially i were capturing cube data like this in the above image, In this case Data. Remember node is not capturing data. I made some changes, and made the script as below image. Now data is capturing perfectly. I am not getting why? at the end both are cubes with same list structure right?
The data.remember node in both screenshots has 65 items in it. My guess is the change is not in that section of the graph but elsewhere. Open the file in Dynamo Sandbox instead to see where the issue is.
I guess not. Because made only this specific change and in generative design study problem solved. I have shared both solved and old one.can you please check?
https://drive.google.com/drive/folders/1k0K0mjRVDywYwg9VJv_oHelbebMkX1FE?usp=sharing
I’m seeing more than a single change in the document difference and the previous screenshot certainly doesn’t align anymore (least not that i can find), but I can’t even get your initial Python to work so I’m unable to quickly test (perhaps you’re using the old IronPython2 engine, in which case it’s time to update to a supported version).
All of that said, if GD isn’t returning any results it may just be that the list of cuboids being different is causing the engine to shuffle (bad node to use for generative workflows btw as you don’t benefit from the genetic algorithm when you us it) into a different order, resulting in a null.