b2fea6b149
solver not specific to load case number
2021-02-28 19:24:44 +01:00
4dd99d4c39
solver is selected in load case, not numerics.yaml
2021-02-28 19:13:20 +01:00
c483dc609f
common name
2021-02-28 11:47:27 +01:00
be0e393e1d
cleaning homogenization
2021-02-25 21:55:15 +01:00
9679c5403e
continue with cell based map (solver + homog)
2021-02-23 15:44:58 +01:00
d8112cc2e1
storing by instance just complicates the code
2021-02-23 13:45:06 +01:00
89858543fa
more cleaning; use 'ce', 'ph', 'me' wherever applicable
...
hide ip,el
2021-02-23 11:47:29 +01:00
286f59ed8c
fix for OpenMP
2021-02-23 10:47:04 +01:00
8d57252a54
Merge remote-tracking branch 'origin/development' into internal-restructure
2021-02-23 09:03:57 +01:00
e249168189
modifying storing of orientations;
...
needed for nonlocal, and also to remove the use if ip,el at homogenization level.
ip, el should be used only for looping eventually.
2021-02-22 20:38:49 +01:00
2f9d891fdd
instance less; use cell mapping
2021-02-22 16:17:32 +01:00
5348305ac8
restart key part of loadstep and not time discretization
2021-02-22 14:42:54 +01:00
4d5e5cfb70
Merge branch 'fix-IntelMPI' into 'development'
...
Bugfix for access of unallocated variable
See merge request damask/DAMASK!342
2021-02-22 12:40:37 +00:00
d54e49e3bc
restore functionality to write non-parallel
...
not needed at the moment, but in general useful. If PETSc = parallel
should always hold, we can simplify much more
2021-02-22 13:37:21 +01:00
db25bc947d
Merge remote-tracking branch 'origin/development' into internal-restructure
2021-02-19 15:19:42 +01:00
6c7201610e
Bugfix for access of unallocated variable
...
IntelMPI seems to access sendbuf for root!=0 in MPI_Scatterv
2021-02-17 17:56:39 +01:00
53bab41b47
consistent name 'ph' and cleaning
2021-02-16 16:06:09 +01:00
9f78e27724
use cell mapping
2021-02-15 18:43:51 +01:00
341e8ddd6a
storing per instance does not add any value
2021-02-14 18:34:48 +01:00
f46d212e47
simplified access pattern
2021-02-14 17:35:39 +01:00
4026881e5a
clean interface
...
still need to get rid of internal converstion to instance and el,ip
arguments
2021-02-14 15:29:10 +01:00
5a1ca012f8
more suitable data structure
...
no need to know (ip,el) at the constitutive level
2021-02-14 14:36:56 +01:00
18971d7d8b
separation by instance does not add any value
2021-02-14 10:26:33 +01:00
c09c2a6c8e
easier to read without instance
2021-02-14 00:50:42 +01:00
5126370934
cleavageopening+anisobrittle are strongly coupled
2021-02-13 19:20:52 +01:00
9481b16878
missing renames
2021-02-13 19:10:13 +01:00
8dc53344ec
'kinematics'=>'eigen', now part of 'mechanics'
2021-02-13 18:52:37 +01:00
22a0aff488
separting thermal and damage sources
2021-02-13 18:41:30 +01:00
72c099dbbe
store data separetly
2021-02-13 15:06:27 +01:00
595ee7a35a
copy and paste error
2021-02-13 14:38:53 +01:00
b3231bf0a8
avoid undefined return
2021-02-13 14:15:41 +01:00
ab202b8e73
less verbose reporting
2021-02-13 13:07:35 +01:00
570086c814
hard code at max 1 damage mechanism
2021-02-13 13:07:12 +01:00
d9699b0f2e
simplified access pattern
2021-02-13 11:01:08 +01:00
775a51faa1
explicit instance mapping not needed
2021-02-13 10:11:39 +01:00
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
6e3515982d
not needed outside of thermal
2021-02-13 07:55:32 +01:00
f95e3bc08d
simplified access pattern
2021-02-13 07:25:48 +01:00
c790c82a42
separating by instance just complicates things
2021-02-13 06:59:18 +01:00
2b0b1aeffe
jobname.yaml not supported anymore
2021-02-13 06:31:06 +01:00
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
4eb2a981ca
keeping variables local
2021-02-12 15:31:43 +01:00
a09989fe0b
homogenized damage only needed in homogenization
2021-02-12 12:35:50 +01:00
7bec3e0363
use partitioned damage
2021-02-12 11:24:04 +01:00
462ca1a30b
not needed
2021-02-12 08:10:25 +01:00
f6be3fe0b7
no need for pointer
2021-02-12 07:58:00 +01:00
4515920b69
not needed
2021-02-11 23:54:43 +01:00
958936c449
Merge branch 'development' into polishing-for-release
2021-02-11 21:59:59 +01:00
e855083964
systematic names
2021-02-11 14:19:04 +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
Martin Diehl