LightForm-group / UoM-CSF-matflow

Matflow configuration files and task schemas for running on the University of Manchester's CSF
MIT License
8 stars 0 forks source link

Ability to use predefined .geom and material.yaml files with matflow-damask #18

Open Gbowker opened 3 years ago

Gbowker commented 3 years ago

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

  1. Read input files.
  2. Write a volume_element dict that can be passed to a simulate_volume_element_loading task. (already functionality to do these individually in damask-parse)

Output

Implementation

aplowman commented 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.

Gbowker commented 3 years ago
Gbowker commented 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.

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?

aplowman commented 3 years ago

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.