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
bd9cae11a5
allow multi line scalar list items.
...
If a scalar list item has ',', the parser would consider it as a separator and not a part of the string
For the moment, this scalar item is enclosed with double quotes ""
In the next step, the flow parser should be able to use this quotes as an indicator for strings
2021-07-22 15:51:33 +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
574cfd7034
Merge remote-tracking branch 'origin/development' into more-flexible-L
2021-07-22 00:20:33 +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
76572e4ca9
standard notation
2021-07-21 16:34:33 +02:00
e3e9dfdc60
following paper
2021-07-21 16:29:57 +02:00
8feeda6f05
phase_mechanical_elastic should store data related to elasticity
2021-07-21 16:23:21 +02:00
fc5237fa80
using central values
2021-07-21 15:46:38 +02:00
8259cb3cdc
notation as in paper
2021-07-21 15:03:28 +02:00
2fff191421
[skip ci] updated version information after successful test of v3.0.0-alpha4-117-g9f2c37761
2021-07-21 14:56:53 +02:00
b2e94974ca
short names
2021-07-21 14:52:37 +02:00
f25dee4c3a
quad points updated and rounded based on literature values
2021-07-21 14:34:18 +02:00
df1fe39dc2
Merge remote-tracking branch 'origin/development' into write_ipdisplacements
2021-07-21 13:30:12 +02:00
9427885b43
updated private
2021-07-21 13:29:59 +02:00
9f2c377612
Merge branch 'drop-1d-tensor-support' into 'development'
...
L, P, F, etc. are second order tensors
See merge request damask/DAMASK!415
2021-07-21 11:25:35 +00:00
9d349f8a7c
symbolic notation
2021-07-21 06:50:28 +02:00
b5bf1d525e
Merge remote-tracking branch 'origin/development' into more-flexible-L
2021-07-21 06:36:05 +02:00
6f19113072
L, P, F, etc. are second order tensors
2021-07-21 06:19:04 +02:00
575c84ad86
[skip ci] updated version information after successful test of v3.0.0-alpha4-114-gb98819a36
2021-07-20 20:01:14 +02:00
b98819a36c
adjusting names
2021-07-20 18:29:21 +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
85735605f8
more flexibility for the L in the load case
...
Note that mixed boundary conditions for L introduce an ambiguity.
Consider:
L = [[1.0, x, x],
[ 0, 0, 0],
[ 0, 0, 0]]
P = [[x, 0, 0],
[x, x, x],
[x, x, x]]
What we need is F^(n+1)=F_dot^(n+1) x Delta_t, where F_dot^(n+1) is
F_dot^(n+1)_ij = L_ik F^n_kj.
So component F_11 has contributions from L_12 and L_13. We first assume
L_12=L_13=0 and then choose F^(n+1)_12 and F^(n+1)_13 to get
P_12=P_13=0. This implicitly gives a solution for L_12 and L_13, which
is however only one out of infinitely many.
2021-07-20 07:10:28 +02:00
Franz Roters