e1630e4057
consistent naming with Python module
2023-07-15 23:10:29 +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
d0b832e6f1
consistent with naming in HDF5_utilities
2023-06-03 17:06:32 +02:00
043d48d4d3
correct unit
2023-03-21 22:41:52 +01:00
13630325c3
notation following paper
...
https://doi.org/10.1016/j.jmps.2016.10.012
DAMASK paper
2023-03-13 17:23:28 +01:00
c1cb6a72c1
loops instead of code duplication
2023-03-12 13:40:45 +01:00
132640eed5
simplified
2023-03-12 13:40:45 +01:00
a40524da02
rename to wrapLines; additional formatting options; whitespace trimming
2023-02-28 14:59:30 -05:00
95a953d25b
more reasonable name
2023-02-28 07:58:10 +01:00
9418664604
report origin of configuration if given
2023-02-25 15:17:13 +01:00
0880649dd9
more systematic name
2023-01-23 08:31:59 +01:00
4af29d0393
Merge branch '247-naming-for-classes' into 'development'
...
Resolve "naming for classes"
Closes #247
See merge request damask/DAMASK!699
2023-01-19 16:37:45 +00:00
b4a500a194
Resolve "naming for classes"
2023-01-19 16:37:45 +00:00
da0a15f63a
string length is not know, avoid overflow
2023-01-10 11:54:13 +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
1b5194288b
polished tests, consistent variable name
2022-06-04 07:26:45 +02:00
a531b7ccae
transitioned remaining real exponents to int
2021-11-28 12:46:26 -05:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
fc5237fa80
using central values
2021-07-21 15:46:38 +02:00
6ad6158bfb
(en)try is the name used in the DADF5 file
2021-07-18 09:44:52 +02:00
f9edeb40a5
descriptive names
2021-07-17 11:50:21 +02:00
777620b800
polishing
2021-07-16 22:41:38 +02:00
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
ee80efd705
using new mappings
2021-05-22 22:52:05 +02:00
0fc7f66ef8
consistent names
2021-04-07 21:25:11 +02:00
cdae867beb
simplified
...
damage currently works only for single constituent
2021-04-07 09:11:40 +02:00
0d974648f0
part of damage, not of eigen
2021-04-06 12:18:48 +02:00
330803881b
variable 'damage' is not occupied anymore
2021-04-06 11:41:45 +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
5126370934
cleavageopening+anisobrittle are strongly coupled
2021-02-13 19:20:52 +01: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
7bec3e0363
use partitioned damage
2021-02-12 11:24:04 +01:00
f6be3fe0b7
no need for pointer
2021-02-12 07:58:00 +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