From 297901259b7d5dcd7237972c1fa182ad16fde611 Mon Sep 17 00:00:00 2001 From: Dominic Ricottone Date: Thu, 24 Oct 2024 10:28:35 -0500 Subject: [PATCH] Fix markup I mixed up the markup for subscripts. In LaTeX, etc., subscript is marked up like foo_1 or foo_{bar}. In GH flavor markdown, subscript is marked up like foo~1~ or foo~bar~. I had mistakenly used foo_1_. --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index f0678b3..151f85b 100644 --- a/README.md +++ b/README.md @@ -22,16 +22,16 @@ Enbo Zhou. > Mathematical programming usually has the following form: > -> Maximize/Minimize f(X_1_, X_2_, ... x_n_) +> Maximize/Minimize f(X_1, X_2, ... x_n) > -> Subject to g_1_(X_1_, X_2_, ... x_n_) <= b_1_; g_2_(X_1_, X_2_, ... x_n_) <= b_2_; ... g_m_(X_1_, X_2_, ... x_n_) <= b_m_ +> Subject to g_1(X_1, X_2, ... x_n) <= b_1; g_2(X_1, X_2, ... x_n) <= b_2; ... g_m(X_1, X_2, ... x_n) <= b_m > -> Where X_i_, i = 1, 2, ... n, are decision variables, +> Where X_i, i = 1, 2, ... n, are decision variables, > f is the objective function measuring soluton quality, > and we optimize f to acquire the best solution. -> g_i_, i = 1, 2, ... m, are mathmatical [functions] to help formalize +> g_i, i = 1, 2, ... m, are mathmatical [functions] to help formalize > constraints. -> b_i_, i = 1, 2, ... m are constants to define constraints. +> b_i, i = 1, 2, ... m are constants to define constraints. > [L]et us assume that that the US Forest Service is planning to treat 100 > acres (threshold capacity) of the Stanislaus National Forest to decrease -- 2.45.2