Commit Graph

14151 Commits

Author SHA1 Message Date
Martin Diehl 5126370934 cleavageopening+anisobrittle are strongly coupled 2021-02-13 19:20:52 +01:00
Martin Diehl 9481b16878 missing renames 2021-02-13 19:10:13 +01:00
Martin Diehl 8dc53344ec 'kinematics'=>'eigen', now part of 'mechanics' 2021-02-13 18:52:37 +01:00
Martin Diehl 22a0aff488 separting thermal and damage sources 2021-02-13 18:41:30 +01:00
Sharan Roongta 099cd90890 Merge remote-tracking branch 'origin/development' into python-improvements 2021-02-13 16:51:29 +01:00
Martin Diehl 72c099dbbe store data separetly 2021-02-13 15:06:27 +01:00
Martin Diehl 595ee7a35a copy and paste error 2021-02-13 14:38:53 +01:00
Martin Diehl b3231bf0a8 avoid undefined return 2021-02-13 14:15:41 +01:00
Martin Diehl 9ba185973f more systematic directory structure 2021-02-13 13:33:58 +01:00
Martin Diehl ab202b8e73 less verbose reporting 2021-02-13 13:07:35 +01:00
Martin Diehl 570086c814 hard code at max 1 damage mechanism 2021-02-13 13:07:12 +01:00
Martin Diehl d9699b0f2e simplified access pattern 2021-02-13 11:01:08 +01:00
Martin Diehl 775a51faa1 explicit instance mapping not needed 2021-02-13 10:11:39 +01:00
Martin Diehl b3dde6d722 only one damage mechanism per phase
material.yaml specification is designed to allow more than one, but that
requires to have two phase fields etc.
For the moment, keep it as simple as possible.
2021-02-13 09:55:17 +01:00
Martin Diehl 6e3515982d not needed outside of thermal 2021-02-13 07:55:32 +01:00
Martin Diehl f95e3bc08d simplified access pattern 2021-02-13 07:25:48 +01:00
Martin Diehl c790c82a42 separating by instance just complicates things 2021-02-13 06:59:18 +01:00
Martin Diehl 2b0b1aeffe jobname.yaml not supported anymore 2021-02-13 06:31:06 +01:00
Martin Diehl 830d00fa67 simplified structure
choice of damage model triggers eigendeformation, no repeated variables
This implementation is the most ugly hack I could imagine. I just serves
the purpose of having a stable material.yaml
2021-02-12 22:46:26 +01:00
Test User 2676837578 [skip ci] updated version information after successful test of v3.0.0-alpha2-428-gb7b764ab5 2021-02-12 22:30:53 +01:00
Franz Roters b7b764ab5f Merge branch 'polishing-for-release' into 'development'
Polishing for release

See merge request damask/DAMASK!334
2021-02-12 18:46:04 +00:00
Martin Diehl fe63adcca4 mimic python error message and ensure that error is raised 2021-02-12 18:20:39 +01:00
Martin Diehl 4eb2a981ca keeping variables local 2021-02-12 15:31:43 +01:00
Martin Diehl a09989fe0b homogenized damage only needed in homogenization 2021-02-12 12:35:50 +01:00
Sharan Roongta 9e8a243d6f avoid name conflict with lattice parameter 'c' 2021-02-12 12:15:08 +01:00
Sharan Roongta f1b8978e21 accept variables that will be used
**kwargs allowed the use of extraneous arguments
2021-02-12 11:24:12 +01:00
Martin Diehl 7bec3e0363 use partitioned damage 2021-02-12 11:24:04 +01:00
Martin Diehl 462ca1a30b not needed 2021-02-12 08:10:25 +01:00
Martin Diehl f6be3fe0b7 no need for pointer 2021-02-12 07:58:00 +01:00
Martin Diehl 4515920b69 not needed 2021-02-11 23:54:43 +01:00
Martin Diehl 958936c449 Merge branch 'development' into polishing-for-release 2021-02-11 21:59:59 +01:00
Martin Diehl 09c330b8d2 test for CRLF error (got lost) 2021-02-11 21:57:44 +01:00
Martin Diehl e8fae6b2a7 simplified 2021-02-11 21:56:53 +01:00
Martin Diehl e855083964 systematic names 2021-02-11 14:19:04 +01:00
Test User 992b4a7e6d [skip ci] updated version information after successful test of v3.0.0-alpha2-421-ge96352b0e 2021-02-11 11:42:33 +01:00
Franz Roters e96352b0ea Merge branch 'parse-CRLF-YAML' into 'development'
Stop if YAML contains CRLF line endings

See merge request damask/DAMASK!333
2021-02-11 09:08:03 +00:00
Martin Diehl 4e31862f0f avoid repetition 2021-02-10 18:35:13 +01:00
Martin Diehl 6895ef6b18 always write LF line endings
small pitfall: I windows users use a filehandle that results from a call
to open() without the newline option, they get still CRLF line endings
2021-02-10 10:03:35 +01:00
Martin Diehl 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
Martin Diehl 5b8e199627 avoid errors related to CRLF (windows) file endings 2021-02-10 00:02:38 +01:00
Martin Diehl 4bcbcb34d0 ensures that at least one orientation in the FZ is found 2021-02-09 23:58:00 +01:00
Martin Diehl 869307c5ec temperature not needed for pure mechanics
would also require to define thermal homogenization
2021-02-08 22:56:37 +01:00
Test User d5c98bbf62 [skip ci] updated version information after successful test of v3.0.0-alpha2-415-g09c2d7f3f 2021-02-05 18:46:17 +01:00
Franz Roters 09c2d7f3f3 updated tests 2021-02-05 17:12:00 +01:00
Franz Roters 8048d69a97 [skip ci] logic inverted 2021-02-05 16:59:28 +01:00
Sharan Roongta ba2e8b3c63 variable name follows label 2021-02-05 11:57:18 +01:00
Sharan Roongta a1a7a339d4 specify solver,initial and boundary conditions in load file 2021-02-05 11:20:28 +01:00
Sharan Roongta 2e173b4b7b 'estimate_rate' better describes what we want to do than 'drop_guessing'
true by default
2021-02-04 19:17:32 +01:00
Sharan Roongta cab5a5cec7 homogenization 'none' name misleading. 2021-02-04 15:37:40 +01:00
Sharan Roongta 14ce127dc4 fraction --> v 2021-02-04 13:46:01 +01:00