ariesteam/aries — Issue #38: Consolidated storylines issue
Author: kbagstad
Created: 2011-12-27 23:33:50+00:00
State: open

I've put in a lot of work on storylines and have a few more items to hopefully wrap them up, along with the big job of testing them.

1) In the sediment assessment files, the units for sediment erosion and deposition are not uniform between the case studies. Will this pose problems and how would you propose to deal with it? One obvious way would just be to do a transformation on the data in the .xml so that it’s always in consistent units. Thoughts?

2) In the coastal protection storyline, why did you initially put in both LivesAtRiskStorm/CycloneDependentLivesAtRisk and the corresponding pair of assets at risk concepts in the storyline? These seem highly redundant, like one should be removed. Agree?

3) An old issue that I haven’t been able to re-test: for some reason in the ARIES explorer 2 versions of the "water supply" storyline are showing up. Not sure why this would be the case, but clearly there should only be one.

4) Top-level concepts are now done consistently, if most likely incorrectly. We should schedule a brief screenshare to make sure we’re on the same page and that these are done correctly once and for all.

5) Just to be clear, to extract output data from a BN into the storyline, are we calling on the concept from the old undiscretizer? That's how I've been entering it but it could be a source of problems if that's not the case.