If you are running a DPL model that is relatively large and is linked to an Excel spreadsheet that is also relatively large, you can save time by recording and playing endpoints. Playing endpoints works whenever DPL can re-use the Endpoint Database to generate results. The Endpoint Database stores all the value model information that is needed to roll-back the Decision Tree. Typically, calculating this value model information (particularly if this information comes from an Excel spreadsheet that needs to be re-calculated) is the most time consuming part of a DPL run. When you play endpoints, DPL only needs to look up values rather than recalculate them which results in much quicker runtime.
When you select Full Tree Enumeration from Endpoints (also referred to as "Playing Endpoints") evaluation method from the Home | Run | Decision Analysis drop-down list, DPL analyzes the model by using the previously recorded Endpoint Database and produces the outputs selected on the ribbon. This evaluation method is only available if endpoints were recorded previously for the model. You can play endpoints after changing your model as long as the recorded endpoints "cover" all the scenarios. You can change probabilities, set events using Branch Control, reorder the tree, etc. You may be able to add events if they do not directly change your value model, e.g., if they probabilistically condition another event in the model. You can not add states to events since this would add "new" endpoints to the value model. If you try to play endpoints and there are scenarios not included in the endpoint database, you will get the error "endpoint not found".
Policy outputs
When you generate a Policy Tree by playing endpoints, it will not show any get/pay values. Only the endpoint values (values at the end of the tree, the sum of all get/pays on that path) are used when playing endpoints.
Versions: DPL Professional, DPL Enterprise, DPL Portfolio
See Also