-
Notifications
You must be signed in to change notification settings - Fork 4
Known Issues
For general issues identified and planned to be fixed see the issue page.
There are some known limitations with the MidasCivil object model that may result in information being lost when pushing to the software. The known limitations are outlined below.
It is important that all unique section properties, materials, constraints and releases have a unique name, to be able to push all objects to MidasCivil. Objects with the same name will be treated as the same object.
It should be noted that Midas does not have an automatic mesh feature: the elements that you push to midas via the FEMesh BHoM object should reflect the mesh density you want in the model. Therefore, meshing of surfaces should be carried out within Grasshopper.
It is possible in MidasCivil to apply both a spring and a support to the same node, when this is read by the MidasCivil_Toolkit the spring will overwrite the support. MidasCivil does offer fixities within spring so this is considered bad modelling practice.
Beam Releases cannot be pushed as a individual BHoM object; it must be pushed along with a bar. This is because Midas Bar Releases are always related to a bar.