Bump initial_{activity,new_capacity}_up values

Resolve infeasibilities with updated base model.
iiasa · Dec 5, 2024 · 8967c53 · 8967c53
1 parent 1153b7a
commit 8967c53
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 3 deletions.
diff --git a/message_ix_models/model/transport/config.py b/message_ix_models/model/transport/config.py
@@ -71,8 +71,10 @@ class Config(ConfigHelper):
             "non-LDV growth_activity_lo": -0.0192 * 1.0,
             "non-LDV growth_activity_up": 0.0192 * 2.0,
             "non-LDV growth_new_capacity_up": 0.0192 * 1.0,
-            "non-LDV initial_activity_up": 1.0,
-            "non-LDV initial_new_capacity_up": 1.0,
+            # NB If these values are not large enough, they can cause infeasibilities in
+            #    the base period for technologies that do not have historical_activity
+            "non-LDV initial_activity_up": 2.0,
+            "non-LDV initial_new_capacity_up": 2.0,
         }
     )
 

diff --git a/message_ix_models/model/transport/non_ldv.py b/message_ix_models/model/transport/non_ldv.py
@@ -198,7 +198,10 @@ def bound_activity(c: "Computer") -> list[Key]:
 
 
 def bound_activity_lo(c: Computer) -> list[Key]:
-    """Set minimum activity for certain technologies to ensure |y0| energy use."""
+    """Set minimum activity for certain technologies to ensure |y0| energy use.
+
+    Responds to values in :attr:`.Config.minimum_activity`.
+    """
 
     @lru_cache
     def techs_for(mode: Code, commodity: str) -> list[Code]: