Difference between revisions of "Analytica Release Notes/Changes in Patch Build 4.4.3"

Line 11: Line 11:
 
** Many models load much faster, especially if you have [[Proactive Evaluation|<code>ProactivelyEvaluate Index : 0</code>]] set.
 
** Many models load much faster, especially if you have [[Proactive Evaluation|<code>ProactivelyEvaluate Index : 0</code>]] set.
 
** Table indexes are evaluated later when you view or evaluate a table.  Thus, evaluation time is shifted from load time to evaluation time (you can still force the evaluation of selected variables or indexes at load time by configuring [[Proactive Evaluation]] if you want).
 
** Table indexes are evaluated later when you view or evaluate a table.  Thus, evaluation time is shifted from load time to evaluation time (you can still force the evaluation of selected variables or indexes at load time by configuring [[Proactive Evaluation]] if you want).
** When you view an edit table for the first time, the table index might need to be evaluated (particularly if they are computed indexes).  So you may experience delays or evaluation error messages when you attempt to view an edit table.  These would have happened before when you parsed the definition.
+
** When you view an edit table for the first time, the table index might need to be evaluated (particularly if they are computed indexes).  So you may experience delays or evaluation error messages when you attempt to view an edit table.  These would have happened at an earlier point in 4.4.2, when you first parsed the definition.
 
** If a table index has an evaluation error, or is not a valid index (i.e., not a list), the variable with the table is now considered parsed, while formerly it would be cross-hatched, meaning it was considered unparsed.
 
** If a table index has an evaluation error, or is not a valid index (i.e., not a list), the variable with the table is now considered parsed, while formerly it would be cross-hatched, meaning it was considered unparsed.
  

Revision as of 18:23, 27 July 2012

<< What's new in Analytica 4.4

This page is under construction

This page lists changes that have been incorporated into the 4.4.3 patch release since the 4.4.2 patch release. In pages like What's new in Analytica 4.4?, we usually only list enhancements, not small bug fixes like the ones listed here. But because this is a patch release, and its only purpose is to provide fixes to lots of small bugs, we list them here.

File Saving and Loading

  • When variables with table definitions (Table, DetermTable, ProbTable and IntraTable) are first parsed (during the Checking phase of the model load), the parser no longer has to evaluate the table indexes. This has several consequences:
    • The parsing and evaluation phases are more distinct, rather than intertwined.
    • Many models load much faster, especially if you have ProactivelyEvaluate Index : 0 set.
    • Table indexes are evaluated later when you view or evaluate a table. Thus, evaluation time is shifted from load time to evaluation time (you can still force the evaluation of selected variables or indexes at load time by configuring Proactive Evaluation if you want).
    • When you view an edit table for the first time, the table index might need to be evaluated (particularly if they are computed indexes). So you may experience delays or evaluation error messages when you attempt to view an edit table. These would have happened at an earlier point in 4.4.2, when you first parsed the definition.
    • If a table index has an evaluation error, or is not a valid index (i.e., not a list), the variable with the table is now considered parsed, while formerly it would be cross-hatched, meaning it was considered unparsed.
  • When a Dynamic with a non-Time dynamic index is parsed (such as Dynamic[I](1,self[I-1]*1.2)), the dynamic index is no longer evaluated at parse time. Consequences:
    • Better separation between parsing and evaluation.
    • Faster load times, since the dynamic index isn't computed at parse time.
    • Dynamic[I](...) variables are considered parsed even when I is undefined or has an evaluation error. Previously, these would appear hatched (unparsed).
  • File saving is been made more robust to a wide variety of disk failures that might occur while saving a model file, reducing the changes of losing information as a result of disk or network failure/outage, disk full, media defects, etc.

Evaluation and Built-in Functions

Influence Diagrams

Tables

Graphing

User Interface

Example Models and Libraries

Typescript

ADE

  • Increased the stack size in ADE to be the same as Analytica. Because of a smaller stack, some deeply nested computations that succeeded in Analytica experienced a stack overflow in ADE.
Comments


You are not allowed to post comments.