Simulate Early, Simulate Often... In Rhino
Wondering if there is a rule of thumb for how much hard drive space is required - maybe by the grid resolution or something?
I'm working on an assembly that is maybe 8'(ft) x ~6" x ~12", but it is highly detailed (see image) and in order to get accurate results I have resolution at 440874 elements. On running the simulation my HD ran out of space about 3 times. The simulation generated 300+GB of integration_.tmp files and locked up the machine. I have since moved some files and have 400+GB free on my C drive.
This simulation has run before successfully and the only thing I have changed is the restraints. Prior simulations had all restraint faces as fixed in X,Y & Z, but I have now refined them to release axes at certain locations to more accurately simulate actual conditions. Might the varied restraint conditions be increasing calculations & required memory space? Right now it's at 27% & is up to Integrate26.tmp - all these Integrate_.tmp files are 4,300,820KB. Seems to have finished the integration step as it jumped to 51% and no longer seems to be generating the Integrate_.tmp files.
Thank you for any light you can shed on this subject.
The amount of space required for the integration files is related to geometric detail and the resolution setting. In an ideal world where everything is made of cubes, the size of the integration file is proportional to the resolution. Unfortunately, everyone wants things with pretty curves and thin sections that make the file size quite unpredictable. :-)
P.S. I should add that under normal circumstances the plug-in will delete the integration files when it is done with them, but they can linger in cases where solving is canceled or the plug-in or Rhino stops working unexpectedly.
I just saw this again and want to note that the builds of Scan&Solve Pro after 2017.4.27 are much more miserly about usage of hard drive space for integration.
© 2023 Created by Michael Freytag. Powered by