7d7d0c2659
only local variable are good variables
2021-12-11 08:49:30 +01:00
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
Martin Diehl