Closed kbagstad closed 12 years ago
Can you give the contexts/colorado.clj file a quick look? I'm looking for a way to set all values to zero, effectively, across the map - not just within some predefined scenario area. It seems like this should do it (adapted the code from the San Pedro context file) but when I run models I'm not seeing much difference. This is particularly true for carbon - run commands are model -o core.models.carbon-colorado/identification-carbon core.contexts.beta/co_grand_boulder_larimer (the base case) and core.models.carbon-colorado/identification-carbon core.contexts.colorado/no-mountain-pine-beetle-carbon (the scenario).
Gary hadn't seen the context file way of doing scenarios, so wasn't familiar with it, so a quick check of my syntax and assumptions would go a long way here.
Just to clarify, I know how to use scenarios that change values for certain pixels (most of the detailed San Pedro scenarios that we fought forever with) or polygons (the San Pedro context file). What I'm not clear about is how to change a single node's value over an entire context area. I think it's been done right in the CO context but give it a look - I'm still seeing weird results from carbon in particular, though viewshed seems to work, and I can't tell why one should work and another shouldn't.
I just had a look - the contexts are right (not much to go wrong there) - no condition means to apply the change indiscriminately across the whole map. The case you indicate seems to work ok at my side, at least for the variable it's supposed to affect. If I run with the two contexts I get
colorado:ModerateDamage |****\ | 110462 colorado:NoDamage | | 8412 colorado:LowDamage | | 5208
no-data |*****| 688660
for the unmodified case, and
no-data |***| 688660
with the modified scenario. Is anything else going on that seems strange?
@fvilla