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
8fbadef524
print instead of write
2020-12-14 22:37:14 +01:00
189597dbff
drop support for old PETSc versions
2020-12-13 08:55:07 +01:00
9119254210
materialpoint => homogenization
...
especially as prefix for global data (clear name spaces)
2020-10-24 17:26:42 +02:00
1681889e0b
PETSc 3.14 is out
2020-10-06 07:12:04 +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
7754a1ea56
Restructuring for material.yaml
2020-08-15 16:08:46 +02:00
48b42debe0
redundant
2020-07-03 20:55:05 +02:00
640bc7b190
[skip ci] polishing
2020-06-29 15:09:13 +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
ac2539b305
further cleaning of numerics.f90
2020-06-17 20:46:03 +02:00
d4d29ff376
cleaning: comments added
2020-06-17 17:19:21 +02:00
5cd2be0569
less global variables
2020-06-16 19:15:01 +02:00
431284aa95
not needed
2020-06-01 18:23:01 +02:00
44fc65b812
Merge branch 'development' into FEM-PETSC_3.11+
2020-06-01 15:19:37 +02:00
1885a701fa
nothing to debug here
2020-06-01 15:19:30 +02:00
530623a2b3
function was only renamed in PETSc 3.12
2020-05-13 13:15:37 +02:00
f2d1343cdf
need to select the whole mesh
2020-05-13 12:58:39 +02:00
72c835a554
not used
2020-05-11 16:00:53 +02:00
48c9d31720
matching names
2020-03-20 15:08:07 +01:00
03bec0221a
systematic names
2020-03-20 15:00:18 +01:00
Martin Diehl