efc9391ca7
simplified
2023-06-23 00:06:44 +02:00
e197e45566
use existing functionality
2023-06-22 23:25:25 +02:00
cb6b1b30f5
shortened CLI reporting; condensed repeated CLI functions
2023-06-16 12:09:53 -04:00
0324e7ece1
parameters should be spelled in capitals
2023-06-04 13:52:31 +02:00
ca1c22874b
consistent and short
2023-06-04 13:51:05 +02:00
d0b832e6f1
consistent with naming in HDF5_utilities
2023-06-03 17:06:32 +02:00
f3da19a8e2
drop little-used variables
2023-02-28 15:09:23 -05:00
a40524da02
rename to wrapLines; additional formatting options; whitespace trimming
2023-02-28 14:59:30 -05:00
949bc39173
polishing
2023-02-28 07:34:11 +01:00
04db45f5c0
functionality to report references in material.yaml
2023-02-25 12:13:27 +01:00
ca2d184007
Merge remote-tracking branch 'origin/development' into long-YAML-files
2023-02-19 16:04:30 +01:00
15f15c1d78
Merge branch 'LFCR-check' into 'development'
...
one more CRLF check
See merge request damask/DAMASK!725
2023-02-15 23:51:56 +00:00
01719874ea
one more CRLF check
2023-02-15 16:36:20 -05:00
3eb9545573
Merge branch 'development' into long-YAML-files
2023-02-14 17:33:48 +01:00
e5b7ad335f
debug.yaml causes more work than it saves
2023-02-13 22:26:58 +01:00
3e439503fe
enable strings > 2Gb
2023-02-10 22:37:11 +01:00
a2bde4a0f0
correct check for CRLF
...
old attempt tried to look only at forst occurence of LF but reported
CRLF also for LF endings.
2023-02-09 23:32:39 +01:00
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
Martin Diehl