Free cookie consent management tool by TermsFeed Policy Generator

Changes between Initial Version and Version 1 of Ticket #2997


Ignore:
Timestamp:
03/19/19 12:48:10 (7 years ago)
Author:
rhanghof
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2997

    • Property Component changed from Problems.DataAnalysis.Symbolic to Encodings.SymbolicExpressionTreeEncoding

  • Ticket #2997 – Description

    initial v1  
    1 When using multi encoding in combination with several symbolic expression trees, only the grammar of the first used symbolic expression tree is used to generate syntax trees. The grammar for creating the syntax trees is stored in the Global Scope and cloned from the grammar of the first syntax tree in the encoding when first used. The setting of the cloned grammar in the global scope can be found in the method ''InstrumentedApply'' of the class ''MultiSymbolicDataAnalysisExpressionCreator''.
     1When using multi encoding in combination with several symbolic expression trees, only the grammar of the first used symbolic expression tree is used to generate syntax trees. The grammar for creating the syntax trees is stored in the Global Scope and cloned from the grammar of the first syntax tree in the encoding when first used. The setting of the cloned grammar in the global scope can be found in the method ''InstrumentedApply'' of the class ''SymbolicExpressionTreeCreator''.
    22[[BR]]
    33Due to the query ''if (ClonedSymbolicExpressionTreeGrammarParameter.ActualValue == null)'' it is only set the very first time. Thus it is not possible to set the grammar for another symbolic expression tree.