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

Moving Comments between DC Worksheets

medini_1064792687

I have a HW model with ca. 2k components that I've developed a FMEDA with a number of entries in the "Comments on this failure" column. I've derived a new HW model off this original and the FMEDA, but my notes are largely lost with the new derived FMEDA. I'd like to programmatically move the notes over. To this end, I've been working with the JS capability.

I am new to scripting with medini, but haven't found anything to help me with this problem. I've gotten to the point that I can obtain the notes from a selected failure mode from the first FMEDA, but I'm not able to see the Failure Mode name or the container that Failure Mode is in.

// select parts
if (selection && selection.length && selection[0] instanceof Metamodel.dc.DCFailureModeEntry) {
	var elements = Global.getFinder(selection).findByType(Metamodel.dc.DCFailureModeEntry); 
	if (elements.isEmpty()) { 
	 console.error("No elements to proceed - bail out"); 
	} 
	console.log("Found {0} elements", elements.size()); 
}
// Iterate over elements
elements.forEach(function reportComment(element) { 
	if (element instanceof Metamodel.dc.DCFailureModeEntry){
		console.log("element: {0}", element.name);
		console.log("comment: {0}", element.user_comment);
		console.log("parent: {0}", element.mediniGetContainer());
	}
});

I figure that I will need this information in order to move the notes to the second FMEDA.

The element name is returned as DCFailureModeEntry and the parent name is returned as DCComponentEntry

I'd like to know:

Why I cannot see the names for the element's name or the parent's name?
Is there an easy way to copy these notes over from one FMEDA to another once?

For question 2 I'm wondering if the approach I'm taking is even worth the effort.

Using 2023.R1

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1023909254

Hi Todd,

in case you have based your project on the BestPracticeTemplate, there is an easy way to achieve the display of all comments - you just have to activate the the property "Comments in all worksheets"

This property will aggregate all comments which you have given for a failure mode in different DC worksheets. Note, you may need to press F5 in order to refresh it.

Let me know if this solves your issue.

Best regards,

Eckhardt

medini_1023909254

... and a small add-on concerning:

I'd like to know:

Why I cannot see the names for the element's name or the parent's name?

element in your Script-snippet is of type DCFailureModeEntry and this type has no attribute name - Javascript is very forgiving and just ignores this. To get the name of the failure mode you need to use

element.element.name - i.e. you navigate from the DCFailureModeEntry to the related failure mode and then to the name. 

(which btw also shows that element may not really a good name for a variable used in a script as you or Javascript may get confused)

Eckhardt 

medini_1064792687

Thanks for the quick reply, Eckhardt.

Enabling comments on all worksheets did not seem to work, despite using the best practices template. I refreshed and closed/open the project again and this is what I'm seeing for the same component in the DC Worksheets (note that this component did not change between models).

Project A (the original)

Project B

medini_1023909254

Hi Todd,

just to make sure - are your DC Worksheets in the same medini model - or (as your naming indicates) in two different medini projects?

Eckhardt

medini_1064792687

Eckhardt,

My keyboard should be disabled until I've had coffee ;-). I had meant Models.

Here is a screenshot with some redactions and name changes to protect the innocent. Hopefully this conveys better than my poor choice of words.

Todd

medini_1023909254

Hi Todd,

no problem - now I understand. And in this case unfortunately the derived property "Comments in all Worksheet" will not work. The reason is that this property is looking for/aggregating comments for failure modes in different DC Sheets which are derived from the same architecture model. In your case you have however multiple (unrelated) architecture models with their own DC Sheets. As there are no relations between the model, the tool can not look-up things.

Basically there are two ways to handle variants of an architecture in DC Sheets:

Build-In solution
Within a single project you have only one architecture model which contains the elements of all variants (e.g. a 150% model). In that case you can have within the DC Sheet the possibility to define Variants and do the evaluation for all variants within the same DC Sheet:

Please check also the user guide at
Ansys medini™ analyze User Guide > Safety Analysis > FMEDA and Diagnostic Coverage Metrics > Analysis of Variants in FMEDA
Using separate medini projects for the individual variants.
In this case after completing the first Architecture/DC Sheet use "Derive new Project" in the context menu of the Model Browser to create a project for the second variant. This will create a full copy of the original project (incl. architecture and DC Sheet). Now you can update/modify the architecture in this new project and afterwards go to the (existing) DC Worksheet and check/review it resp. add further evaluations for new parts.
These two project would be independent from each other but you can bring changes from one project to the other one by Diff/Merge.

Best regards

Eckhardt

medini_1064792687

Thanks, Eckhardt.

I've looked at the DC variant approach, but the difficulty is with producing a sane BOM with hundreds of deltas, some of which include reusing part names (not my choice, but what I'm given). I think the DC variant approach makes sense for minor revisions.

Not a big fan of having to derive a new project when I can create a variant HW model, but I understand the simplicity of it.

This is why I originally had my query - is there a clean way to programmatically copy notes from one DC worksheet to another when the underlying model is different between the two. So I know I can get the notes from one DC Worksheet, now it just a matter of figuring out how to find that same component and failure mode in new DC Worksheet. I'll continue my efforts…

Todd