You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: