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

Delete the die area at the parent elements

medini_1024120963

If you perform an IPD-XML Import sometimes the source tool does sum up the die are of its children which is not correct and leads to huge total die areas in medini.

In case you have no glue area which is supposed to be described in the parents die area according to the IPD-XML definition. You may simply delete the die area at the parents.

The script below will allow you to delete the die area value at each container element.

Happy scripting!

Best regards

Joël

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1023909254

Hi Joel,

just to be clear:

Your script is "repairing" an IPD architecture model in medini that was created by importing an IPD-XML file which is not compliant to the IPD-XML Definition! Of course the real solution would be that the 3rd Party tool, which is generating the IPD-XML, would produce from the beginning a correct IPD-XML file (i.e. the area information must not aggregate any area information of sub-instances - see Section 3.2.4 point 4 in the IPD-XML definition).
Also note, there are further parameters which should also not be aggregated (e.g. SequentialElementsCount which is the base for the calculation of the transient failure rates)
Currently your script would also delete any area information for components in other architecture models (which are not imported from IPD-XML). Such information are e.g. created by the "Aggregate Failure Rates" command in medini and are base for the subsequent Percentage-of-Parent determination
"kill container die" as the script name sounds very strange ;-)

Eckhardt

medini_1059007410

Hi,

Yes, especially on Eckhardt's point 3.: Please execute the from the context menu of the IPD-XML imported architecture model. In that case only the die areas of the parts in that model are modified.

Regards,

Nils

medini_1023909254

Hi Nils,

yes, that would limit the chance to destroy something. In addition also a check for the typecode could be done:

//...
 if(element.typeCode != "IPD") {
 return false;
 }

 if (element.the_owned_elements.size()==0) { 
 return false; 
 } 
//...

Eckhardt

medini_1024120963

Hi Eckhardt & Nils,

thank you for highlighting that the IPD-XML is not compliant if this script is needed and that it would also delete die area values in other system models.

Therefor please find the evolution of the initial script here, It is now also checking if the SYSML Model is based on an IPD Import.

Furthermore it shall be excecuted from the System Model object in the medini model browser.

PS: Thank you for the valuable hints.

Best regards

Joël

medini_1058747041

Hello together,

I would execute this script on the imported Design Model?

In case I "destroy" something with this script I could update the Design Model with the original IPD XML-file, correct?

Thanks

Lukas

medini_1023909254

Hello Lukas,

yes you should execute it on the imported design model (i.e. the one which is tagged with [IP Design Model]

And yes - as soon as you do an update of the model, everything will be as before.

Eckhardt

medini_1058747041

Hi Eckhardt

ok thanks, shall I use the script "kill_container.." or "delete_container.." ?

Lukas

medini_1024120963

HI Lukas,

delete container is the latest version of the script.

Please use it on the imported IPD_XML SysML model.

Joël