ab0e65c6bc
systematic names and sensible defaults
2021-06-25 15:12:54 +02:00
06e76c1a81
consistent default absolute tolerances
...
better use conservative values, users can easily relax if needed
2021-06-25 10:13:03 +02:00
fada9a7f6c
more meaningful order
2021-06-01 17:05:13 +02:00
2aa78a710b
correct capitalization
2021-05-21 22:05:09 +02:00
cdae867beb
simplified
...
damage currently works only for single constituent
2021-04-07 09:11:40 +02:00
330803881b
variable 'damage' is not occupied anymore
2021-04-06 11:41:45 +02:00
869976c7a0
new names
2021-04-06 11:38:44 +02:00
ce91537b0f
get_asXXs --> get_as1dXX
2021-03-11 18:40:16 +01:00
a7e2ed40dd
rename Nconstituents --> Nmembers
2021-03-04 15:16:36 -05:00
ab202b8e73
less verbose reporting
2021-02-13 13:07:35 +01:00
570086c814
hard code at max 1 damage mechanism
2021-02-13 13:07:12 +01:00
d9699b0f2e
simplified access pattern
2021-02-13 11:01:08 +01:00
775a51faa1
explicit instance mapping not needed
2021-02-13 10:11:39 +01:00
b3dde6d722
only one damage mechanism per phase
...
material.yaml specification is designed to allow more than one, but that
requires to have two phase fields etc.
For the moment, keep it as simple as possible.
2021-02-13 09:55:17 +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
0d3b9b9f2a
correct reporting
2021-01-27 10:44:03 +01:00
74a7be1607
[skip sc] more systematic naming
...
module name 'damagee' gets extra e for the moment to avoid conflict with
global variable 'damage'
2021-01-26 21:47:55 +01:00
1d0d05855a
no need to prefix local functions
2021-01-26 20:30:46 +01:00
6db58dffb7
filenames reflect hierarchical structure
2021-01-25 20:31:12 +01:00
Martin Diehl