Dear WRF-Chem team,
I’m running WRF-Chem v4.7 over India with one parent (d01, 27 km) and three parallel children (d02-d04, 9 km) using two-way nesting (feedback=1). To assess regional impacts of city-scale emissions, I plan to add short emission pulses near each child domain’s center and evaluate the response within each child.
In this setup, should I perturb emissions only in the child domains, or also in the overlapping area of d01? I want to avoid double counting or inconsistent mass budgets. More generally, how are emissions handled with two-way nesting. E.g., are child emissions ever aggregated back to d01, or does feedback only exchange state variables while each domain reads its own emission inputs?
If the recommended practice is to modify only the children, is it preferable to keep d01 emissions unchanged over the child footprints, or to zero them during the injection hour(s)?
Any guidance or pointers to documentation would be greatly appreciated. Thank you for your time!
Best,
Yuhan
I’m running WRF-Chem v4.7 over India with one parent (d01, 27 km) and three parallel children (d02-d04, 9 km) using two-way nesting (feedback=1). To assess regional impacts of city-scale emissions, I plan to add short emission pulses near each child domain’s center and evaluate the response within each child.
In this setup, should I perturb emissions only in the child domains, or also in the overlapping area of d01? I want to avoid double counting or inconsistent mass budgets. More generally, how are emissions handled with two-way nesting. E.g., are child emissions ever aggregated back to d01, or does feedback only exchange state variables while each domain reads its own emission inputs?
If the recommended practice is to modify only the children, is it preferable to keep d01 emissions unchanged over the child footprints, or to zero them during the injection hour(s)?
Any guidance or pointers to documentation would be greatly appreciated. Thank you for your time!
Best,
Yuhan