Matthew Gidden
Matthew Gidden
Observation: Using `add_year()` on the current main branch results in scenarios with misaligned `input`, `output` and `technical_lifetime parameters`. This can result in completely unexpected results. Below, for example, is the...
I have experienced silent errors when performing multiple `message_ix.Scenario.solve()`s simultaneously on the same computer. As best I can tell, these occur when I employ the `solve_options` kwarg, which forces a...
# Request In many contexts, understanding the underlying reference energy system (RES) structure of a given scenario is needed. Given the RES structure in a dataframe, we can then use...
**Required:** write a single sentence that describes the changes made by this PR. This PR raises an exception at the start of `add_year()` ## How to review **Required:** describe specific...
This PR adds changes for the spigot project. To date these includ: - adding message and macro file changes from #430 **Required:** write a single sentence that describes the changes...
This issue would address potential solve speedups (e.g., I am seeing week-long solve times at the moment for some scenarios). The idea is straightforward - for a scenario which has...
Perhaps this is impossible to fix at the moment, but I ran into many many headaches before realizing that there is not a one-to-one mapping between `s.set('year')` and the set...
I regularly run into issues around scenarios being locked when they are purely used for data reading. This can be true any time a scenario is needed for cloning, for...
This basically keeps all reported/post process timeseries in the clone/removed solution scenario. Thus if reporting is run again, stale values could be still included
Per our discussion in #97, read-only operations (e.g., just reading scenario data from a database) is at the moment not thread safe. In essence, there is a `check_out()` occuring in...