Turn code comments into set element associated texts in 1a_definitions

This way the explanations can be exported programmatically.

inc/1a_definitions.gms

@@ -32,23 +32,23 @@ Sets
     mSetting "setting categories for models" /
 
         // General Time Structure
-        t_start, // First time step for the start of simulation
-        t_jump, // Number of time steps realized with each solve
-        t_horizon, // Length of the simulation horizon in time steps (central forecast)
-        t_end, // Last time step of the simulation
-        loadPoint, // Load advanced basis; 0 = no basis, 1 = latest solve, 2 = all solves, 3 = first solve
-        savePoint, // Save advanced basis; 0 = no basis, 1 = latest solve, 2 = all solves, 3 = first solve
-        lastStepInIntervalBlock, // Last time step in the block of intervals with the same length
-        stepsPerInterval, // Number of time steps aggregated within interval
-        stepLengthInHours, // Length of one time step in hours
+        t_start "First time step for the start of simulation"
+        t_jump "Number of time steps realized with each solve"
+        t_horizon "Length of the simulation horizon in time steps (central forecast)"
+        t_end "Last time step of the simulation"
+        loadPoint "Load advanced basis; 0 = no basis, 1 = latest solve, 2 = all solves, 3 = first solve"
+        savePoint "Save advanced basis; 0 = no basis, 1 = latest solve, 2 = all solves, 3 = first solve"
+        lastStepInIntervalBlock "Last time step in the block of intervals with the same length"
+        stepsPerInterval "Number of time steps aggregated within interval"
+        stepLengthInHours "Length of one time step in hours"
 
         // Samples and Forecasts
-        samples, // Number of active samples
-        forecasts, // Number of active forecasts
-        t_forecastLengthUnchanging, // Length of forecasts in time steps - this does not decrease when the solve moves forward (requires forecast data that is longer than the horizon at first)
-        t_forecastLengthDecreasesFrom, // Length of forecasts in time steps - this decreases when the solve moves forward until the new forecast data is read (then extends back to full length)
-        t_forecastStart, // Time step for first reading the forecasts (not necessarily t_start)
-        t_forecastJump, // Number of time steps between each update of the forecasts
+        samples "Number of active samples"
+        forecasts "Number of active forecasts"
+        t_forecastLengthUnchanging "Length of forecasts in time steps - this does not decrease when the solve moves forward (requires forecast data that is longer than the horizon at first)"
+        t_forecastLengthDecreasesFrom "Length of forecasts in time steps - this decreases when the solve moves forward until the new forecast data is read (then extends back to full length)"
+        t_forecastStart "Time step for first reading the forecasts (not necessarily t_start)"
+        t_forecastJump "Number of time steps between each update of the forecasts"
         t_improveForecast "Number of time steps ahead of time on which the forecast is improved on each solve"
         t_perfectForesight "Number of time steps for which realized data is used instead of forecasts"
         onlyExistingForecasts "Use only existing forecast values when reading updated forecasts. Note: zero values need to be saved as Eps in the gdx file."
@@ -56,12 +56,12 @@ Sets
         scenarioLength   "Length of scenario in time steps for creating stocahstic scenarios from time series data"
 
         // Features
-        t_trajectoryHorizon, // Length of the horizon when start-up and shutdown trajectories are considered (in time steps)
-        t_initializationPeriod,  // Number of time steps in the beginning of the simulation which are solved but the results of which are not stored
-        dataLength, // The maximum number of time steps in any input data time series (recommended for correctly circulating data)
+        t_trajectoryHorizon "Length of the horizon when start-up and shutdown trajectories are considered (in time steps)"
+        t_initializationPeriod "Number of time steps in the beginning of the simulation which are solved but the results of which are not stored"
+        dataLength "The maximum number of time steps in any input data time series (recommended for correctly circulating data)"
         red_num_leaves "Desired number of preserved scenarios or leaves (SCENRED)"
         red_percentage "Desired relative distance (accuracy) of scenario reduction (SCENRED)"
-        incHRAdditionalConstraints // Method to include the two additional constraints for incremental heat rates;
+        incHRAdditionalConstraints "Method to include the two additional constraints for incremental heat rates"
                                    // 0 = include for units with non-convex fuel use, 1 = include for all units
         /