Structural Mechanics Cases #7
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,54 @@ | ||||||
| class StructuralMechanicSolver { | ||||||
| constructor() { | ||||||
| this.addInput("model_import_settings", "map"); // 0 | ||||||
| this.addInput("material_import_settings", "map"); // 1 | ||||||
| this.addOutput("solver_settings", "map"); | ||||||
| this.properties = { | ||||||
| "solver_type" : "Static", | ||||||
|
There was a problem hiding this comment.
Suggested change
new syntax |
||||||
| "model_part_name" : "Structure", | ||||||
| "domain_size" : 2, | ||||||
| "echo_level" : 0, | ||||||
| "analysis_type" : "non_linear", | ||||||
| "model_import_settings" : { | ||||||
| "input_type" : "mdpa", | ||||||
| "input_filename" : "Ring" | ||||||
| }, | ||||||
| "material_import_settings" : { | ||||||
| "materials_filename" : "StructuralMaterials.json" | ||||||
| }, | ||||||
| "time_stepping" : { | ||||||
| "time_step" : 1 | ||||||
| }, | ||||||
| "line_search" : false, | ||||||
| "convergence_criterion" : "residual_criterion", | ||||||
| "displacement_relative_tolerance" : 0.0001, | ||||||
| "displacement_absolute_tolerance" : 1e-9, | ||||||
| "residual_relative_tolerance" : 0.0001, | ||||||
| "residual_absolute_tolerance" : 1e-9, | ||||||
| "max_iteration" : 10, | ||||||
| "rotation_dofs" : false, | ||||||
|
There was a problem hiding this comment. this should be variable, can you expose it like the domain size? There was a problem hiding this comment. I think ricc wanted those to be modified directly from the properties There was a problem hiding this comment. In the other GUIs this is automatically switched on depending on the user-defined elements. In this case, automating it would imply parsing the mpda (which we already do) and go through all the element types in the elements section. Not sure if this will be possible. What is not clear to me is how we can select this field from the properties (e.g. the properties of a shell element are almost identical to that of a 2D plane stress case without rotations). There was a problem hiding this comment. This is similar as the CL problem that appeared above. As @rubenzorrilla says we need to extract more info from the mpda, which is not a problem but also need to dynamically generate nodes based on inputs, which is something we are missing at the moment (but possible). I would leave it as is for this PR and make a separate one to implement those changes. |
||||||
| "volumetric_strain_dofs" : false | ||||||
| }, | ||||||
| this.domain_size = this.addWidget("combo","Domain Size", 2, function(v){}, { values:[2,3]} ); | ||||||
|
|
||||||
| this.size = this.computeSize(); | ||||||
| } | ||||||
|
|
||||||
| onExecute() { | ||||||
| this._value = Object.assign({}, this.properties); | ||||||
| this._value["domain_size"] = this.domain_size.value; | ||||||
| this._value["model_import_settings"] = this.getInputData(0); | ||||||
| this._value["material_import_settings"] = this.getInputData(1); | ||||||
|
|
||||||
| // Get the | ||||||
|
|
||||||
| this.setOutputData(0, this._value); | ||||||
| } | ||||||
| } | ||||||
|
|
||||||
| StructuralMechanicSolver.title = "Structural mechanic solver"; | ||||||
| StructuralMechanicSolver.desc = "Properties for the structural mechanic solver"; | ||||||
|
|
||||||
| LiteGraph.registerNodeType("solver_settings/StructuralMechanicSolver", StructuralMechanicSolver); | ||||||
|
|
||||||
| console.log("StructuralMechanicSolver node created"); //helps to debug | ||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same for the filename.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done