v1.0.2

SFHWorkflows v1.0.2

Diff since v1.0.1

• Write input config to input.yml in the output directory
• Validate filters listed in the binning section of the config with those listed in the data/photometry section

Because you can read in an example config as a dictionary with YAML.load_file(...), and then edit the dictionary, and then call fit_sfh, the original config file may not reflect the parameters that the results were run with. This inserts in the parse_config(::AbstractDict) method a write of the config dictionary to a file in the output directory. This way even if you altered the config dictionary programmatically, you still have a record of what parameters the code was run with.

This also adds validation of the input yfilter and xcolor from the binning section of the config against the filters that were defined in the config["data"]["photometry"]["binning"] section so that a user-friendly error is surfaced if the filters differ between these two sections.

Closed issues:

• Verify photometry filters against AST filters during parsing (#6)

v1.0.1

SFHWorkflows v1.0.1

Diff since v1.0.0

• Fix Tmax (should be T_max) keys in example config.yml for LinearAMR and LogarithmicAMR
• Revise readdlm call for reading photometry and AST files to accept any number of whitespaces as the delimiter

Closed issues:

• Use Apps feature (#3)

v1.0.0

SFHWorkflows v1.0.0

Initial release of standard star formation history workflow (based on StarFormationHistories.jl) using input configuration file