7b986f6f77
using new table functionality
2022-12-07 21:55:20 +01:00
aaae8a701b
Fortran style adjustments
2022-12-07 17:29:03 +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
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
d0b86f54fb
consistent with new naming scheme
2021-04-25 08:16:26 +02:00
d59051f576
systematic names
2021-04-07 22:42:10 +02:00
869976c7a0
new names
2021-04-06 11:38:44 +02:00
710f5b74b2
Merge remote-tracking branch 'origin/development' into 2d-table-yaml
2021-03-29 00:00:39 +02:00
3b392281e4
consistent naming in HDF5 output
2021-03-25 19:22:59 +01: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
22a0aff488
separting thermal and damage sources
2021-02-13 18:41:30 +01:00
e855083964
systematic names
2021-02-11 14:19:04 +01:00
0d3b9b9f2a
correct reporting
2021-01-27 10:44:03 +01:00
1da1018d86
polishing
2021-01-26 23:56:20 +01:00
69f6de0e4f
consistent access pattern and naming
2021-01-26 23:44:11 +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
85dcd7af16
hierarchical naming
2021-01-26 20:30:47 +01:00
17ec5f378e
short names
2021-01-26 20:30:47 +01:00
6db58dffb7
filenames reflect hierarchical structure
2021-01-25 20:31:12 +01:00
Martin Diehl