b0809a8afe
function is obsolete
2023-08-28 17:59:37 -04:00
039d5e0fce
improved comments and naming
2023-07-24 18:46:06 +02:00
dc9d4bb5a9
centralized ID handling to enable cross-talking
2023-07-18 21:15:34 +02:00
26014aec1f
'true' kinematics first
2023-07-18 21:15:34 +02:00
2ae1f1f829
simplified
2023-07-18 21:15:34 +02:00
0324e7ece1
parameters should be spelled in capitals
2023-06-04 13:52:31 +02:00
ca1c22874b
consistent and short
2023-06-04 13:51:05 +02:00
87e74ef792
docstring polishing
2023-02-25 10:07:38 +01:00
327992871b
white space and style adjustments
2023-01-18 18:50:01 +01:00
4f69c7630d
competing damage models are not implemented
...
while there might be the chance that we need this, we better focus on
today's capabilities and don't make the material.yaml syntax more
complicated in anticipation of potential changes
2022-12-18 09:34:25 +01:00
df5487e1a9
Re-written YAML types
...
Strict typing for YAML
New access pattern requires to specify the expected type, i.e. 'scalar', 'list', or 'dict'. This ensures that the node offers the expected functionality instead of polluting 'tNode' with dummy functions which throw error messages if not overwritten.
The restructuring of the code allows to hierarchically construct methods without much code duplication.
Some aspects of the error messaging system have been improved.
2022-10-25 16:09:36 +00:00
78838c2f75
consistent variants including space
2022-06-08 23:27:09 +02:00
d6ba73d9e2
consistent names
2021-12-11 09:54:46 +01:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
a03aa97970
default name
2021-07-22 15:41:09 +02:00
f9edeb40a5
descriptive names
2021-07-17 11:50:21 +02:00
6651656903
isoductile is not working
2021-06-28 23:13:56 +02:00
1eb1e54f78
adjustment to new structure/names was missing
...
reason: test missing/not good
2021-05-06 08:47:30 +02:00
74548d5f51
new names (as in HDF5 out)
2021-04-12 21:29:04 +02:00
0fc7f66ef8
consistent names
2021-04-07 21:25:11 +02:00
0d974648f0
part of damage, not of eigen
2021-04-06 12:18:48 +02:00
3b392281e4
consistent naming in HDF5 output
2021-03-25 19:22:59 +01:00
5a1ca012f8
more suitable data structure
...
no need to know (ip,el) at the constitutive level
2021-02-14 14:36:56 +01:00
18971d7d8b
separation by instance does not add any value
2021-02-14 10:26:33 +01:00
9481b16878
missing renames
2021-02-13 19:10:13 +01:00
8dc53344ec
'kinematics'=>'eigen', now part of 'mechanics'
2021-02-13 18:52:37 +01:00
22a0aff488
separting thermal and damage sources
2021-02-13 18:41:30 +01:00
72c099dbbe
store data separetly
2021-02-13 15:06:27 +01:00
f95e3bc08d
simplified access pattern
2021-02-13 07:25:48 +01:00
830d00fa67
simplified structure
...
choice of damage model triggers eigendeformation, no repeated variables
This implementation is the most ugly hack I could imagine. I just serves
the purpose of having a stable material.yaml
2021-02-12 22:46:26 +01:00
e855083964
systematic names
2021-02-11 14:19:04 +01:00
Philip Eisenlohr