5a5f1cfc5b
mesh works again for PETSc >= 3.19
...
needs also bugfix in PETSc: https://gitlab.com/petsc/petsc/-/merge_requests/6986
2023-11-02 15:41:20 +01:00
9c4fa16c7d
new mech dict
2023-09-06 19:57:40 +02:00
09f3b2063d
Merge remote-tracking branch 'origin/development' into restructure-numerics
2023-08-17 12:09:10 +02:00
99292c5081
prefix not required
2023-08-02 16:02:51 +02:00
c960f8ed58
space needed to add new option + marc changes
2023-08-02 14:21:47 +02:00
ac63ee3600
marc and other minor changes
2023-08-02 14:18:54 +02:00
482ba98b18
mesh numerics changes
2023-08-02 13:28:50 +02:00
0324e7ece1
parameters should be spelled in capitals
2023-06-04 13:52:31 +02:00
ca1c22874b
consistent and short
2023-06-04 13:51:05 +02:00
e5b7ad335f
debug.yaml causes more work than it saves
2023-02-13 22:26:58 +01:00
e6c2e73e03
Merge remote-tracking branch 'origin/development' into 231-no-petscscalar-and-_range
2022-12-10 14:54:02 +01:00
aaae8a701b
Fortran style adjustments
2022-12-07 17:29:03 +00:00
b96576ce93
standardizing double definition across modules
2022-12-01 17:27:30 +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
0ca4d42678
PETSc 3.18.0 compatibility
...
CHKERR macros are now longer, should be replaced with PetscCall in the
future
2022-10-02 12:48:54 +02:00
60e097a04e
something is wrong with interfaces for 64 bit
2022-06-27 22:35:29 +02:00
61dc14e0b9
Merge remote-tracking branch 'origin/development' into implicit-none-external
2022-06-27 15:13:20 +02:00
3b57934d6e
Marc precision handling
2022-06-27 08:37:41 +00: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
6d78400f87
the concept of IP/element_ID should not be used at the DAMASK core
2022-02-05 07:29:00 +01:00
82dabe29c1
mesh: separate kind for DAMASK and PETSc integers
2022-01-13 16:30:42 +01:00
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
3fb5bd459c
pInt leftovers
2022-01-13 07:44:15 +01:00
69843d0833
Merge branch 'development' into pretty-print-init
2021-11-15 12:39:14 -05:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
8138d3a180
style adjustments
2021-11-11 23:59:48 +01:00
ba31ff7263
do not rely on ML per default
2021-11-11 23:23:14 +01:00
a00c6743c3
symbolic notation in numerics.yaml
...
- p_i: integration order
- p_s: shape function order
ensure working combination (p_s = p_i: full integration, p_s = p_i+1:
reduced integration)
2021-10-26 11:51:08 +02:00
5b66db8a39
only mechanics at the moment
...
will be extended, but most likely differently
2021-07-22 10:12:43 +02:00
eb834b635d
unify notation with grid
...
consistent style: Symbols, not descriptions.
also removed untested/unused loginc functionality. Once load cases are
written in YAML, we can introduce the scaling as in DAMASK_grid
2021-07-22 08:48:44 +02:00
173a5f8e55
less public/unneeded variables
2021-07-22 07:48:01 +02:00
f9edeb40a5
descriptive names
2021-07-17 11:50:21 +02:00
ed6b1be352
solver handles terminally ill
2021-07-16 20:43:08 +02:00
3f0eafd640
first step towards separating of mechanics, thermal, and damage
2021-07-16 17:53:11 +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
6a2c107723
consistent names for debugging
2021-03-26 12:34:16 +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
80c8c9e51e
fixing use for new Intel Fortran
...
visibility of use associated entities can now be limited
2020-11-28 07:23:55 +01:00
9119254210
materialpoint => homogenization
...
especially as prefix for global data (clear name spaces)
2020-10-24 17:26:42 +02:00
7f8613f6ad
always update dPdF (was the default anyways)
2020-09-30 10:24:24 +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
cc92b0ad84
print is more appropriate than write
2020-09-19 08:29:50 +02:00
e5c2382f73
missing renames ...
2020-09-13 11:17:49 +02:00
Martin Diehl