You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current default packing method spheresSST does not require panda3d which adds extra overhead and error messages during import.
Running a test recipe after disabling panda3d (by commenting out lines of code where it was used) resulted in a speedup of ~30%. This can be significant when generating a large number of packings.
Solution
Remove functions and imports that rely on panda3d. Currently, there is some code that uses it for real time display which is no longer an available feature.
Alternatives
Only remove panda3d from the spheresSST workflow while still keeping it in other places if needed.
The text was updated successfully, but these errors were encountered:
Use Case
Our current default packing method
spheresSST
does not requirepanda3d
which adds extra overhead and error messages during import.Running a test recipe after disabling
panda3d
(by commenting out lines of code where it was used) resulted in a speedup of ~30%. This can be significant when generating a large number of packings.Solution
Remove functions and imports that rely on
panda3d
. Currently, there is some code that uses it for real time display which is no longer an available feature.Alternatives
Only remove
panda3d
from thespheresSST
workflow while still keeping it in other places if needed.The text was updated successfully, but these errors were encountered: