Search tips

apple banana
Find rows that contain at least one of the two words.

+apple +juice
Find rows that contain both words.

+apple macintosh
Find rows that contain the word 'apple', but rank rows higher if they also contain 'macintosh'.

+apple -macintosh
Find rows that contain the word 'apple' but not 'macintosh'.

+apple ~macintosh
Find rows that contain the word 'apple', but if the row also contains the word 'macintosh', rate it lower than if row does not. This is "softer" than a search for '+apple -macintosh', for which the presence of 'macintosh' causes the row not to be returned at all.

+apple +(>turnover >strudel)
Find rows that contain the words 'apple' and 'turnover', or 'apple' and 'strudel' (in any order), but rank 'apple turnover' higher than 'apple strudel'.

Find rows that contain words such as 'apple', 'apples', 'applesauce', or 'applet'.

"some words"
Find rows that contain the exact phrase 'some words' (for example, rows that contain 'some words of wisdom' but not "some noise words").

By continuing to use this site you agree to the use of cookies. For more information and to find out how to change this click here. Accept Cookies
Please enable cookies in your browser for this website.
Advanced search

Postbuild-Selectable Projects: Error Message Caused by Conflicting CompuMethods in the Input ARXML Files

Last updated: 2019-02-12

If there are different compuMethods for a SystemSignal in the Input files and it is a Postbuild-Selectable project, this error may occur:

[Warning] Two CompuScales from "/VariantDefinition/Criterion/Communication == 0" and "/VariantDefinition/Criterion/Communication == 1" are simply merged if they share the same index in their respective lists of siblings. If this behavior is undesired <MERGE-BY-FEATURES> can be used in the merge configuration for "/VariantDefinition/Criterion/Communication == 1" to identify elements of that type by a combination of feature values.
[Error] Merge conflict in containment "compuMethod" at SwDataDefPropsConditional below SystemSignal "<Asr path of SystemSignal>". Post-build variance is not supported at this place. The conflict should be resolved by aligning the input data of "/VariantDefinition/Criterion/Communication == 1" to match the content of the other variants. As a temporary alternative, any of the following entries in the merger configuration file could work around the problem: Use <IGNORE-DIFF metaClass="SwDataDefPropsConditional" feature="compuMethod"/> in the <MERGE> section to ignore all differences in that feature. Use <POSTFIX-ON-NAME-CLASH metaClass="SystemSignal" postfix="_/VariantDefinition/Criterion/Communication_==_1"/> in the <MERGE> section to resolve the short name clash for all elements of that type. Use <MOVE from="<Asr path of SystemSignal>" to="<Asr path of SystemSignal>/VariantDefinition/Criterion/Communication_==_1"> in the <PRE-PROCESSING> section to resolve the short name clash for this element. Use <DISCARD-EXPLICITLY element="<Asr path of SystemSignal>"/> in the <PRE-PROCESSING> section to exclude the element from the merge.

Recommended Solution:

adaption of the input files

Workaround: extend the file SystemDescriptionMergConfig.xml with these lines
<IGNORE-DIFF metaClass="SwDataDefPropsConditional" feature="compuMethod"/>
<IGNORE-DIFF metaClass="SwDataDefPropsConditional" feature="unit"/>

Article Options
Views: 647