Past year model run shouldn't require FUTURE to be specific (e.g. PBA50) #45

lmz · 2021-06-10T16:37:58Z

Reported by @alexmitrani, TM1.5 doesn't run smoothly for historic years (e.g. 2015) with FUTURE=NA
but rather requires FUTURE=PBA50 etc, which doesn't really make sense as it's not in the future.

Document what's requiring FUTURE to be set this way and remove the constraint for historic runs.

lmz changed the title ~~Historical model run shouldn't require FUTURE to be specific (e.g. PBA50)~~ Past year model run shouldn't require FUTURE to be specific (e.g. PBA50) Jun 10, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Past year model run shouldn't require FUTURE to be specific (e.g. PBA50) #45

Past year model run shouldn't require FUTURE to be specific (e.g. PBA50) #45

lmz commented Jun 10, 2021 •

edited

Loading

Past year model run shouldn't require FUTURE to be specific (e.g. PBA50) #45

Past year model run shouldn't require FUTURE to be specific (e.g. PBA50) #45

Comments

lmz commented Jun 10, 2021 • edited Loading

lmz commented Jun 10, 2021 •

edited

Loading