scaling code in strategy.py uses a more abstract notion of "scaling units" that only make sense in proportional to other scaling load amounts (i.e. ratios) - htex uses "tasks" as the unit. wq now uses "cores" as the unit.

variables and text inside strategy.py should explain this. variables and docstrings should be clearer about this.

Author: benclifford