f75235f6a9
Merge branch 'more-flexible-L' into 'development'
...
more flexibility for the L in the load case
See merge request damask/DAMASK!420
2021-08-09 21:27:13 +00:00
2635bb012c
Merge remote-tracking branch 'origin/development' into YAML-improvements
2021-08-05 14:49:33 +02:00
c5a80bc75d
more readable
2021-08-02 16:50:21 +02:00
044a048944
taking care of corner cases (e.g. restart)
...
adjusting tests to take care of new 'setup' group
2021-08-01 22:46:11 +02:00
e89a03d456
Suggestion by @Franz
2021-07-28 18:04:52 +02:00
3d7f15c940
meaningful error message incase of mismatch in quotes
2021-07-28 12:14:00 +02:00
ddb0429a1d
store load case (full reproducibility for grid solver)
2021-07-27 07:57:04 +02:00
d9aa638ad7
shorter
2021-07-22 15:11:38 +02:00
85735605f8
more flexibility for the L in the load case
...
Note that mixed boundary conditions for L introduce an ambiguity.
Consider:
L = [[1.0, x, x],
[ 0, 0, 0],
[ 0, 0, 0]]
P = [[x, 0, 0],
[x, x, x],
[x, x, x]]
What we need is F^(n+1)=F_dot^(n+1) x Delta_t, where F_dot^(n+1) is
F_dot^(n+1)_ij = L_ik F^n_kj.
So component F_11 has contributions from L_12 and L_13. We first assume
L_12=L_13=0 and then choose F^(n+1)_12 and F^(n+1)_13 to get
P_12=P_13=0. This implicitly gives a solution for L_12 and L_13, which
is however only one out of infinitely many.
2021-07-20 07:10:28 +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
77d1ed465e
divide and test
2021-05-22 11:09:50 +02:00
9a37b6ddbe
support windows line endings
...
if first line ends with CRLF, convert all CR to ' ' (trailing spaces
will cause no harm)
2021-05-19 09:08:41 +02:00
bbb292d093
polishing
2021-04-07 20:39:29 +02:00
2e96fcf768
Merge branch 'development' into spring-cleaning
2021-03-29 07:26:17 +02:00
7072ab0984
non-converging simulation is an error
2021-03-27 17:07:36 +01:00
b1cca4f5bd
polishing
2021-03-24 15:50:39 +01:00
ef45e856a1
don't scan the whole file in case of proper line endings
...
might lead to strange behavior if people randomly distribute CRs in
their file. But that actually deserves to get strange behavior
+ Test
2021-02-10 09:08:57 +01:00
5b8e199627
avoid errors related to CRLF (windows) file endings
2021-02-10 00:02:38 +01:00
5bed0787ed
replace log scaling with geometric regression scaling
...
more flexibility in time discretization via parameter 'r'.
Also, changed variable names to reflect names in loadcase.yaml
2020-11-25 18:56:03 +01:00
9c75674b20
unused
2020-11-12 07:50:56 +01:00
cd7ada0da9
use Fortran internals for error handling
2020-11-11 20:09:14 +01:00
3dd5eaf1c1
clean exit with stack trace
2020-11-11 14:06:21 +01:00
3dbc07a26b
better error description
2020-10-23 18:43:52 +02:00
9550b0d8a2
mandatory N_constituents
2020-10-07 17:44:54 +02:00
776901cb81
microstructure --> material
2020-10-01 12:43:05 +02:00
a61bf3bb26
file endings, file header can be added, take care of EOF
2020-09-29 19:55:25 +02:00
0de54404ee
skip empty lines; yaml file optional start/stop indicator can be added
2020-09-25 04:07:40 +02: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
1d2e9324f1
do not rely on 6=STDOUT, 0=STDERR
2020-09-19 10:51:07 +02:00
797073b015
print choses output unit automatically, no need to rely on 6
...
also shorter...
2020-09-17 19:28:41 +02:00
5b83c8ad3c
use 'error stop'
...
- does not require IO
- prints stack trace
2020-09-13 12:09:32 +02:00
16f8df3420
standard "docstring"
...
- start with capital
- active form
- end with full stop
2020-09-13 11:32:36 +02:00
3c5b89ac78
not needed anymore
2020-09-13 11:28:48 +02:00
07f23d3d1d
no need for alias
2020-09-13 11:21:43 +02:00
566ab7e7d9
reading in VTR files
...
will replace geom file in the near future
2020-09-12 14:43:04 +02:00
d7932aeacb
Merge branch 'vtr-as-input-prerequisites' into 'development'
...
prerequisites for using VTR as input format for spectral solver
See merge request damask/DAMASK!214
2020-09-09 18:13:09 +02:00
95af422d5f
complain about invalid microstructure
...
many error messages are not needed any more
2020-09-08 23:49:44 +02:00
fb68d430ec
decode only relevant part of the base64 string
2020-09-08 23:15:43 +02:00
3fdcebc0a0
following python recommendation
...
functions have "active" docstring
2020-09-06 17:50:32 +02:00
7754a1ea56
Restructuring for material.yaml
2020-08-15 16:08:46 +02:00
68bf21c900
can use string of dynamic length
2020-08-09 06:40:43 +02:00
8de3b67c26
no silent crash
2020-07-13 21:13:53 +02:00
78bf8b0ab7
bugfix: close file before returning
2020-06-25 11:25:39 +02:00
78b6b3ecdb
Merge branch 'development' into YAML-compatible-numerics
2020-06-25 11:02:54 +02:00
cdb4a11a2e
proper error message; Comments starting point is standardized
2020-06-18 00:17:43 +02:00
5c544a6e4e
bugfix
...
- IO_read sanities files such that they end with EOL (unless 0 byte)
- IO_readline simply counts EOL to determine number of lines
2020-06-05 20:58:36 +02:00
9cd9ee71c5
off-by-one issue fixed
2020-06-05 14:44:31 +02:00
a9e0e93213
need to handle case of zero length file when splitting
2020-06-05 13:38:40 +02:00
512e54a7ee
before we forget ...
2020-06-02 17:34:58 +02:00
Philip Eisenlohr