20fdcb91d9
use central functionality
2023-12-30 15:48:04 +01:00
169bc977d7
was a 'write-only' variable
2023-12-23 22:39:23 +01:00
e4ad5a94a5
better names
2023-12-16 18:28:17 +01:00
9a1cf1a04e
first changes for YAML mesh load case, and simplification of code
2023-12-15 16:03:39 +01:00
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
57e02bb991
PETSc 3.20
2023-10-09 20:10:05 +02:00
af955df891
added phi_min back to example; more consistency in code syntax
2023-09-06 15:11:48 -04:00
925da8aad4
Merge remote-tracking branch 'origin/numerics-comment-format' into restructure-numerics
2023-09-06 20:14:58 +02:00
09f3b2063d
Merge remote-tracking branch 'origin/development' into restructure-numerics
2023-08-17 12:09:10 +02:00
cc77d5c69b
interfaces are not included in petsc version<=3.16.x yet
2023-08-04 19:16:47 +02:00
482ba98b18
mesh numerics changes
2023-08-02 13:28:50 +02:00
d2c374624e
Additional language polish
2023-06-28 10:23:00 +00: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
d0b832e6f1
consistent with naming in HDF5_utilities
2023-06-03 17:06:32 +02:00
e6c2e73e03
Merge remote-tracking branch 'origin/development' into 231-no-petscscalar-and-_range
2022-12-10 14:54:02 +01:00
411c86b5ef
following style guide
2022-12-01 19:52:53 +01: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
64fad03b97
explicit casting
2022-06-27 23:39: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
dece12a1a6
remove unused CLI module inclusion
2022-04-26 12:19:13 -04:00
91b71fdff8
systematic naming scheme
2022-04-24 04:45:41 +02:00
82dabe29c1
mesh: separate kind for DAMASK and PETSc integers
2022-01-13 16:30:42 +01:00
a7417a7ad7
default integer, PETSc integer, and MPI integer might be different
2022-01-13 12:02:33 +01:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
b4ff89f304
improved test
2021-10-27 22:54:26 +02: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
5ac592eb9e
initialize L_(i/p), L_(i,p)0
2021-07-22 12:31:10 +02:00
69cc0b528b
do calculation for initialization
2021-07-22 11:38:03 +02:00
4a2e62fdb2
Merge branch 'development' into 'write_ipdisplacements'
...
# Conflicts:
# src/mesh/mesh_mech_FEM.f90
2021-07-19 17:19:40 +00:00
a654cd4fb1
To avoid fortran double variable truncation for quadrature points
2021-07-19 17:07:43 +02:00
2f1fa8292b
unify style to majority of occurences
2021-07-16 10:30:45 +02:00
3830492791
Merge remote-tracking branch 'origin/development' into write_ipdisplacements
2021-07-15 17:34:44 +02:00
4d6a9a51ed
correct logic
2021-07-15 17:32:41 +02:00
94843becda
writing ip displacements (algorithm contain bugs)
2021-07-14 19:33:54 +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
a0ffbc5f17
little polishing
...
- same names as for grid
- 'local' naming misleading here (probably for x_local etc also not a
good choice)
- following names in PETSc notation (https://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/DMPLEX/DMPlexGetPointLocal.html )
- using allocation with bounds to simplify access
- NOTE: The nodal coordinates are not what damask.Result expects except
for simple, 1 IP elements!
2021-07-02 23:49:06 +02:00
b322ed3e03
feauture to write nodal displacements to hdf5 file added
2021-06-25 20:46:21 +02:00
e855083964
systematic names
2021-02-11 14:19:04 +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
Martin Diehl