Stochastic Programming - Index of
Stochastic Programming - Index of
Stochastic Programming - Index of
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
DYNAMIC SYSTEMS 135<br />
with z 0 given. Let α be a discount factor. What is <strong>of</strong>ten done in this case is<br />
to solve for each s ∈ S the following problem<br />
min<br />
s.t.<br />
T∑<br />
α t r t (z t ,x t ,ξt s )+α T +1 Q(z T +1 )<br />
t=0<br />
z t+1 = G t (z t ,x t ,ξ s t )fort =0,...,T with z 0 given,<br />
A t (z t ) ≤ x t ≤ B t (z t )fort =0,...,T,<br />
⎫<br />
⎪⎬<br />
⎪⎭<br />
(6.1)<br />
where Q(z) represents the value <strong>of</strong> ending the problem in state z, yielding<br />
an optimal solution x s =(x s 0 ,xs 1 ,...,xs T ). Now what We have a number <strong>of</strong><br />
different solutions—one for each s ∈ S. Shall we take the average and calculate<br />
for each t<br />
x t = ∑ p s x s t ,<br />
s∈S<br />
where p s is the probability that we end up on scenario s This is very <strong>of</strong>ten<br />
done, either by explicit probabilities or by more subjective methods based on<br />
“looking at the solutions”. However, several things can go wrong. First, if x is<br />
chosen as our policy, there might be cases (values <strong>of</strong> s) forwhichitisnoteven<br />
feasible. We should not like to suggest to our superiors a solution that might<br />
be infeasible (infeasible probably means “going broke”, “breaking down” or<br />
something like that). But even if feasibility is no problem, is using x a good<br />
idea<br />
In an attempt to answer this, let us again turn to event trees. In Figure 12 we<br />
have T = 1. The top node represents “today”. Then one out <strong>of</strong> three things can<br />
happen, or, in other words, we have a random variable with three outcomes.<br />
The second row <strong>of</strong> nodes represents “tomorrow”, and after tomorrow a varying<br />
number <strong>of</strong> things can happen, depending on what happens today. The bottom<br />
row <strong>of</strong> nodes takes care <strong>of</strong> the rest <strong>of</strong> the time—the future.<br />
This tree represents six scenarios, since the tree has six leaves. In the setting<br />
<strong>of</strong> optimization that we have discussed, there will be two decisions to be made,<br />
namely one “today” and one “tomorrow”. However, note that what we do<br />
tomorrow will depend on what happens today, so there is not one decision for<br />
tomorrow, but rather one for each <strong>of</strong> the three nodes in the second row. Hence<br />
x 0 works as a suggested first decision, but x 1 isn’t very interesting. However, if<br />
we are in the leftmost node representing tomorrow, we can talk about an x 1 for<br />
the two scenarios going through that node. We can therefore calculate, for each<br />
version <strong>of</strong> “tomorrow”, an average x 1 , where the expectation is conditional<br />
upon being on one <strong>of</strong> the scenarios that goes through the node.<br />
Hence we see that the nodes in the event tree are decision points and the arcs<br />
are realizations <strong>of</strong> random variables. From our scenario solutions x s we can<br />
therefore calculate decisions for each node in the tree, and these will all make