MPM with Grasshopper #6
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- new button for analysis - new button for run - creation of all necessary files for mpm - dynamic naming of projects
- output of projectparameters in corresponding files - structure of project parameters for MPM almost completely avaiable as "hard code" - only grid output process is not finished yet
- static output for project parameters file completed - work on output of material parameters started
new MPM analysis, new mpm analysis class with more input parameters; constructed similiar to other analysis types and classes
- errors in AnalysisMpm_new corrected - field for bodymesh in AnalysisMpm_new introduced - reverse of all changes in outputkratos FEM - if for mpm analysis added to outputkratos FEM - WriteProjectParameters function added to outputkratos FEM
- bugs in outputKratosFem fixed - new classes for non linear material - new class for transient analysis
Function write Project parameters is finished: - differentation between static and dynamic analysis is implemented - function can access objects of class TransientAnalysis - variable names of Transient analysis were changed again, otherwise problems with already existing code
- new datastructure has to be established: - where formerly mesh was used, now geometry has to bes used - this requires additional classes: SolidElement and SolidElementProperties -these were created, but are far from finished yet - UserDataMesh and RefinementMesh had to be created, but are also far from finished
- UserDataUtilities: new function GetOrCreateUserDataMesh - modified MPM_GH_new to extract mMeshList from DataTree - Adapted AnalysisMPM_new to new datastructure - added a new constructor to OutputKratosFEM - changed description of input parameters in SolidElement
tteschemacher
commented
Jul 18, 2022
| if (!DA.GetData(1, ref material)) return; | ||
|
|
||
| double thickness = 0; | ||
| if (DA.GetData(2, ref thickness)) return; |
There was a problem hiding this comment.
Suggested change
| if (DA.GetData(2, ref thickness)) return; | |
| if (DA.GetData(2, ref thickness)); |
You have to remove the return statement, here. Otherwise, the function ends here even though you have actually provided the default paramater.
Bug from SolidElement removed in accordance with pull request and advice from @tteschemacher Bug from MPM_GH_new.cs for output parameter (analysis) removed -> now no errors in standard procedure
In MPM_GH_new.cs the function ResetUserData was added in accordance with Model_IGA_GH Code in MPM_GH_new.cs was cleaned
Project files of GiD for simple set-up added
Grid mesh output apart from boundary conditions ok, check if nodes from body mesh are also necessary also grid mesh output widely static in many parameters
add boundary condition direct on solid?
Output of non-conforming grid conditions not yet finished
now no double node number in body and grid mesh, no double element numbers in body and grid meshes; in contrast to gid mdpa files, nodes and elements of body mesh come first in grid mesh
Body and grid mdpa files are correct apart from contrary numbering of elements. It remains to be checked if this causes problems
Readme.md for LSA example finished
Output Kratos FEM: much new stuff for non-conforming bcs
…tly. Output in background mdpa is working and penalty process is given out in project parameters.
…ody meshes OutputKratosFEM: comments on how to restructure writing of non-conforming boundary conditions, conforming boundary conditions and body.mdpa
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a work in progress PR for the implementation of MPM in Grasshopper by @phfranz .