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
0ca4d42678
PETSc 3.18.0 compatibility
...
CHKERR macros are now longer, should be replaced with PetscCall in the
future
2022-10-02 12:48:54 +02:00
64fad03b97
explicit casting
2022-06-27 23:39:54 +02:00
60e097a04e
something is wrong with interfaces for 64 bit
2022-06-27 22:35:29 +02:00
61dc14e0b9
Merge remote-tracking branch 'origin/development' into implicit-none-external
2022-06-27 15:13:20 +02:00
3b57934d6e
Marc precision handling
2022-06-27 08:37:41 +00:00
2f1904efec
only MPI_f08 is standard conforming
2022-06-21 23:11:22 +02:00
b8c3d75700
[skip sc] enforce interfaces (quick fix: declare as external)
2022-06-21 22:59:01 +02:00
6236ad52d1
consistent naming
2022-05-03 13:00:28 +02:00
bb83d20fe9
Merge branch 'development' into structure-improvements
2022-04-27 05:55:19 +02:00
dece12a1a6
remove unused CLI module inclusion
2022-04-26 12:19:13 -04:00
d41d03015a
better matching name
2022-04-24 17:38:59 +02:00
91b71fdff8
systematic naming scheme
2022-04-24 04:45:41 +02:00
34cc66f1bf
use old interface for previous PETSc versions
2022-04-04 08:14:48 +02:00
cfe01b83f8
avoid deadlock for MPI runs
2022-02-17 21:37:37 +00:00
b43695067d
Merge remote-tracking branch 'origin/development' into nonlocal-standard-access
2022-02-11 12:53:58 +01:00
345659b0e8
update sta file after each inc
2022-02-07 15:09:26 +01:00
6d78400f87
the concept of IP/element_ID should not be used at the DAMASK core
2022-02-05 07:29:00 +01:00
82dabe29c1
mesh: separate kind for DAMASK and PETSc integers
2022-01-13 16:30:42 +01:00
29530da579
use correct kind of constants for calls to MPI/PETSc
2022-01-13 13:50:30 +01:00
a7417a7ad7
default integer, PETSc integer, and MPI integer might be different
2022-01-13 12:02:33 +01:00
3fb5bd459c
pInt leftovers
2022-01-13 07:44:15 +01:00
43ae4983ed
fixed misaligned/too short "writing..." statements
2021-11-15 12:58:59 -05:00
69843d0833
Merge branch 'development' into pretty-print-init
2021-11-15 12:39:14 -05:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
8138d3a180
style adjustments
2021-11-11 23:59:48 +01:00
ba31ff7263
do not rely on ML per default
2021-11-11 23:23:14 +01:00
b4ff89f304
improved test
2021-10-27 22:54:26 +02:00
a00c6743c3
symbolic notation in numerics.yaml
...
- p_i: integration order
- p_s: shape function order
ensure working combination (p_s = p_i: full integration, p_s = p_i+1:
reduced integration)
2021-10-26 11:51:08 +02:00
5ac592eb9e
initialize L_(i/p), L_(i,p)0
2021-07-22 12:31:10 +02:00
69cc0b528b
do calculation for initialization
2021-07-22 11:38:03 +02:00
5b66db8a39
only mechanics at the moment
...
will be extended, but most likely differently
2021-07-22 10:12:43 +02:00
eb834b635d
unify notation with grid
...
consistent style: Symbols, not descriptions.
also removed untested/unused loginc functionality. Once load cases are
written in YAML, we can introduce the scaling as in DAMASK_grid
2021-07-22 08:48:44 +02:00
173a5f8e55
less public/unneeded variables
2021-07-22 07:48:01 +02:00
de7ef43095
documenting/silencing gfortran
2021-07-21 23:49:24 +02:00
58a7921966
no need for temp, pack instead of reshape for 1D array
2021-07-21 22:45:04 +02:00
b817c620a3
let the computer count
2021-07-21 21:25:33 +02:00
23077fd58c
testing coordinates
...
I don't understand why this pattern exists (with w(2) = 3, w(3) = 2),
but it exists
2021-07-21 19:42:53 +02:00
5a04a1d661
let the computer do the counting
2021-07-21 19:41:14 +02:00
c56979e2ad
single source of truth
2021-07-21 18:47:19 +02:00
000007ba59
better test automatically
2021-07-21 18:06:37 +02:00
b1ba64e6af
understanding floating point precision
...
double can use 16 or 17 significant figures
- if the leading number is high (above 5 or so), only 16 figures are
significant.
- a trailing 1 is never significant
2021-07-21 18:04:50 +02:00
f25dee4c3a
quad points updated and rounded based on literature values
2021-07-21 14:34:18 +02:00
a919ac0aea
Merge branch 'write_ipdisplacements' of git.damask.mpie.de:damask/DAMASK into write_ipdisplacements
2021-07-20 15:35:48 +02:00
86d918367f
Round quadrature points
2021-07-20 15:34:13 +02:00
4a2e62fdb2
Merge branch 'development' into 'write_ipdisplacements'
...
# Conflicts:
# src/mesh/mesh_mech_FEM.f90
2021-07-19 17:19:40 +00:00
a654cd4fb1
To avoid fortran double variable truncation for quadrature points
2021-07-19 17:07:43 +02:00
97203ff551
document and keep definitions together
2021-07-18 23:30:30 +02:00
f9edeb40a5
descriptive names
2021-07-17 11:50:21 +02:00
ed6b1be352
solver handles terminally ill
2021-07-16 20:43:08 +02:00
Martin Diehl