5c221e16e1
solver should not solve for field if homogenization description is absent
2022-12-29 19:08:05 +00:00
06f8697bd1
manage tabulated data with linear interpolation in-between points
2022-12-07 21:44:44 +01:00
c507e2d3b6
avoid potenttial out-of-bounds memory access
2022-10-27 15:56:59 -04:00
5c688345ed
more verbose and specific messaging in self-test and errors
2022-10-27 15:39:48 -04:00
b8c3d75700
[skip sc] enforce interfaces (quick fix: declare as external)
2022-06-21 22:59:01 +02:00
78838c2f75
consistent variants including space
2022-06-08 23:27:09 +02:00
b56ded62d9
encapsulate data, prefix only public functions
2022-05-27 18:01:40 +02:00
75bd643258
more precise warning for fftw_plan_mode
2022-05-27 11:58:10 -04:00
d66c777d6e
introduced "IO_panel" to write statements to STDERR
2022-05-27 11:47:14 -04:00
6c6b3e64b3
more flexible reporting
2022-05-27 09:38:47 +02:00
f7d23ad151
internal variable, no prefix needed
2022-05-27 08:40:01 +02:00
f31dd8cbe8
unknown error/warning numbers are internal errors
2022-05-27 08:34:52 +02:00
f90523eb07
more flexible reporting
2022-05-27 08:33:50 +02:00
79fad5ca19
IP was only used for an argument that is NOT the IP ID
2022-05-27 06:41:15 +02:00
724c4fcf5d
not used
...
ip,el,g is anyways not flexible enough. Remove unused arguments before
developing a more flexible approach
2022-05-27 00:23:51 +02:00
556d9d840e
specifying V_e is more natural than F_i
2022-05-19 01:15:17 +02:00
723252ef15
libfyaml backend
...
currently it simply converts the whole file content to flow mode.
The nice thing is: It can convert EVERYTHING to flow mode. libfyaml is
the only library that passes the whole YAML test suite
2022-04-12 23:24:07 +02:00
945b10e3e6
avoid segmentation fault (null is returned if not scalar)
2022-03-20 00:00:52 +01:00
7ee440c1b1
separating functionality for more flexibility
2022-02-28 01:35:39 +01:00
e3a9adc722
not used
2022-02-07 07:20:15 +01:00
da9fdf53d2
consistent indentation and line-spacings in reporting
2021-11-15 12:35:44 -05:00
a00c6743c3
symbolic notation in numerics.yaml
...
- p_i: integration order
- p_s: shape function order
ensure working combination (p_s = p_i: full integration, p_s = p_i+1:
reduced integration)
2021-10-26 11:51:08 +02:00
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
Sharan Roongta