Roadmap
Changelog

We want your feedback!

Request new features, report bugs, or provide general feedback—we appreciate it all. If you are reporting a bug, please include as much detail as possible, including any steps you took prior to finding the issue and screenshots when possible.

Faster Add Forecast to Collection

Would be ideal to more quickly add a forecast to a collection in two specific spots: On your list of /analyses/ page - have a quick actions button to add to collection. Would need to include a custom modal that allows user to select the specific baseline/solution/market/capture from the analysis (and which collection to add it to). On the /collections/ page in My Collections list and in Contents tab. Would need dialog to select specific baseline/solution/market/capture.

gilman.callsen 2 months ago

💡 Feature Request

Precise Koi Engine Route information

It would be awesome to have some kind of precise / known tag for the engine route (path) that was followed ot produce a given scenario. Right now there are only so many, so it’s not terribly difficult to discern by looking at the model and the techlib file BUT, because pathways do different things in order to handle data availability issues and/or might also include use of special submodules (CDR or “Soft / Facilitator”) I think it would be valuable to know what route it took to get there so that if it looks funky / buggy, we have a more targeted method by following such markers.

seth.sheldon 3 months ago

1

📥 Feedback & Ideas

Adapt search bar to accommodate multiple models with same name

This is not a bug but more of a personal observation/suggestion. When searching using the “rooftop” keyword, multiple models appear with the same name. After selecting “preview,” I recognize they are slightly different (in terms of market capture, description, etc.), and I get that they’re probably generated based on different company IPs. From a UX perspective, it would save time and effort for a user to be able to distinguish between these models more easily. For instance, if there was an extra column listing those key differences, or if models would somehow be pooled into one master “Rooftop PV Systems” category (this one is especially helpful when a user is searching for something not solar PV related, yet getting so many irrelevant results).

giedre.darg 3 months ago

1

📥 Feedback & Ideas

Bad rounding for high GWP model

Because the GHG intensities are so high (best expressed in Mt/kt), if the user selects Mt per Mt, the solution scale is mistakenly rounded to “0”. Would it be hard to add a contingency where is the Unit Impact is >5000 in t/t, more sig figs are shown? Or some other way of handling this more extreme case w/o misleading 0s. https://app.koi.eco/forecast/910114/1-0?baselineId=89401&solutionId=89402&marketSizeId=12945&marketCaptureId=8405&numUnitId=1351&denUnitId=1351&tab=ui

aurora.ginzburg 3 months ago

1

🐛 Bug Reports

Wacky default Geographic scope

This must be an Engine issue, but some % of the default models appear to be defaulting to national-level geographies rather than World, even though world would be more logical. Possible solution is enforcing geo rules at outset and having those developed, or possibly always starting with World and then having relative scales to that (anchored to that)

seth.sheldon 3 months ago

2

🐛 Bug Reports

"duplicate baseline scenario" for solution editing button

It came up on a call that if a consultant wanted to very simply duplicate a baseline, set it as the soln scenario, and then ask the startup what % they are reducing phases by, that is not always possible. The limitation comes from the available soln scenarios to duplicate being limited to records set to be available as “solutions”. Could be useful to have a “duplicate baseline” as the soln scenario for consultants who want to have simple way of asking startups where they are interfering in a baseline scenario.

aurora.ginzburg 4 months ago

💡 Feature Request

warning or message when zeros are due to rounding

quick idea I wanted to throw out there -- a stopgap option for avoiding false zeros (in the sense that people see a zero and think it is genuine 0 rather than a small number). Idea is maybe we just throw a small warning / tag when all of the values are showing 0, like "note: all values are showing up as zero, possibly due to rounding. try adjusting the UOMs for the numerator and denominator"):

seth.sheldon 6 months ago

📥 Feedback & Ideas