29530da579
use correct kind of constants for calls to MPI/PETSc
2022-01-13 13:50:30 +01:00
a7417a7ad7
default integer, PETSc integer, and MPI integer might be different
2022-01-13 12:02:33 +01:00
1e965c42b7
don't rely on ML
...
avoid dependencies to external packages as much as possible
2021-12-27 17:44:22 +01:00
1ddf1e5694
support for PETSc with 64bit integers
...
compiles, but untested
2021-12-21 23:53:46 +01:00
bfc6b69ee2
integer exponents: faster and shorter
2021-11-25 20:52:22 +01:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
4160c4fdb4
fix for parallel HDF5
...
if filters are applied, writing from one process does not work if the
file is opened for parallel write
2021-08-15 13:26:15 +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
f9edeb40a5
descriptive names
2021-07-17 11:50:21 +02:00
2a84aa7ae4
obvious, no need for comment
2021-07-16 20:32:21 +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
58bc6e2ba6
avoid chained inclusions
2021-07-08 14:27:04 +02:00
5d0fc4fca3
more meaningful order
...
and intent(out) variables for read are at the front
2021-06-01 16:46:24 +02:00
0072ebfa64
polishing
2021-03-27 23:17:04 +01:00
4912342b1b
added missing arguments
2021-03-15 11:46:30 +01:00
a59af55f1a
read data by one process and broadcast it
2021-03-15 10:58:59 +01:00
adcb24d2e1
write data of average quantities non parallel
2021-03-10 16:33:02 +01:00
d54e49e3bc
restore functionality to write non-parallel
...
not needed at the moment, but in general useful. If PETSc = parallel
should always hold, we can simplify much more
2021-02-22 13:37:21 +01:00
e855083964
systematic names
2021-02-11 14:19:04 +01:00
437d91495b
No FEsolving
2021-01-06 14:24:02 +01:00
3884549e19
store field variables as 1D array
...
first step of simplifying layout:
1) Solver translates from ip,el tuple (FEM) or cells(1),cells(2),cells(3) triple to list.
2) DAMASK iterates over all points
3) homogenization knows mapping (point,constituent) -> (instance,member)
2020-12-16 21:56:02 +01:00
afbcb82502
Merge remote-tracking branch 'origin/development' into misc-improvements
2020-12-15 10:32:59 +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
8fbadef524
print instead of write
2020-12-14 22:37:14 +01:00
97ee7e6ee5
not needed anymore
2020-12-07 17:26:50 +01:00
429c226008
IO is not inherited when using ifort 19
...
this is intented, public modules should only bring their own functions
and variables into global scope
2020-11-11 12:19:39 +01:00
b46a25a7d2
C capitalization
2020-11-11 11:47:23 +01:00
9119254210
materialpoint => homogenization
...
especially as prefix for global data (clear name spaces)
2020-10-24 17:26:42 +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
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
329cc1c953
tighter tolerance for stress
2020-09-20 17:36:11 +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
d584207e0a
same layout for easy diff
2020-09-20 13:01:56 +02:00
8dfb972ac1
private is already default (module wide)
2020-09-20 11:49:20 +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
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
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
2056b4223a
better name
2020-07-01 23:01:37 +02:00
dda2f2cf22
defined locally
2020-07-01 22:39:44 +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
640bc7b190
[skip ci] polishing
2020-06-29 15:09:13 +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
be84561e2e
num structure replicated; polishing
2020-06-24 16:48:51 +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
0fc482585b
used for both grid & mesh; polishing
2020-06-17 23:00:03 +02:00
ac2539b305
further cleaning of numerics.f90
2020-06-17 20:46:03 +02:00
7f0c2d3825
further removal of public variables
2020-06-16 20:49:58 +02:00
5a94218d23
fixes error:
...
[0]PETSC ERROR: Object is in wrong state
[0]PETSC ERROR: Cannot set coordinates until after DMDA has been setup
2020-05-11 08:02:34 +02:00
7aa47d8f5a
module name follows filename
2020-03-20 07:18:11 +01:00
839443bc85
better (generic) name where possible
2020-02-26 07:06:25 +01:00
5bc1c98da7
use 0-based indexing for worldrank
2020-01-12 00:49:03 +01:00
bd6f2a6b5c
consistent string length
2020-01-04 19:01:36 +01:00
bd5f963260
polishing
2020-01-04 16:54:07 +01:00
326e3d0824
polishing
2020-01-03 14:02:14 +01:00
2975e46ca1
not needed
2020-01-03 13:52:06 +01:00
a0a99c526b
some remaining IntOut format strings
2019-12-11 19:28:31 +01:00
b0ce324213
Merge remote-tracking branch 'origin/development' into simple-int-formatting
2019-12-08 20:24:05 +01:00
4eacc1d16d
polishing
2019-12-07 15:45:37 +01:00
f5292019e5
use rotation class
2019-12-02 20:23:50 +01:00
8a9d3f8d6d
avoid code duplication
2019-12-02 20:09:27 +01:00
1d2d7d1ea3
remove public variables
...
they make code unreadable and unmaintainable
2019-10-29 23:24:12 +01:00
0c6b7e1112
not nice, but working ...
2019-10-29 23:15:02 +01:00
d1f719d3cf
separation of "age" and "forward" not useful
2019-10-28 13:36:36 +01:00
8de6fcfc24
unifying names
2019-10-28 13:29:32 +01:00
ab4a98fb53
make use of HDF5 and structure data
2019-10-28 13:17:05 +01:00
10f2c53256
clearly distiguish
...
- DAMASK as a materialpoint model (CPFEM, not fitting name)
- solver
2019-10-25 08:30:12 +02:00
07d8379313
further untangling
2019-10-25 07:55:23 +02:00
cf8b16c066
better have one function per task
...
but separating ageing and forward for the solver is not trivial due to
guessing
2019-10-25 07:31:09 +02:00
378729f5c4
clearer structure
2019-10-25 00:42:59 +02:00
9db5cbb667
trying to get rid of a global "restartWrite" variable
2019-10-24 22:50:30 +02:00
0bc4326618
better have one function per task
2019-10-24 13:46:36 +02:00
71def397d5
no need to age before writing restart data
2019-10-24 13:14:40 +02:00
176f6028cd
CPFE2 writes current variables (like grid solvers)
2019-10-24 13:06:42 +02:00
0483fc7b3f
small functions with one task are better
2019-10-24 06:16:42 +02:00
534073358e
arguments are better than public variables
2019-10-23 23:06:47 +02:00
5ba6b6c244
name reflects planned functionality:
...
should update node and cell center coordinates
2019-09-27 15:02:36 -07:00
13c62b890b
module name should reflect file name
2019-09-27 14:34:34 -07:00
25d02c2f19
most of the functionality is only relevant for commercial FEM
2019-06-15 16:21:04 +02:00
cfc1dcf04b
mesh_elem and theMesh are deprecated
2019-06-06 22:49:17 +02:00
5a0e408d59
Merge branch 'development' into SolverRestart-in-HDF5
2019-04-30 17:07:45 +02:00
Martin Diehl