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

Using Profile Property under Element prediction variables

medini_1039539557

Hi,

We would like to have a Raw Failure Rate function which takes into account an Element profile property.

Is there Any way to access the profile property from the Variables under Prediction Tab? and how can we use it to be a function of the Raw Failure Rate of the element? should we use Scaling ?

e.g. Element.RawFailureRate = Element.GateCount * 0.002FIT;

Thanks in advance,

Best regards,

Alon

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Ok, I was quicker than expected, reusing some existing scripts.

Attached you will find a sample project that was derived from the Microcontroller example. It contains a script "Update IP Variables" that is mapping an arbitrary number of attributes (e.g. IPD profile properties) to variables based on selected elements or a root package (recursion).

In line 17 you find the mapping to customize, currently it maps two IPD properties.

/*
 * This maps from any attribute (native or profile) to a variable.
 * But remember: variables can only contain numeric values so far!
 */
var mappings = {
	"ipd_cellCount" : "CellCount",
	"ipd_area" : "DieArea",
};

Please post any feedback and updates here

Happy Scripting

Jan

All comments

medini_1024169437

Alon,

I think the original threat proposed to write a script that transforms the profile property (gate count) into a variable. Reason is that only variables can be taken into account for custom scaling formulas.

So before moving forward, lets clarify whether that solution is clear on you end.

The script would have to be executed *always* before computing the failure rates.

Happy Scripting

Jan

medini_1039539557

Hi Jan, Thank you. This solution is acceptable.

How can we proceed?

medini_1024169437

Well, I could prepare and post a skeleton script that handles the main things like variable lookup, creation of the variable if not present etc.

You have to take it and adapt to your needs, e.g. variable name, profile property name etc.

Sounds like a plan?

Jan

medini_1039539557

Great! looking forward. Thanks!

medini_1024169437

Ok, I was quicker than expected, reusing some existing scripts.

In line 17 you find the mapping to customize, currently it maps two IPD properties.

/*
 * This maps from any attribute (native or profile) to a variable.
 * But remember: variables can only contain numeric values so far!
 */
var mappings = {
	"ipd_cellCount" : "CellCount",
	"ipd_area" : "DieArea",
};

Please post any feedback and updates here

Happy Scripting

Jan

medini_1039539557

Awesome! It looks good and working. nice solution!

Thanks a lot.

medini_1024169437

Glad it does, please mark as "answered" if you can

Jan

medini_1077257242

Good morning,

I would like to import variables from Excel into the profiling section, and then from profiling into the Element Prediction Variables.

Using the mapping, I’m able to correctly bring the values into the profiling section, but when I use this script in Variable Prediction, it only creates the variables without assigning the values.

Could you please help me?

The version of Medini I’m using is 3023 R1.

Thank you.

medini_1024169437

Hi Magri,

I <?WORD FLAGGED?> dthe script and it still works in my place. So could you check the output in the scripting console?

I get this for example:

Updating i_spi...
Updating variable 'CellCount' to 'null' (read from 'ipd_cellCount')...
Updating variable 'DieArea' to '56.5500' (read from 'ipd_area')...

My Note that the script assumes that your model elements has IPD profile properties. If you have no such properties or have changed the mapping to other variables that do not exist, the script does not check that at the moment. It simply accesses the value with "element[propertyName]". You may want to do some checks before like "if (!(propertyName in element))" or "if (element[propertyName] == null").

Happy Scripting

Jan

medini_1024169437

Another thing: now I saw your lower screenshot, it shows the "Display name" of the attribute but internally in the script, you must use the technical name, so in case you have a property c2 with display name C2 you must use "c2" in the script.

Jan

medini_1077257242

Thanks Jan, i solved my problem.
You can close the ticket.

Bye

medini_1056584416

Thanks Jan!
I wanted to add that I recently helped Paolo with this script. As you said, understanding the mapping at the beginning is key.

Here are a few additional points on my side:

the script works on a single element/element type, or a whole model/library,
it currently focuses on user-defined variables from the prediction formula, but it can be easily extended to search also default variables (those loaded from the catalog). This must be done carefully to avoid corrupting a library or model. To do this, you would add another research between all variables (<em>element.failureRateData.variables</em>) before the one that start from line #70 of the original script that focus instead only on user variables (element.failureRateData.userVariables). In both cases, if you are trying to set a variable that doesn't exist, then the script will automatically create a new user variable.

Michele

medini_1024169437

Cool, thanks Michele for contribution.

Jan