af714cfd5b
broken Intel compiler (do concurrent)
...
errors occur under unclear conditions, better avoid at the moment:
https://community.intel.com/t5/Intel-Fortran-Compiler/do-concurrent-broken-with-openmp/m-p/1301528#M156942
https://community.intel.com/t5/Intel-Fortran-Compiler/Bug-with-do-concurrent-and-openmp/m-p/1173473m
2021-07-27 16:44:13 +02:00
cc18abb42d
write marc displacements of nodes and IPs in HDF5 file
2021-02-02 09:03:41 +01:00
41fbc58c1b
standard conforming name
2020-09-22 13:09:12 +02:00
63f9078f04
don' hardcode output unit
...
replaced remaining write(6,..), flush(6) with write(OUTPUT_UNIT,...),
flush(OUTPUT_UNIT)
2020-09-22 12:15:36 +02:00
e848590c5c
Merge remote-tracking branch 'origin/development' into Fortran-simplifications
2020-09-17 19:39:31 +02:00
b497ec4371
use print instead of write
...
https://www.scivision.dev/print-vs-write-fortran/
2020-09-13 13:01:38 +02:00
e932b386b9
Merge branch 'development' into MiscImprovements
2020-02-07 17:11:01 +01:00
9c138c87f0
not needed
2020-01-29 14:57:12 +01:00
0eba4e39cc
trying to make the whole procedure understandable
2020-01-26 14:18:16 +01:00
ffea69955e
polishing and testing
...
element 11/12 (7/57 for MSC.Marc) have the same geometry type, i.e. both
are a hexahedral with 8 integration points/cells
Type 11 is linear (8 nodes), type 12 quadradic with reduced integration (20 nodes).
The modified definition ensures that the cell nodes 9-20 of element 11
are in the same order as the real nodes 9-20 of element 12. Real nodes
1-8 (corners) and 21-27 needed no modification.
Notes:
* Documentation on https://damask.mpie.de/Documentation/ElementType is now outdated.
* Element defition in MSC.Marc manual volume B (2001 version) is
confusing because element numbering is sometimes clowise and
sometimes counterclockwise. The latter one seems to be correct
2020-01-26 09:24:32 +01:00
b16f4155d4
cell definition follows correct order for 11/12 (7/57 in MSC.Marc)
2020-01-26 09:06:45 +01:00
7671e257bd
reorder elem 11 (Marc 7) to match 12 (Marc 57)
2020-01-26 08:17:59 +01:00
544ff9b6ee
gfortran rejects (Intel seems fine)
...
assume a bug, see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93251
2020-01-13 16:11:36 +01:00
0cf27a8229
indicate parameters and report vtk type
2020-01-13 10:02:23 +01:00
115a2552f8
4 newer versions are out
2020-01-10 03:19:39 +01:00
b386dc73b2
enable to non-transposed tensor data
...
usually, we store per data per cell, i.e. len(shape(x)) == 3 means x is
a tensor.
Due to the use of transposed tensors (due to column-major storage order
in Fortran), we usually want to store the transpose of (3x3) tensors.
Now the default can be changed
2019-10-17 07:46:20 +02:00
9b5545229f
leftover comment ...
2019-10-16 21:13:43 +02:00
3a1c4f95c3
some polishing
2019-10-16 08:40:27 +02:00
02744406e8
was not used
2019-06-16 02:11:09 +02:00
9f35267470
not needed
2019-06-15 15:43:43 +02:00
47e0d83562
taking care of compiler hints
2019-06-13 22:24:51 +02:00
c7513b010b
use definition from element
2019-06-13 09:13:03 +02:00
9379d1884e
further cleaning
2019-06-11 16:16:10 +02:00
402502d6cd
prepare cleaning
2019-06-06 08:16:07 +02:00
3db32102a3
algorithm to split elements into cells
...
- finds all shared nodes
- needs polishing
2019-05-17 13:22:52 +02:00
346c7c4a7f
one implicit none is enough
2019-05-14 23:12:32 +02:00
215598ade9
consistent formatting: always indent by 2 spaces
2019-03-07 20:39:33 +01:00
81b971374b
no need to use pInt
2019-03-07 19:34:27 +01:00
8e0556fe3e
[skip ci] nicer reporting
2019-02-01 12:43:14 +01:00
cda85b0d2d
might be needed somewhere
2019-01-24 15:51:03 +01:00
7e039dff67
verbose initialization
2019-01-24 15:18:53 +01:00
badf9e9cca
object oriented element definitions
2019-01-24 10:24:10 +01:00
Martin Diehl