ccd6e44b6b
Merge remote-tracking branch 'origin/development' into 134-output_none
2021-11-27 19:17:27 +01:00
43ae4983ed
fixed misaligned/too short "writing..." statements
2021-11-15 12:58:59 -05:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
64d70d9be3
user option to have no output
...
f_out = none
2021-11-15 14:39:29 +01:00
f75235f6a9
Merge branch 'more-flexible-L' into 'development'
...
more flexibility for the L in the load case
See merge request damask/DAMASK!420
2021-08-09 21:27:13 +00:00
044a048944
taking care of corner cases (e.g. restart)
...
adjusting tests to take care of new 'setup' group
2021-08-01 22:46:11 +02:00
b9d4eb23cc
only rank 0 reads file for MPI
2021-07-27 08:54:17 +02:00
812b0f07f5
read file only once (per process)
2021-07-27 08:35:52 +02:00
ddb0429a1d
store load case (full reproducibility for grid solver)
2021-07-27 07:57:04 +02:00
574cfd7034
Merge remote-tracking branch 'origin/development' into more-flexible-L
2021-07-22 00:20:33 +02:00
9d349f8a7c
symbolic notation
2021-07-21 06:50:28 +02:00
6f19113072
L, P, F, etc. are second order tensors
2021-07-21 06:19:04 +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
03b7532cc5
numpy.MaskedArray behavior
2021-07-19 23:27:10 +02:00
1c1dc9383e
symbolic names
2021-07-19 22:30:20 +02:00
136a4b1377
PETSc defines are rather complicated
...
now mpi_f08 can be used on newer PETSc installations if old MPI modules
are not exposed
2021-07-09 18:48:25 +02:00
637f78bd52
old name (for PETSc < 3.15)
2021-07-09 14:50:29 +02:00
139f2c177a
use MPI_f08 if possible
...
most PETSc installations provide outdated MPI (f90 version)
MPI_COMM_WORLD is now of derived type (Fortran 08 style)
PETSC_COMM_WORLD is the plain integer (f90 style) alias.
Note that HDF5 is assumed to have f90 interfaces
2021-07-08 16:27:37 +02:00
3705f1d3a2
F,P, ... in loadcase are 2nd order tensors
2021-06-03 08:21:16 +02:00
d1a6607782
Merge branch 'load2Dtensor' into 'development'
...
support for 2D tensor in load case
See merge request damask/DAMASK!391
2021-05-29 13:21:47 +00:00
adb1e51e24
support for 2D tensor in load case
...
currently optional, but should become mandatory after a transition
period
2021-05-26 08:04:14 +02:00
d2855913b5
new mappings
2021-05-22 11:48:42 +02:00
2e96fcf768
Merge branch 'development' into spring-cleaning
2021-03-29 07:26:17 +02:00
710f5b74b2
Merge remote-tracking branch 'origin/development' into 2d-table-yaml
2021-03-29 00:00:39 +02:00
7072ab0984
non-converging simulation is an error
2021-03-27 17:07:36 +01:00
a72e2db678
Merge branch 'development' into output-rename
2021-03-25 21:03:20 +01:00
3b392281e4
consistent naming in HDF5 output
2021-03-25 19:22:59 +01:00
fc172921fb
unified citation style continued
2021-03-19 10:41:47 +01:00
ce91537b0f
get_asXXs --> get_as1dXX
2021-03-11 18:40:16 +01:00
e4271537c5
syntax polishing; use of YAML defaults to avoid if%contains
2021-03-04 15:14:16 -05:00
2f68c43755
new style configuration for damage
2021-03-01 06:16:16 +01:00
8af0c8dbc3
using initial temperature from load case file
2021-02-28 21:51:07 +01:00
0cde43198f
modernizing:
...
- 'pass' for dummy thermal homogenization
- setting temperature in load case
2021-02-28 20:49:51 +01:00
ef543a5b49
thermal solver is defined in load case
...
not in numerics.yaml
2021-02-28 20:09:08 +01:00
b2fea6b149
solver not specific to load case number
2021-02-28 19:24:44 +01:00
4dd99d4c39
solver is selected in load case, not numerics.yaml
2021-02-28 19:13:20 +01:00
5348305ac8
restart key part of loadstep and not time discretization
2021-02-22 14:42:54 +01:00
e855083964
systematic names
2021-02-11 14:19:04 +01:00
8048d69a97
[skip ci] logic inverted
2021-02-05 16:59:28 +01:00
ba2e8b3c63
variable name follows label
2021-02-05 11:57:18 +01:00
a1a7a339d4
specify solver,initial and boundary conditions in load file
2021-02-05 11:20:28 +01:00
2e173b4b7b
'estimate_rate' better describes what we want to do than 'drop_guessing'
...
true by default
2021-02-04 19:17:32 +01:00
4f059910ab
fix broken statistics reporting in case of multi-physics
2021-01-24 10:39:32 +01:00
a2b5178b45
polishing
2021-01-17 21:56:19 +01:00
8af53472ee
Merge remote-tracking branch 'origin/development' into signal_input_handling_1
2021-01-17 16:52:48 +01:00
0a3d43e0fc
only one process gets the signal: use OR, not AND
2020-12-17 15:17:20 +01:00
d83e8dac59
need to share variable before if
2020-12-17 13:20:18 +01:00
da1b006315
MPI communication for SIGUSRXXX
2020-12-17 12:47:33 +01:00
2dd520b4a2
P_aim should be independent from P_av
...
P_av is not defined after restart or cutback. Restart with change of
load case is probably still an issue
2020-12-15 08:06:50 +01:00
768d139768
reset the signal terms to false after task is done
2020-12-14 09:34:35 +01:00
40bd5db361
signals enabling writing results,restart and termination
2020-12-14 09:17:15 +01:00
5bed0787ed
replace log scaling with geometric regression scaling
...
more flexibility in time discretization via parameter 'r'.
Also, changed variable names to reflect names in loadcase.yaml
2020-11-25 18:56:03 +01:00
2157bf50cd
mech --> mechanics
2020-11-17 22:21:35 +01:00
a1ab526456
avoid global variables
2020-10-24 16:01:56 +02:00
1c13737935
better readable
2020-10-21 21:12:55 +02:00
96243a4ac8
simplifying
2020-10-21 17:46:29 +02:00
f25f7ad01e
[skip sc] consistent naming convention
2020-10-16 16:17:06 +02:00
3f3a88fdda
capitalization
2020-10-15 23:32:38 +02:00
6c79093a75
[skip sc] Fdot --> dotF
2020-10-15 23:22:37 +02:00
6455627af9
accessed by correct dict now; tests improved
2020-10-15 18:09:45 +02:00
1c911f6213
simplified
2020-10-14 17:55:57 +02:00
35fe935088
not used
2020-10-14 13:53:31 +02:00
f291166a03
initialisation not needed
2020-10-14 10:53:37 +02:00
1426a35602
loadcase in yaml
2020-10-14 10:31:34 +02:00
32b81770d9
shorter
2020-09-25 21:35:47 +02:00
8396af5aec
not needed
2020-09-25 15:19:31 +02:00
421d4b8f37
forgotten renames
2020-09-25 15:12:56 +02:00
79d672f4a7
cleaning
2020-09-24 17:04:06 +02:00
f8816a6e0c
Merge remote-tracking branch 'origin/development' into stress-ramp-loadcase
2020-09-24 16:57:07 +02:00
41fbc58c1b
standard conforming name
2020-09-22 13:09:12 +02:00
53ce4e07d2
forgotten renames in subfolders
2020-09-22 13:02:33 +02:00
0a7d4f61ac
Need only logical mask
...
'merge' substitutes multiplication with float mask
2020-09-20 16:54:58 +02:00
6367cb8fcb
consistent handling of boundary conditions
...
A stress boundary condition 'P' indicates the stress at the end of the
load case (same as for 'F') 'Pdot' for given increase of (technical)
strain is not implemented.
Does not change anything for the most common case of zero-stress
boundary conditions, but simplifies the specification of stress ramps
2020-09-20 15:48:41 +02:00
593a40b392
Merge branch 'Fortran-simplifications' into stress-ramp-loadcase
2020-09-20 11:42:04 +02:00
053c3f39ea
solution completely relies on state defined by 'forward'
2020-09-19 23:40:17 +02:00
d0b5905544
remaining write(6,...) without advance='no'
2020-09-19 11:02:40 +02:00
c6c34ccf7e
Merge remote-tracking branch 'origin/development' into stress-ramp-loadcase
2020-09-19 08:46:38 +02:00
cc92b0ad84
print is more appropriate than write
2020-09-19 08:29:50 +02:00
a2e9420336
boundary conditions to not change during iteration
2020-09-14 14:58:44 +02:00
38a4118dc5
prefix to global variables increases readability
2020-09-13 11:05:42 +02:00
b499578a95
prefix should be name of the module
...
poor substitute for namespace
2020-09-13 10:39:17 +02:00
da0e16520c
handling of MPI in 'parallelization'
2020-09-13 10:26:33 +02:00
7754a1ea56
Restructuring for material.yaml
2020-08-15 16:08:46 +02:00
68bf21c900
can use string of dynamic length
2020-08-09 06:40:43 +02:00
48b42debe0
redundant
2020-07-03 20:55:05 +02:00
57e4d01a6b
Merge branch 'development' into YAML-compatible-debug
2020-07-01 13:40:56 +02:00
0b2d62e98d
polishing
2020-06-29 17:05:11 +02:00
14a4dc5184
Merge branch 'YAML-compatible-numerics' into YAML-compatible-debug
2020-06-27 21:48:59 +02:00
77e7e3d3c4
polishing
2020-06-26 20:12:05 +02:00
78b6b3ecdb
Merge branch 'development' into YAML-compatible-numerics
2020-06-25 11:02:54 +02:00
692fc98fd5
'num' structure for data to avoid multiple reading of parameters
2020-06-24 16:35:47 +02:00
7c4afe06c9
less generic variables
2020-06-19 03:56:16 +02:00
4942304ee8
extended for grid
2020-06-18 17:43:25 +02:00
cdb4a11a2e
proper error message; Comments starting point is standardized
2020-06-18 00:17:43 +02:00
0fc482585b
used for both grid & mesh; polishing
2020-06-17 23:00:03 +02:00
d3f9e9f115
polishing
2020-06-17 18:02:22 +02:00
f6355d199a
better as local variables
2020-06-17 16:47:13 +02:00
19c44d5e97
Read numerics.yaml once
2020-06-16 18:47:19 +02:00
a9e0e93213
need to handle case of zero length file when splitting
2020-06-05 13:38:40 +02:00
7ec1ae977e
new names
...
spectral => grid
FEM => mesh
because there are FEM solvers for both discretizations. old names will
be available for a certain time
2020-04-25 09:56:51 +02:00
Martin Diehl