Closed VladimirIvan closed 3 years ago
I believe this is due to this commit https://github.com/ipab-slmc/exotica/commit/1facf3320592b6cc0759f70759151844ccfbb525 which explicitly checks whether a property is part of a known initializer. Since SphereCollision
and a few others locally change the type by explicit casting inside the task-maps for instance, this fails under the new behaviour.
When loading extended Initializer types in python,
exo.Setup.create_problem()
prints "Ignoring property" warnings (also see #608 ), e.g.:prints:
This is most probably caused by casting the python dict types where they don't have to be cast. This may be unavoidable though. TODO: investigate.
The following code performs the initialization in c++ and doesn't print any warnings: