Reporting Measure Arguments

[nmerket]

Fixes # . (is there an issue for this @asparke2?)

Pull Request Description

This correctly wires up the reporting measures again after the big refactor and adds the ability to specify arguments for them in the configuration file.

Checklist

Not all may apply

• Code changes (must work)
• Tests exercising your feature/bug fix (check coverage report on CircleCI build -> Artifacts)
• All other unit tests passing
• Update validation for project config yaml file changes
• Update existing documentation
• Run a small batch run to make sure it all works (local is fine, unless an Eagle specific feature)
• Add to the changelog_dev.rst file and propose migration text in the pull request

[nmerket]

@asparke2 I added the reporting_measures argument and validation to the commercial workflow generator, but I stopped short of implementing it because I didn't know where you wanted the measures added to your workflow.

Here's how I did it for the residential workflow. Yours will probably be very similar.

buildstockbatch/buildstockbatch/workflow_generator/residential.py

Lines 336 to 341 in dc2cbe6

	if 'reporting_measures' in workflow_args:
	for reporting_measure in workflow_args['reporting_measures']:
	if 'arguments' not in reporting_measure:
	reporting_measure['arguments'] = {}
	reporting_measure['measure_type'] = 'ReportingMeasure'
	osw['steps'].insert(-1, reporting_measure) # right before ServerDirectoryCleanup

[nmerket]

@asparke2 You feeling like this is ready? I'm thinking it is.

[asparke2]

Looks good! I made one last commit to address a bug I just found when testing another local docker run.

[nmerket]

Ah, good catch! I'll merge this then.