32b5e4dece
update time estimate for long running processes
2021-06-18 18:14:52 +02:00
0805445ea8
exchanged x/z dimension in XDMF writing
2021-06-18 10:17:39 -04:00
0551c5c169
Private branch updated
2021-06-18 12:21:28 +02:00
70505a6a63
improved build instructions for Docker
2021-06-18 08:59:30 +02:00
257180b558
no direct support for shell scripts anymore
2021-06-18 07:36:03 +02:00
ce8ec6d471
Reference file updated with 2D elements with dummy dimensions
2021-06-17 20:44:07 +02:00
e5fdcdf1a6
Reference results updated for 2D elements with dummy dimensions
2021-06-17 20:28:02 +02:00
36bf68b336
Out of plane coordinates for 2D elements are updated with dummy values
2021-06-17 20:26:37 +02:00
db1882e4de
polishing
2021-06-17 18:26:37 +02:00
d6995d780b
[skip ci] updated version information after successful test of v3.0.0-alpha3-235-gdee255ae7
2021-06-16 22:45:01 +02:00
dee255ae71
Merge branch 'vtr-to-vti' into 'development'
...
VTK image data is the appropriate type, not VTK rectilinear grid
See merge request damask/DAMASK!399
2021-06-16 19:02:20 +00:00
331cb80cf2
Reference result is updated
...
correct ip coordinates for 4th and 5th order integration
2021-06-16 18:16:10 +02:00
b9d4217d86
permutationStar111 for 4th order integration is updataed
2021-06-16 14:58:26 +02:00
f19dc27246
transition compatibility
2021-06-16 14:35:54 +02:00
f080136751
fixed test
2021-06-16 10:43:50 +02:00
9b1f5c7783
testing new functionality for Neper / vti
2021-06-15 23:19:08 +02:00
9f40f9ee44
fixed tests
2021-06-15 22:29:40 +02:00
01a32ea236
import from Neper
2021-06-15 22:29:28 +02:00
1bfbd30ae2
polishing
2021-06-15 19:53:05 +02:00
218e6a79a8
VTK image data is the appropriate type, not VTK rectilinear grid
...
FFTs require constant spacing in all three directions, this is
guaranteed by the vtkImageData but not by vtkRectilinearGrid
2021-06-15 19:02: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
e2ce882d73
Test added
2021-06-10 17:13:42 +02:00
5202da13ea
better not have a "Lattice" object with "lattice" parameter
2021-06-07 21:49:04 +02:00
41e5f0c06c
re-introduced multiple inheritance
2021-06-06 22:25:42 +02:00
33efe03378
[skip ci] updated version information after successful test of v3.0.0-alpha3-226-g2df56a6c4
2021-06-03 12:41:30 +02:00
0722f4f754
disable if not possible
2021-06-03 11:22:28 +02:00
3c8d06b6f1
encapsulating all lattice(-family) related data
2021-06-03 11:18:00 +02:00
2df56a6c43
Merge branch '2Dloadcase' into 'development'
...
F,P, ... in loadcase are 2nd order tensors
See merge request damask/DAMASK!397
2021-06-03 09:00:14 +00:00
4701eea10f
decoupling Orientation and Lattice/LatticeFamily
2021-06-03 10:02:49 +02:00
03d3f362e6
equality checks
...
note: doing this type of comparison means:
- LatticeFamily('cubic') == Lattice('cF')
- Lattice('cF') != LatticeFamily('cubic')
we have the same behavior for comparison between Orientation and
Rotation
2021-06-03 09:38:43 +02:00
3b150ddbea
simplified/separated
2021-06-03 09:22:54 +02:00
87e94b6cf4
sorting
...
most functions require only lattice family, functions that require full
lattice details are at the end
2021-06-03 08:43:56 +02:00
3705f1d3a2
F,P, ... in loadcase are 2nd order tensors
2021-06-03 08:21:16 +02:00
302da1f76a
separating functionality
2021-06-02 17:11:37 +02:00
35b17fd029
[skip ci] updated version information after successful test of v3.0.0-alpha3-223-g6cd0d79c6
2021-06-02 15:51:26 +02:00
6cd0d79c61
old merge not reflected
2021-06-02 14:08:12 +02:00
41bd0af549
Merge branch 'development' of magit1.mpie.de:damask/DAMASK into development
2021-06-02 14:07:00 +02:00
6682818187
Merge branch 'Fortran-cleaning' into 'development'
...
Separating functionality
See merge request damask/DAMASK!396
2021-06-02 14:01:28 +02:00
39c2506b8d
Merge branch 'Fortran-cleaning' into 'development'
...
Separating functionality
See merge request damask/DAMASK!396
2021-06-02 09:24:47 +00:00
b55d51491d
separating functionality
2021-06-02 08:48:45 +02:00
e281d8384f
distinguish 'family' and 'lattice'
...
this requires the user to specify a keyword ('*' notation in __init__).
Since all 'from_xxx' methods anyway require a keyword, it does not
causes much more work (one explicit keyword in case of cube orientation
when using __init__ directly).
2021-06-01 21:51:28 +02:00
684016f3e3
utility function without connection to an object
2021-06-01 21:29:35 +02:00
fada9a7f6c
more meaningful order
2021-06-01 17:05:13 +02:00
5d0fc4fca3
more meaningful order
...
and intent(out) variables for read are at the front
2021-06-01 16:46:24 +02:00
fc75efa4d0
[skip ci] updated version information after successful test of v3.0.0-alpha3-214-g6f9e521cd
2021-06-01 12:58:33 +02:00
569b1fc563
not needed (duplicated code)
2021-06-01 11:09:02 +02:00
6f9e521cdb
Merge branch 'HDFgeometryupdate' into 'development'
...
HDF geometry update
See merge request damask/DAMASK!395
2021-06-01 08:01:53 +00:00
431416b5ba
Separating functionality
...
lattice should become a module with static data and functions
2021-06-01 07:56:55 +02:00
Martin Diehl