From b7a9eea3e1a5f2942caa7f44be540a3fa38b91f3 Mon Sep 17 00:00:00 2001
From: daymontas1 <53146798+daymontas1@users.noreply.github.com>
Date: Fri, 3 May 2024 16:10:43 +0200
Subject: [PATCH] Update MESSAGE-MACRO_run.gms

Defining ''solve_param'' in ''MESSAGE-MACRO_run.gms'' creates a problem in testing. Therefore, ''solve_param'' is defined in ''macro_data_load.gms'' instead.
---
 message_ix/model/MESSAGE-MACRO_run.gms | 2 --
 1 file changed, 2 deletions(-)

diff --git a/message_ix/model/MESSAGE-MACRO_run.gms b/message_ix/model/MESSAGE-MACRO_run.gms
index fe3815569..abdd3b352 100644
--- a/message_ix/model/MESSAGE-MACRO_run.gms
+++ b/message_ix/model/MESSAGE-MACRO_run.gms
@@ -89,9 +89,7 @@ Set
 * NB MAX_ADJUSTMENT and max_adjustment have different meanings:
 * - MAX_ADJUSTMENT is a fixed threshold used to truncate the relative demand change produced by MACRO.
 * - max_adjustment is the amount of that change, after any truncation.
-*setting solve_param to 1 (the default values) triggers sequential solving across regions in MACRO, whereas setting it to 2 enables concurrent solving for all regions
 Scalar
-    solve_param        solving mechanism for MACRO                                  / 1 /
     max_adjustment_pre maximum adjustment in previous iteration                     / 0 /
     max_adjustment_pos maximum positive adjustment in current iteration
     max_adjustment_neg maximum negative adjustment in current iteration