In the current implementation, creating the mgra input file with the RSM zones is part of the zone aggregator process.
When setting the flag to skip running the zone aggregator for a scenario, the user specifies a reference location to use the RSM zone system from an RSM baseline run, as a result the taz and mgra crosswalks and mgra file gets copied from the reference baseline.
The problem is that if one were to specify a different MGRA for a land-use test of RSM and chose to skip the zone aggregator, their RSM scenario landuse will get overwritten when the zone system is read from baseline run.
Required Code Change:
When skipping the zone aggregator, only copy the mgra and RSM zones crosswalks from the baseline
Move the process to create mgra data file (with RSM zones) outside of zone aggregator and in the input aggregator. It will use the existing mgra file from the current scenario input folder, use the copied crosswalks and create the mgra file with RSM zones in the input folder.
@vivekyadav26 Let me know if there is any further clarification needed.
In the current implementation, creating the mgra input file with the RSM zones is part of the zone aggregator process.
When setting the flag to skip running the zone aggregator for a scenario, the user specifies a reference location to use the RSM zone system from an RSM baseline run, as a result the taz and mgra crosswalks and mgra file gets copied from the reference baseline.
The problem is that if one were to specify a different MGRA for a land-use test of RSM and chose to skip the zone aggregator, their RSM scenario landuse will get overwritten when the zone system is read from baseline run.
Required Code Change:
@vivekyadav26 Let me know if there is any further clarification needed.