d953e6bedf
unified style
2023-07-24 18:29:36 +02:00
1fdc5443b2
avoid code (loop) duplication
2023-07-21 08:39:46 +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
0880649dd9
more systematic name
2023-01-23 08:31:59 +01:00
b4a500a194
Resolve "naming for classes"
2023-01-19 16:37:45 +00:00
5c221e16e1
solver should not solve for field if homogenization description is absent
2022-12-29 19:08:05 +00:00
aaae8a701b
Fortran style adjustments
2022-12-07 17:29:03 +00:00
b9ee401ff5
add damage restart functionality and associated tests
2022-12-05 10:52:59 +00: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
bb65d58214
add read-in init phi, correct write-out damage result
2022-09-21 08:50:00 +02:00
445a091fec
easier to understand
2022-06-24 07:36:25 +02:00
78838c2f75
consistent variants including space
2022-06-08 23:27:09 +02:00
1b5194288b
polished tests, consistent variable name
2022-06-04 07:26:45 +02:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
b98819a36c
adjusting names
2021-07-20 18:29:21 +02:00
fada9a7f6c
more meaningful order
2021-06-01 17:05:13 +02:00
4713e0e85d
new names and mappings
2021-05-23 13:14:57 +02:00
887524bcc1
polishing
2021-04-11 16:09:29 +02:00
b2292986f4
distributing responsibilities
2021-04-11 13:42:50 +02:00
4b89e2f40c
sorted and documented
2021-04-11 08:32:13 +02:00
a386b82f74
distributing responsibility
2021-04-11 08:14:39 +02:00
d488f1708a
consistent naming
2021-04-11 07:41:59 +02:00
1b89032086
names as in DAMASK paper
2021-04-08 23:45:26 +02:00
c4765d3742
following paper
2021-04-08 13:31:21 +02:00
0fc7f66ef8
consistent names
2021-04-07 21:25:11 +02:00
1851b66cb4
use new data container
2021-04-07 14:56:11 +02:00
c4942e3f82
part of damage init
2021-04-07 13:22:22 +02:00
16f7af4c27
consistent interface
2021-04-07 13:02:42 +02:00
cdae867beb
simplified
...
damage currently works only for single constituent
2021-04-07 09:11:40 +02:00
c53927ad6f
not needed
2021-04-07 08:47:46 +02:00
cb6b7a5fb9
standardized names
2021-04-07 07:26:54 +02:00
49804c6e44
preparing split
2021-04-06 11:55:30 +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
9679c5403e
continue with cell based map (solver + homog)
2021-02-23 15:44:58 +01:00
d8112cc2e1
storing by instance just complicates the code
2021-02-23 13:45:06 +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
8b11af0d84
more sensible location
2021-01-25 15:13:17 +01:00
5a35c5ebc3
homogenization functionality
2021-01-24 22:44:47 +01:00
1f94a64ca6
part of homogenization
2021-01-24 18:47:19 +01:00
b58465415b
store damage parameter like temperature
2021-01-24 18:20:47 +01:00
32bb0d8c6e
new variables for damage
2021-01-20 21:37:43 +01:00
Martin Diehl