Hackathon Wed Notes

From <code>/earth
Jump to: navigation, search

Owen's Notes[edit]

  • Model types: Energy, Land use, Social
  • Dashboard - advanced controls: major inputs & outputs on a single tab
    • Key results
    • Markets
    • Emissions types
    • Model specific inputs
    • Base etc scenarios
    • Compares solution to conventional technology - costs, adoption and emissions
    • Normalized by functional unit
    • Adoption is modelled, drives requirements for both conventional and solutions
    • Costs include initial, operating (fixed and variable) costs
    • Variable meta-analysis tracks all the research used to inform each value (costs, emissions, adoption scenarios)
  • Other tabs:
    • Scenarios split conventional and solution in different proportions
    • Have integration models (not discussed here) that prevent double counting across models
    • TAM needs plus costs and emissions for conventional & solution split by adoption scenarios
    • Want to allow different users to create their own reference scenarios (e.g. scoped to a specific city)
    • Regions are IPCC standard regions, but models can break donw more granularly if desired
    • Some models have their own sheets that provide an input to the main model tabs
  • Adoption
    • If there is insufficient research on adoption, researcher can define own adoption curve + assumptions - this is essentially a standalone tool
    • Also a separate curve for interpolating research that is not annual
  • Glossary:
    • Functional unit - primary unit used by a model, all values converted relative to this unit
    • TAM = Total addressable market = total need for a thing, globally, over time
    • PDS = Prodect Drawdown scenario
    • Lifetime unit - how long does a first cost purchase last until it needs to be replaced/disposed etc?
    • Average annual use - expressed lifetime in terms of usage by functional unit.
    • VMA = Variable meta analysis
  • Questions:
    • What limitations have you found with the spreadsheet based model?
    • Error bars?
    • Multilingual?
  • Thoughts:
    • For all the places there are multiple outputs (conventional/solution, scenarios, projection at year X etc), these can basically loop over inner loops with different inputs
  • Audiences & outcomes:
    • Policymakers at all scales & levels (international, national, municipal etc) example: Martin O'Nally
      • Want results that are usable and actionable for our area
    • Investors and philanthropists that are intrested in climate solutions
      • Philanthropists intrested in finding most impactful organizations and tracking progress towards stated goals
        • Lack ways of measuring and comparing results across organizations
      • Investors
    • Researchers - university, non-profits, practitioner collecting data - contributors to model, want to surface "stories". A story is narrative plus data - currently global, but want to surface local, regional and national also.
      • Inform better understanding of solution sets to enable policymakers to make better decisions on their contributions and investments
      • Contribute intellectual capital by contributing data and literature reviews
    • Drawdown (synthesizing requests from researchers, educationalist, planners etc)
      • Democratize and regionalize platform - create form of distributed leadership with regional hubs that manage & maintain their own regionalization, aggregate those to inform global understanding
        • Maintain data, networks of researchers, participate in data collection and curation
        • Hubs are formed organizally: For example, currently EU, Switzerland, London etc
        • Drawdown project would be maintainer of global model, but not the sole owner of the tool.
      • Want to allow the model itself to evolve and improve over time, but still retain a harmonized approach.
  • Follow up discussion:
    • People want access - why don't they have access? Originally planned for that, but currently it seems too complicated to do, although has not been formally tested.
      • Intent for using Excel was accessibility - currently the model is not really being distributed though. Desire for the model to be fully open.
      • If we left the hackathon with documentation allowing a researcher being able to more easily download and use the model, would that be a success?
        • Already doing this with fellows program, but it's time and labor intensive.
        • This is quite model specific - not an integrated system that allows people to access all models.
      • We have talked about some things that are hard to do in current system:
        • e.g. duplicated data across multiple sheets, other limitations.
        • Enable people to ask "what if" and understand secondary effects (across multiple models).
    • Data separation for licensing issues?
  • Potential directions:
    • (a) Integrated system - provide ways for users to get answers across multiple solutions
    • (b) Update data (in Excel?) - need to copy paste data into multiple spreadsheets
    • (c) Use of system requires expert knowledge
    • (d) Should we be out of Excel?
    • (e) Board recommendation
  • Agreed goals:
    • Release 1 spreadsheet and 1 python program under a free software license.
    • We will choose 1 module that are part of the core model.
    • Design evolution of modules/pipeline.
    • Graceful evolution of existing module functionality into new framework.