f1f658bbd2
Merge remote-tracking branch 'origin/development' into plastic-name-behavior-fix
2021-07-26 15:07:53 +02:00
1c17fbb97a
[skip ci] Merge branch 'master' into development
2021-07-26 15:02:29 +02:00
5b18fcf803
Merge commit 'v3.0.0-alpha4-172-g93814054d'
2021-07-26 15:02:14 +02:00
93814054d5
[skip ci] updated version information after successful test of v3.0.0-alpha4-171-g6a9c892d7
2021-07-26 15:02:14 +02:00
59c69d069c
[skip ci] Merge branch 'master' into development
2021-07-26 13:30:27 +02:00
ce4052a49d
[skip ci] updated version information after successful test of v3.0.0-alpha4-141-g18dbda784
2021-07-26 13:30:08 +02:00
6a9c892d7b
Merge branch 'write_ipdisplacements' into 'development'
...
Write ip displacements
See merge request damask/DAMASK!414
2021-07-26 09:01:04 +00:00
18dbda7843
Merge branch 'YAML-1D-bugfix' into 'development'
...
YAML 1D bugfix
See merge request damask/DAMASK!417
2021-07-26 08:32:45 +00:00
b3f5e12232
using burgers vector of tw/tr system seems to make more sense here
...
otherwise twinning will not work in many cases.
Matching number is only required for nucleation of tw/tr
2021-07-24 18:37:25 +02:00
f22f30e05d
same functionality as for 1D
2021-07-24 14:27:00 +02:00
d6ce721a25
need to check type of leaf
...
otherwise, using a [list] where a scalar is expected results in a crash,
not in a meaningful error message
2021-07-24 12:10:59 +02:00
931dc99557
not used
...
climb formulation was updated a while ago
2021-07-24 11:21:07 +02:00
6f906647eb
documenting hex
2021-07-24 09:35:27 +02:00
d4ffc778c2
easier to read
...
removed comment regarding use of dot_state in kinetics_t(w/r). Data stored
in dotState is not reliable, FPI integrator for writes to it and Runge-Kutta
calls the dot state function at different time steps
2021-07-24 07:11:31 +02:00
527fd306e2
change of behavior
...
- gamma (state) increases monotoneously
- region of spontaneous annihilation is ignored in dipole formation
2021-07-23 22:25:06 +02:00
2a78174547
standard names in source code
2021-07-23 22:17:00 +02:00
c46813657f
better to understand
2021-07-23 21:56:34 +02:00
2d1d99542c
takeover from original paper
2021-07-23 21:51:51 +02:00
f96b0371ac
proper output name/format
2021-07-23 21:48:40 +02:00
6936ecb091
sl is the subscript for slip
2021-07-23 21:36:26 +02:00
6c53615d11
[skip ci] updated version information after successful test of v3.0.0-alpha4-137-gb69b85754
2021-07-23 17:48:05 +02:00
b69b857542
Merge branch 'polishing' into 'development'
...
whitespace adjustments and consistent names
See merge request damask/DAMASK!416
2021-07-23 14:15:32 +00:00
d216e77ca6
default values for p/q are dangerous
2021-07-23 09:07:39 +02:00
2cc8612572
consistent variable names
2021-07-23 07:16:08 +02:00
f6378790f1
following python
...
we might want to rename the whole module from 'lattice' to 'crystal'
2021-07-23 06:46:17 +02:00
f5af352644
whitespace adjustments
2021-07-23 00:09:51 +02:00
d682b477dd
following paper
2021-07-22 23:22:45 +02:00
85fd2e3fad
not needed
2021-07-22 23:15:20 +02:00
3f7043de74
standard name
2021-07-22 23:15:20 +02:00
7e27baacfe
missing conversion
2021-07-22 21:39:05 +02:00
a03aa97970
default name
2021-07-22 15:41:09 +02:00
4fab078d18
multinomial tested+simplified
2021-07-22 15:31:30 +02:00
d9aa638ad7
shorter
2021-07-22 15:11:38 +02:00
11cdc63a27
use reasonable load case, even for compile test
2021-07-22 14:00:25 +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
aa03e59306
same statement, different syntax but silences gfortran runtime warning
...
with automated LHS, compiling in DEBUG mode (tested for mesh solver)
gives:
home/m/DAMASK/src/phase_mechanical.f90:1010:43: runtime error: signed integer overflow:
-9223372036854775808 - 1 cannot be represented in type 'integer(kind=8)'
2021-07-22 11:24:10 +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
9767866c1e
cleaned+updated test
2021-07-22 07:24:36 +02:00
de7ef43095
documenting/silencing gfortran
2021-07-21 23:49:24 +02:00
aace5d25a8
initialization needed
2021-07-21 23:19:41 +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
Martin Diehl