Releases: LightForm-group/matflow
Releases · LightForm-group/matflow
v0.2.7
[0.2.7] - 2020.08.18
Added
- Default values can be specified for output map options within the schema
- Default values can be specified for task input parameters within the schema
- Depending on the inputs defined, different commands can be run, via "command pathway" definitions in the schema implementations.
Changed
- Uses
hickle
version 4. - Group structure in workflow HDF5 file has changed (backwards-incompatible); element data is more conveniently organised for inspecting the HDF5 file manually.
Fixed
- Fix problem when a task input key includes slashes.
v0.2.6
v0.2.5
v0.2.4
v0.2.3
[0.2.3] - 2020.06.26
Changed
- Files generated by input maps are only saved into the workflow file if explicitly requested with
save: true
.
Fixed
- Fix bug in
SourcesPreparation.get_formatted_commands
that appears if there are no commands.
v0.2.2
v0.2.1
v0.2.0
[0.2.0] - 2020.06.09
Added
- Add a
Workflow.history
attribute that tracks when the workflow was modified. It also stores pertinent software versions. - Add a CLI command
matflow validate
that runs through the task schema and extension validation. - Add a CLI command
matflow kill
, which kills all executing and pending tasks. - Added configuration option
prepare_process_scheduler_options
to specify scheduler options for the prepare and process tasks. - matflow profile is stored as a
dict
in addition to a string representation of the profile file (both in theWorkflow.profile
attribute).
Changed
- Module and function
jsonable.py
andto_jsonable
renamed tohicklable.py
andto_hicklable
. - Workflow and Task attributes in the workflow HDF5 file are now represented without leading underscores.
- Tasks with only a single element use the task directory directly instead of using an element sub-directory.
- Loading extensions and configuration files has been moved from the root
__init__
to separate modules. make_workflow
,submit_workflow
,load_workflow
,append_schema_source
,prepend_schema_source
andvalidate
can now be imported from the root level:from matflow import make_workflow
etc.- There are no longer unsightly global variables for
TASK_INPUT_MAP
etc. This functionality has been subsumed into the globalConfig
class. This is tidier and provides a better place for some validation. - Software key
sources
has been replaced byenvironment
. - hpcflow configuration directory is generated within the matflow configuration directory.
- Jobscript names refer to the task to which they prepare/execute/process
- hpcflow profile is passed as a
dict
to hpcflow. For information, the hpcflow profile is still dumped to a file.