I've noticed in the solid mechanics module that completeSetup() will give numerical errors if certain types of parameters, e.g. Young's modulus, are not initialized (and therefore default to 0). I think LiDO users are susceptible to forgetting to initialize parameter fields before passing the serac solver to a graph node as they are expecting the decision variables from the graph to populate parameter fields within design iterations. Since parameter fields can have many different physical meanings it would be impossible to come up with meaningful defaults, but it would be useful to output a warning message to users if parameter fields are not updated to aid in the debugging process.
I've noticed in the solid mechanics module that
completeSetup()will give numerical errors if certain types of parameters, e.g. Young's modulus, are not initialized (and therefore default to 0). I think LiDO users are susceptible to forgetting to initialize parameter fields before passing the serac solver to a graph node as they are expecting the decision variables from the graph to populate parameter fields within design iterations. Since parameter fields can have many different physical meanings it would be impossible to come up with meaningful defaults, but it would be useful to output a warning message to users if parameter fields are not updated to aid in the debugging process.