5a04a1d661
let the computer do the counting
2021-07-21 19:41:14 +02:00
c56979e2ad
single source of truth
2021-07-21 18:47:19 +02:00
000007ba59
better test automatically
2021-07-21 18:06:37 +02:00
b1ba64e6af
understanding floating point precision
...
double can use 16 or 17 significant figures
- if the leading number is high (above 5 or so), only 16 figures are
significant.
- a trailing 1 is never significant
2021-07-21 18:04:50 +02:00
f25dee4c3a
quad points updated and rounded based on literature values
2021-07-21 14:34:18 +02:00
a919ac0aea
Merge branch 'write_ipdisplacements' of git.damask.mpie.de:damask/DAMASK into write_ipdisplacements
2021-07-20 15:35:48 +02:00
86d918367f
Round quadrature points
2021-07-20 15:34:13 +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
97203ff551
document and keep definitions together
2021-07-18 23:30:30 +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
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
36bf68b336
Out of plane coordinates for 2D elements are updated with dummy values
2021-06-17 20:26:37 +02:00
b9d4217d86
permutationStar111 for 4th order integration is updataed
2021-06-16 14:58:26 +02:00
e10701b32a
easier to understand
2021-06-14 15:21:10 +02:00
5f01b076d2
This change makes the test work for GNU too
...
Probably something was uninitialized and GNU was accessing unallocated memory
2021-06-14 14:58:14 +02:00
c64f9eb805
hardcoding '3' is an issue for 2d simulations
2021-06-11 20:42:31 +02:00
6cd0d79c61
old merge not reflected
2021-06-02 14:08:12 +02:00
91015fd07c
write out undeformed configuration
2021-05-31 19:41:22 +02:00
650fbd7509
Initial nodal and ip coordinates added to the HDF5 output file
2021-05-31 15:01:42 +02:00
718880f177
Initial nodal and ip coordinates added to the HDF5 output file
2021-05-31 14:09:11 +02:00
2bfed863ba
line was to long
...
macro was changed in PETSc 3.15
2021-04-05 09:04:44 +02:00
84e383964b
polishing/fixing tests
2021-03-27 23:58:49 +01: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
5891786680
Merge remote-tracking branch 'origin/development' into new-gmsh-version
2021-01-13 22:52:50 +01:00
52aaf2fa5e
not needed
2021-01-07 17:04:30 +01:00
793e5d0d2b
Merge branch 'development' into new-gmsh-version
2021-01-07 16:38:16 +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
189597dbff
drop support for old PETSc versions
2020-12-13 08:55:07 +01:00
21faee4eaa
'0' based indexing
2020-12-07 13:03:18 +01:00
f563313ce9
PETSc provides subroutine to read physical tags
2020-12-06 00:10:04 +01:00
665dd3020d
new gmsh version
2020-12-04 03:30:39 +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
c9356fd447
error checking, making readable with damask.Result
2020-11-15 15:39:54 +01:00
9119254210
materialpoint => homogenization
...
especially as prefix for global data (clear name spaces)
2020-10-24 17:26:42 +02:00
Martin Diehl