The mission of Project Drawdown is to help the world reach “Drawdown”— the point in the future when levels of greenhouse gases in the atmosphere stop climbing and start to steadily decline, thereby stopping catastrophic climate change — as quickly, safely, and equitably as possible.
Currently some integrations update the values of parameters in the solution's workbook. In the manual Excel process, researcher's determine if the value they want to update has already been updated (they use color coding on the cell header), and if it was previously updated, they get a new "raw" version of that input to feed into the integration, then replace the integrated result.
Python doesn't have color-coded parameters, so we have no way, currently, to know if a parameter has previously been updated or not. We might fix this either by keeping two parameters (a pre-integration and a post-integration one), or by making the integrations directly ask the solutions for a "raw" version of the parameter. But to get avoid double-counting and get correct results, we need some way to handle this issue.
Currently some integrations update the values of parameters in the solution's workbook. In the manual Excel process, researcher's determine if the value they want to update has already been updated (they use color coding on the cell header), and if it was previously updated, they get a new "raw" version of that input to feed into the integration, then replace the integrated result.
Python doesn't have color-coded parameters, so we have no way, currently, to know if a parameter has previously been updated or not. We might fix this either by keeping two parameters (a pre-integration and a post-integration one), or by making the integrations directly ask the solutions for a "raw" version of the parameter. But to get avoid double-counting and get correct results, we need some way to handle this issue.