Car Buyer Example Decision Net

Netica

“Car Buyer” Example Decision Net

“Car Buyer” is an example decision net illustrating sequential decisions and multiple utility nodes.  For a more simple example, see the Umbrella example.

Open “Car Buyer Neapolitan” from the = 4 && typeof(BSPSPopupOnMouseOver) == 'function') BSPSPopupOnMouseOver(event);" class="BSSCPopup" onclick="BSSCPopup('X_PU_examples_folder.htm');return false;">Examples folder.  It is from Neapolitan90, which is a simpler version of the car buyer example of Howard62.  Eliminating the rationale given there of how the numbers are arrived at, we have the following story:

Joe is going to buy a used car, which could be good with probability 0.8 or a lemon with probability 0.2.  After accounting for repairs, Joe’s profit will be $60 if the car is good, and $-100 if it is bad.  Before buying the car he has the option of having one test or two tests done on it.  The first test costs $9, and both together cost $13.  The first test has a 90% chance of returning positive if the car is good, and a 40% chance if it’s a lemon.  If the first test returns positive, then the second test has a 88.89% chance of returning positive if the car is good, and a 33.33% chance if it’s a lemon.  If the first test returns negative, then the second test has a 100% chance of returning positive if the car is good, and a 44.44% chance if it’s a lemon.

Joe has 2 decisions to make: whether to do the tests, and whether to buy the car.  These are represented by the “Do Tests?” and “Buy It?” decision nodes.  The outcome of the tests are given by nodes “First Test” and “Second Test”.  The costs of the tests are represented by utility node U, and the profits after repairs (not including test costs) by utility node V.  The overall utility is the sum of these two (with costs being negative).

When Joe decides whether to do the tests, he doesn’t know the value of any of these variables, so there are no links entering the “Do Tests?” node.  When he decides whether to buy, he will know the outcome of both tests (the outcomes may be “not done”), and so there are links from those two nodes to “Buy It?”.  He will also know the value of “Do Tests?” since he has already made that decision, so you could put a link from that node to “Buy It?”, but it is not necessary since it is a no-forgetting link and there is already a directed path from “Do Tests?” to “Buy It?”.

You can examine the rest of the link structure, and check out the relation tables, to make sure they make sense to you.

Then compile the net.  Since auto-updating is turned on, it will be solved immediately.  Netica adds a no-forgetting link from “Do Tests?” to “Buy It?”, indicating that “Do Tests?” may be relevant to the second decision, based only on the rest of the link structure (as it turns out, it isn’t).  The expected utility of each decision choice for “Do Tests?” is printed in the node; not doing any of the tests has the highest expected utility of 28, so it is the best choice.  No expected utilities are printed in the “Buy It?” node, since the first decision has not yet been made.

If you click on the “None” decision of “Do Tests?” to indicate that Joe decides not to do any tests, expected utilities appear in the “Buy It?” node.  The best choice is to buy it, resulting in the highest expected utility – an overall profit of $28.  Try clicking on “First” of the “Do Tests?” nodes, indicating that Joe decides to just get the first test done.  His overall expected utility is 26.2.  Then click indicating that the first test outcome was “Positive”.  The best decision is to buy and the expected utility is 35.  If the first test comes out negative, then the best decision is to not buy, and its expected utility is –9 (which is the cost of the test).  You can experiment with other combinations of findings and decision choices.

Now perhaps you want to create your own decision net?