Open Gbowker opened 3 years ago
Thanks Guy. Might as well throw the option to use an existing load case file in there as well!
EDIT: actually never mind about the load case file for now, that is easy enough to include directly in the simulate_volume_element_loading
task.
ffe6322
to matflow-damask branch: ve_from_input_filesThanks Guy. Might as well throw the option to use an existing load case file in there as well!
EDIT: actually never mind about the load case file for now, that is easy enough to include directly in the
simulate_volume_element_loading
task.
No I do think it would be better to keep separate as a task so as to keep the workflow as modular as possible? Unless you mean defining a filepath to the .load file in the simulate_volume_element_loading
task?
If you want to add a generate_load_case
task with method from_DAMASK_load_file
, that would be nice, but it's not vital at the moment. We would need to add a new function damask_parse.readers.read_load
to parse DAMASK's new YAML load file format.
In order to perform replicate simulations of dual phase microstructure experimental loading, the ability to use predefined damask input files in a matflow-damask workflow requires implementation
Note:
Task name: generate_volume_element ( already used here; task_schema l:335 and here; func mappers l:43 ) Method name: from_damask_input_files Implementation name: damask
Inputs
Function steps
Output
Implementation