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; } } }

Access to safety goal specific component level SPF

medini_1052680584

Dear ANSYS team,

When working with Evaluation Groups within an FMEDA, and having the checkbox Totals marked, we can see the SPF-Sum within each component, for each safety goal being analysed (see arrow in the attached screenshot).

How can I have access to those numbers within a script?

Furthermore, it would be very helpful to have a column "Component SPF Importancy", where the numbers mentioned above are divided by the component SPF and not by the whole system SPF, as presently.

Thanks!

Cheers, Andre

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1023909254

Hi Andre, thanks for the feedback ... so you colleague may also go to 22R1.1 (and of course any later version) and it will work for him too.

Eckhardt

All comments

medini_1052680584

Hi,

After a tip from Joel and searching further in the forum, I found one possible solution for the problem.

If myDCComponent is a component in the FMEDA then:

myFirstSafetyGoal = myDCComponent.mediniGetContainer().safetyGoal.get(0);

console.log(myDCComponent.getTotalSpfFailureRate(myFirstSafetyGoal));

will print the SPF contribution of that component to the first safety goal define in the DC Worksheet.

Regards, Andre

medini_1024169437

Hello Andre,

so you basically answered your question yourself, nice :-)

Thanks Joel as well.

Jan

medini_1052680584

Dear ANSYS team,

The strategy above does not seem to work in the v2023R1.1.

I get the following error message:

Failed to execute Java Script: class de.ikv.analyze.domain.core.emf.DomainAwareSafetyGoalImpl cannot be cast to class de.ikv.analyze.metamodel.dc.DCMetricsParameters (de.ikv.analyze.domain.core.emf.DomainAwareSafetyGoalImpl is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @79a92277; de.ikv.analyze.metamodel.dc.DCMetricsParameters is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @35217e0)

Can you please help me adapting the code above to the v2023R1.1?

I couldn't deduce the new behaviour from the metamodel document.

Thanks a lot for a feedback!

Cheers, Andre

medini_1023909254

Hello Andre,

due to the introduction of variants besides safety goals a change in the access method was required. In general it would be something like this:

lambda_spf_rs = (goal!=undefined || variant != undefined) ? worksheet.getTotalSpfFailureRate(goal,variant): worksheet.totalSpfFailureRate;

Eckhardt

PS: In the PMHF Approximation Project Script (available on Online Support Page since V 22R1) you may find further details on accessing data in a DC Worksheet.

medini_1052680584

Hi Eckhardt,

Thanks for the fast feedback!

The example you provided is however used to get the total SPF failure rate of the whole worksheet.

My problem is that I want the total SPF failure rate at the component level, that was possible in previous versions.

Afer your feedback I've tried using some things like:

myDCComponent.getTotalSpfFailureRate(myFirstSafetyGoal, undefined);

to send something as variant, but the debugger says the "EOperation does not match arguments".

Thanks for helping!

Regards, Andre

medini_1023909254

Hi Andre,

yes you are right, my proposal did look at the full Worksheet and not at each individual component.

Anyway, I tried to re-create your issue on my side - but for me it seems to work as expected. Can you check once more, which version of medini you are using? I remember we had this issue in 2022 R1 but it had been resolved with 22R1.1.

May be you can try to create a derived (Javascript) profile property for DC Component Entry with the following definition and let me know if that works:

self.getTotalSpfFailureRate(self.mediniGetContainer().safetyGoal.get(0));

Eckhardt

medini_1052680584

Hi Eckhardt,

Thanks for the feedback!

The solution you proposed returned the same error message as in the script.

And indeed, I am debugging this script for a colleague who is using exactly the v2022 R1.
I've just tested the script in the v2023R1 and it works fine.

I will ask him if he can move to the new medini release. We are all intending to do it soon anyway.

Cheers, Andre

medini_1023909254

Hi Andre, thanks for the feedback ... so you colleague may also go to 22R1.1 (and of course any later version) and it will work for him too.

Eckhardt