| DPL 6.0 CHANGES |
This page lists the main changes made in product updates to DPL 6.0. The updates themselves can be
found on the downloads page.
Issues resolved in DPL 6.03.08
- A compile error occurs when both initialization and calculation links are used with a discrete named distribution chance node
- "Probabilities do not total 1.0" may occur because of rounding when the probability for the last branch is zero (whether or not it is specified)
- The value 65535 is sent to Excel when the values of a linked chance node are strings
Issues resolved in DPL 6.03.07
- DPL may hang when compiling a model linked to a spreadsheet when another application erroneously responds to DDE_INITITATE
Issues resolved in DPL 6.03.06
- DPL allows you to create an invalid blank value of info/control chart for a model which contains decision nodes but no chance nodes
- Init links require too many initializers with discrete named distributions
- The colored arrowheads (arcs) setting may not be respected (so that arcs with conditioning are drawn black) in a new model
Issues resolved in DPL 6.03.05
- When decision tree node name underlining is turned off in the Edit Text dialog, Node Definition turns it back on
- Branches of asymmetrically placed decision tree nodes may be in an odd order after snap to grid
Issues resolved in DPL 6.03.04
- Grid settings are reset to defaults when analytical results are cleared
- Activation changes to alleviate some firewall/connection problems
Issues resolved in DPL 6.03.03
- An influence diagram node may unexpectedly move to the location of another node when Node Definition edits are cancelled
- One-way rainbows may be incorrectly labelled as two-way rainbows
- DPL may terminate unexpectedly on certain invalid floating point operations
Issues resolved in DPL 6.03.02
- A linked spreadsheet is not automatically opened when there are initialization links but no calculation links
- DPL may hang after encountering an unusually long OLE error message
- Crash occurs when running Monte Carlo simulation with certain model structures
- Various demo version documentation and activation changes
Issues resolved in DPL 6.03.01
- Decision analysis results for Excel-linked models in which constant export nodes have different data than the corresponding spreadsheet cells may differ when multiple decision analysis runs are made
- For certain model structures, results may reflect incorrect probabilities (of 0.0 and 1.0) when a decision analysis run follows a Base Case tornado run without a recompile
- Flyovers may appear when dragging decision tree nodes
- Various demo version activation changes
Issues resolved in DPL 6.03.00
- Create program from model will fail if the model contains a get/pay expression that exceeds 1024 characters
- An error may not be issued when a continuous chance node is omitted from the decision tree but its value is used in a get/pay expression
- A risk profile chart window displaying initial decision alternatives may not be reconnected when the project file is reloaded
- Overriding the x-asis does not work with output scaling
- Text selected in the decision tree may not be redrawn when clicking in the influence diagram window (and vice versa)
Issues resolved in DPL 6.02.04
- "Expected right parenthesis" message may occur when opening an Excel-linked project file from Windows Explorer
- "Expected left brace" message may occur when a model uses initialization links and default probabilities
- DPL may hang displaying a blank policy tree window after a spreadsheet linked decision analysis run
- A blank window is created when a base case tornado is requested for a model in which all chance event instances are controlled
- Minimize objective setting is not preserved when a model is duplicated
- Perform subtree labels are light green (discrete chance node color) for continuous chance nodes
- Edits to the spreadsheet path in the Model Links dialog affect the first linked spreadsheet rather than the selected one
- Drag and drop get/pay expressions are not converted to variable names (spaces replaced with underscores, etc.)
- Some items (e.g., statenames, get/pays) may be drawn in the Policy Tree even though they are not checked in Format|Display
- Decision tree node names may be of inconsistent font sizes
Issues resolved in DPL 6.02.03
- Time series percentiles may hang
- A compile error occurs when initialization links are removed from a named distribution chance node
- Branches may not be redrawn after get/pay edit
- Crash occurs if Model Links is selected immediately after adding a new model to a project
Issues resolved in DPL 6.02.02
- Zero may be included in the X-axis scale of event tornado diagrams even though all values are strictly positive/negative
- Save prompt may not occur when exiting DPL after moving an influence diagram node
- Constant named cells without successors may be incorrectly described as formulas in the cell names dialog
- Online help updates
- Update to the DTD file describing VOIC charts
- Improved activation error reporting
Issues resolved in DPL 6.01.01
- Time series percentiles may run in full enumeration mode even though discrete tree simulation was selected
- Base case tornado runs may fail with certain asymmetric tree structures
- State names are truncated when they exceed 1024 bytes in length (in graphic models)
Issues resolved in DPL 6.01.00
- Conjoint appears in tools menu (even when not available)
- Export of base case tornado data may fail when the model has no decisions
- Other output may disappear from the project manager when the project contains no driver model or program
- Requesting time series percentiles can lead to a crash when the model contains both discrete and continuous chance nodes
- X-axis may not be visible in time series percentiles chart
- Crash may occur when strategy table decisions are reordered
- Direct printing of node data from the node definition dialog results in undesired cropping
- Remove in Model Links dialog may not remove all node links
Syncopation provides this information to help you determine if a problem you are experiencing has
been fixed in a product update. While we believe this information is correct, we cannot guarantee
its accuracy or completeness.
Contact support if you have any questions.
|
|
|
