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
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
df1fe39dc2
Merge remote-tracking branch 'origin/development' into write_ipdisplacements
2021-07-21 13:30:12 +02:00
6f19113072
L, P, F, etc. are second order tensors
2021-07-21 06:19:04 +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
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
53b7aab29d
use ph,en access pattern
2021-07-18 09:48:49 +02:00
6ad6158bfb
(en)try is the name used in the DADF5 file
2021-07-18 09:44:52 +02:00
57ad308a7f
readable
2021-07-18 09:22:12 +02:00
d068f45aa0
avoid superflouos damage calculations
2021-07-17 15:25:00 +02:00
c109d5a37b
better have different physics separated
2021-07-17 14:06:48 +02:00
f9edeb40a5
descriptive names
2021-07-17 11:50:21 +02:00
e6d25294d3
separating functionality
2021-07-16 23:32:08 +02:00
fc735d6391
substate0 only needed for staggered state-stress integration
2021-07-16 23:19:48 +02:00
777620b800
polishing
2021-07-16 22:41:38 +02:00
594ad2c310
semi-separate handling of damage
2021-07-16 22:22:41 +02:00
2b24224c7e
more meaningful name
2021-07-16 20:52:41 +02:00
ed6b1be352
solver handles terminally ill
2021-07-16 20:43:08 +02:00
2a84aa7ae4
obvious, no need for comment
2021-07-16 20:32:21 +02:00
5f78f1753c
split up thermal
...
only for grid at the moment
2021-07-16 18:03:38 +02:00
3f0eafd640
first step towards separating of mechanics, thermal, and damage
2021-07-16 17:53:11 +02:00
013c4c0a92
common variable names
2021-07-16 10:31:40 +02:00
2f1fa8292b
unify style to majority of occurences
2021-07-16 10:30:45 +02:00
3830492791
Merge remote-tracking branch 'origin/development' into write_ipdisplacements
2021-07-15 17:34:44 +02:00
4d6a9a51ed
correct logic
2021-07-15 17:32:41 +02:00
94843becda
writing ip displacements (algorithm contain bugs)
2021-07-14 19:33:54 +02:00
766db0524f
Merge remote-tracking branch 'origin/Marc-start-material-at-0' into marc2021.2
2021-07-14 18:06:57 +02:00
05b319fbfb
easier to read
2021-07-14 06:33:04 +02:00
2ffa6cac70
Merge remote-tracking branch 'origin/development' into Marc-start-material-at-0
2021-07-14 06:15:46 +02:00
ce3b4d2a2a
Merge branch 'development' into YAML-fixes
2021-07-13 20:27:21 +02:00
45abca90c5
stricter
...
example of invalid YAML--> mechanical:{type: pass}
2021-07-12 22:17:02 +02:00
d2560ebb39
function should return either 'true' or 'false' and not bear the responsibility to throw errors
...
We were forcing every colon to indicate either key or key: value
2021-07-12 21:42:51 +02:00
df9a94422f
0-based indexing in MSC.Marc
...
inline with Python library and grid, still need to decide on mesh (neper
is 1-based)
2021-07-10 09:49:29 +02:00
Martin Diehl