100215edb6
Merge remote-tracking branch 'origin/development' into YAML-improvements
2021-08-02 16:57:07 +02:00
c5a80bc75d
more readable
2021-08-02 16:50:21 +02:00
e89a03d456
Suggestion by @Franz
2021-07-28 18:04:52 +02:00
578ee2b214
Merge remote-tracking branch 'origin/development' into YAML-improvements
2021-07-28 12:15:09 +02:00
3d7f15c940
meaningful error message incase of mismatch in quotes
2021-07-28 12:14:00 +02:00
5d0c0f4283
outdated instructions
2021-07-27 16:44:52 +02:00
af714cfd5b
broken Intel compiler (do concurrent)
...
errors occur under unclear conditions, better avoid at the moment:
https://community.intel.com/t5/Intel-Fortran-Compiler/do-concurrent-broken-with-openmp/m-p/1301528#M156942
https://community.intel.com/t5/Intel-Fortran-Compiler/Bug-with-do-concurrent-and-openmp/m-p/1173473m
2021-07-27 16:44:13 +02:00
c7ed0e7934
Merge remote-tracking branch 'origin/development' into do-concurrent
2021-07-26 20:20:52 +02:00
012f09caa7
Merge branch 'plastic-name-behavior-fix' into 'development'
...
adjusted names and behavior of dislo(tungsten + twin) + kinehardening
See merge request damask/DAMASK!419
2021-07-26 14:51:20 +00:00
ac6d31b1f9
Merge branch 'polishing' into 'development'
...
Polishing
See merge request damask/DAMASK!418
2021-07-26 13:09:49 +00:00
f1f658bbd2
Merge remote-tracking branch 'origin/development' into plastic-name-behavior-fix
2021-07-26 15:07:53 +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
e56f2e09a4
trivial and never used
...
even the more commoly used fucntions for 3x3 matrices are not all in use
2021-07-26 10:22:53 +02:00
d19ab4c4f6
co concurrent possible here
...
note: do concurrent cannot be used for the double loops for 66 to 3333!
2021-07-25 14:37:50 +02:00
31a4000655
no need for arbitrary dimension
...
not sure if correct, not used at all (even identity4th for 3 dim is not
used, but now at least tested)
2021-07-25 13:32:11 +02:00
3bb5ae3d9e
concurrent/parallel execution is possible here
2021-07-25 13:20:39 +02: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
ae49920256
support single and double quotes in key value pairs also
...
escape characters not supported in double quotes
2021-07-24 17:40:27 +02:00
59d09d708e
string array support for attributes
2021-07-24 17:18:31 +02:00
eef7b8f0a9
nothing to select anymore
2021-07-24 15:16:30 +02:00
d87b10bfe7
symbolic names
2021-07-24 15:03:26 +02:00
db07ee2113
supported by recent compilers
2021-07-24 14:35:17 +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
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
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
a5c4e7232c
probably not needed
...
We remove blank spaces while converting to flow YAML.
2021-07-23 18:37:45 +02:00
c347688410
Merge remote-tracking branch 'origin/development' into YAML-improvements
2021-07-23 17:55:03 +02:00
ca8775e0d4
allow " " in YAML, follow yamllint.
2021-07-23 17:45:10 +02: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
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
Sharan Roongta