nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Update System Model Derived Variants via traces

medini_1068027459

I'd like to create a script, where i select a system model and update the derived variants of it (NOTE: i'm not talking about FMEDA variants). The update should adress all changes related to failure rate calculation.

My idea is to use the traces (Kind: COPYTRACE), that are created, when the system model variant is derived as a way to identify all elements that should be updated.

I have two hurdles for now:

1. i don't know, how to query the traces based on a particular element and i can't find the traces in the attributes (Diagnose->What is this?).

2. I don't see a way for a script to differentiate between the original and the variant, because basically both are standalone system models, but i'd like the script only to work on the original, so that a reverse update is not possible.

I hope someone can help me out with this.

Thanks in Advance!

Regards

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1059007410

Hi Lukas,

1. The traces are not stored in a property, as they are saved in a central place for the whole project. To access them, please use mediniGetTracedElements(), as described in the help (and in several forum entries):
Ansys medini™ analyze Scripting and API Documentation > Object Model > Default Operations

2. The traces themselves do not have a logical direction, so cannot be used to identify the source/variant.

One way is to check for the eAnnotations of the variant model or its elements (with "source"="synchronizationInformation"). The source model does not have such eAnnotation.

Another way is to check in your script for the name (naming rules required) or you add a profile property (e.g. boolean) to identify the source model.

I hope that helps for your next steps.

Regards,

Nils

medini_1068027459

Hi Nils,

thanks for the quick reply.

So incorporating your suggestions, i would

1. check the selection of the model, whether it has the eAnnotations source ("source"="synchronizationInformation")

2. loop thorugh the model elements and use mediniGetTracedElements() to find the traced elements ("variant elements")

3. maybe double check if the unique identifier matches up

4. update the "variant elements"

Please correct me if i'm approaching this the wrong way, otherwise i will try this and post an update here.

Regards,

Lukas

medini_1059007410

Hi Lukas,

Yes, sounds like a viable plan. Looking forward to the outcome :-)

Regards,

Nils

medini_1068027459

I finally came around to it.

I created a script that allows me to do the above, but in a slightly different manner than planned. The differences were:

- i didn't use the eAnnotation "synchronizationInformation" but only checked, whether only the eAnnotation "baseline_file" was there and nothing else

- some double checks

- i originally did not update the derived property of the variables, which i subsequently fixed

i've attached the script.

Regards,

Lukas

medini_1059007410

Hi Lukas,

Great that you found a viable way and it works for you. Thanks for sharing the script!

Regards,

Nils

medini_1068027459

Hi,

i have one additional question.

The script i've posted above assumes, that the part i'm trying to update already has the property failureRateData. However if this is not the case, then this property first has to be created in order to be able to create a variable. I've tried to create "failureRateData", if its needed and not there, but i seem to have done something wrong here, maybe regarding the scope.

I've done the following:

if(tracedParts[n].failureRateData == null){
					Factory.createElement(tracedParts[n], Metamodel.failureratecatalogs.FailureRateData);
}

And get the following error:

"Failed to execute Java Script: Changing container/containment is not allowed in this script (%ProjectDirectory%\config\scripts\.lib\factory.js#1382)"

What am i doing wrong here?

Regards,

Lukas

medini_1059007410

Hi Lukas,

I guess you are missing a pragma, at least $ENHANCED_CONTAINMENT_ACCESS$. The factory does move a "decision" sub-element as part of the FRD creation, and moving elements is not allowed, only with that pragma. See also the "Test Factory.js" pragmas.

Regards,

Nils