d0b832e6f1
consistent with naming in HDF5_utilities
2023-06-03 17:06:32 +02:00
dde60ec53f
Consistent use of () in subroutine calling
2023-02-21 15:18:17 +00:00
5c221e16e1
solver should not solve for field if homogenization description is absent
2022-12-29 19:08:05 +00:00
e6c2e73e03
Merge remote-tracking branch 'origin/development' into 231-no-petscscalar-and-_range
2022-12-10 14:54:02 +01:00
b9ee401ff5
add damage restart functionality and associated tests
2022-12-05 10:52:59 +00:00
c2e78158c8
petsc macros can be omitted with use of preal
2022-12-05 10:38:36 +01:00
b96576ce93
standardizing double definition across modules
2022-12-01 17:27:30 +01:00
0508fa9ec2
flatten solver data layout
...
avoid problem with chunking/compression (only relevant for large
simulations when this feature is used).
In addition, use a unified variable naming: no "_current" for
thermal and damage to follow example of mech.
2022-11-27 17:07:25 +01:00
9d71ffa3ee
better naming
2022-11-24 11:23:10 +01:00
6db3b72c89
avoid global variables
...
extra memory (one vector field) required
2022-11-19 13:05:12 +01:00
ad3c18b29b
avoid use of global variables
2022-11-19 12:24:16 +01:00
18b8923929
centralize FFTs
2022-11-19 09:37:26 +01:00
20da5663c0
simplified, avoid intermediate writes
2022-11-19 08:14:38 +01:00
ce98cfdd5e
padding is handled centrally in the FFT forward routines
2022-11-19 07:58:45 +01:00
df5487e1a9
Re-written YAML types
...
Strict typing for YAML
New access pattern requires to specify the expected type, i.e. 'scalar', 'list', or 'dict'. This ensures that the node offers the expected functionality instead of polluting 'tNode' with dummy functions which throw error messages if not overwritten.
The restructuring of the code allows to hierarchically construct methods without much code duplication.
Some aspects of the error messaging system have been improved.
2022-10-25 16:09:36 +00:00
bb65d58214
add read-in init phi, correct write-out damage result
2022-09-21 08:50:00 +02:00
2f1904efec
only MPI_f08 is standard conforming
2022-06-21 23:11:22 +02:00
b8c3d75700
[skip sc] enforce interfaces (quick fix: declare as external)
2022-06-21 22:59:01 +02:00
487912cfb0
following Python notation
2022-01-29 15:14:40 +01:00
a86dc322fb
consistently put the check on the next line
2022-01-26 12:18:26 +01:00
96fed368ad
name adjustments
2022-01-21 14:51:46 +01:00
7bd8452bf8
set return value
2022-01-20 07:56:45 +01:00
7b1080fdb7
better and consistent variable name
2022-01-20 07:42:16 +01:00
1f86111f57
call SNESSetDM after DMDASNESSetFunctionLocal
...
following example ex5f.F90, seems to resolve segmentation fault
2022-01-19 22:57:22 +01:00
fe094939e6
better to understand
2022-01-19 19:43:54 +01:00
89cb018189
polishing
2022-01-19 18:58:46 +01:00
25ddec76e7
avoid (x/y/z)end and (x/y/z)start, same information is in grid
2022-01-19 17:41:16 +01:00
29530da579
use correct kind of constants for calls to MPI/PETSc
2022-01-13 13:50:30 +01:00
91a3ea96ec
final MPI-DAMASK integer kind decoupling
...
bugfix: set error for openMP-calucations
2022-01-13 13:21:44 +01:00
1ddf1e5694
support for PETSc with 64bit integers
...
compiles, but untested
2021-12-21 23:53:46 +01:00
6ba2a08e5a
easier to read
2021-12-11 11:50:40 +01:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05: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
8e75e87ad9
Merge branch 'MPI_F08' into polishing-for-beta
2021-07-09 11:32:32 +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
a13e02da44
easier to follow
2021-07-06 22:33:12 +02:00
06e76c1a81
consistent default absolute tolerances
...
better use conservative values, users can easily relax if needed
2021-06-25 10:13:03 +02:00
887524bcc1
polishing
2021-04-11 16:09:29 +02:00
547f2ffa69
cleaning
2021-04-11 09:46:11 +02:00
c4765d3742
following paper
2021-04-08 13:31:21 +02:00
0fc7f66ef8
consistent names
2021-04-07 21:25:11 +02:00
c53927ad6f
not needed
2021-04-07 08:47:46 +02:00
fc172921fb
unified citation style continued
2021-03-19 10:41:47 +01:00
9679c5403e
continue with cell based map (solver + homog)
2021-02-23 15:44:58 +01:00
4eb2a981ca
keeping variables local
2021-02-12 15:31:43 +01:00
b58465415b
store damage parameter like temperature
2021-01-24 18:20:47 +01:00
32bb0d8c6e
new variables for damage
2021-01-20 21:37:43 +01:00
35f9861818
Fortran standard is 2018
...
will not work for older compilers
2020-12-18 15:19:04 +01:00
Martin Diehl