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

Problems with Set Derived Script

medini_1059816043

Hallo together,

I try to use the set derived script to set the variables in the architecture to "derived)

If I do it in the library it worked well.

But on the architecture I got a failure:

Why will the script not work in this folder?

What can I do here to set the derived attributes

Thanks

Regards

Markus

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1023909254

Hello Markus,

did you use the script from this article:

https://medini.freshdesk.com/a/forums/topics/1000092817

If not/if it had been modified/adjusted, please upload the script here.

Eckhardt

medini_1059816043

Hallo Eckhardt,

i have downloaded now the script "Set derived variables in blocks".

But I got the same failure:

Thank you

Markus

medini_1023909254

Hi Markus,

well it is not exactly the same error message ;-) - in your first screenshot it says: "Model contains no parts" and in the second it says "Model contains no blocks".

Anyway, the script from https://medini.freshdesk.com/a/forums/topics/1000092817 is working on SysML Types/Blocks - but you seem to call it on an architecture model which does not contain any blocks. In addition, that script also does change the derived flag only for the variable Teta_U.

What do you actually want to achieve? The general way to set the variables to derived would be that you do this manually when defining/adding/modifying the variables at the container level (either you have a single top level container - or sub-system containers like BDR, CAN_Gateway_Brake, CAN_K1939). This is also the place where you would provide values for these variables. So the steps are:

Add/Define the variables of interest at the container and give values to them
Indicate that these variables shall be used in all contained elements (i.e. have them there as derived):
As a final step - in case the variable value shall be taken from a mission profile, set the variable at the container to derived (holds only for Teta_U and DeltaTeta)

Best regards,

Eckhardt

medini_1059816043

Hi Eckhardt,

thanks for information.

What I want to do is the following:

I want to add a mission profile to the project. This worked:

But if I only add the mission profile in this way it will have no influence to the failure rate.

I was of the opinion that I have to activate some parameters and set it to derived.

This was the reason why I have asked for that script.

Or is this the wrong way? How can I see that the mission profile I have added will have any influence to the failure rates.

Thanks

Regards

Markus

medini_1023909254

Hi Markus, that was actually what I wanted to explain with my last message ;-) ... Have a top-level container, add the variables there, push them to all contained elements and finally mark the variable(s) at the top container as derived.

Note, Mission Profiles for SN29500 is something which goes beyond the SN Handbook. In medini we enable this using values for Teta_U and DeltaTeta from the Internal Working Cycles of the MIssion Profile (the data from the working phases in MP is not used!). The take-over is visualized at the instances using a vektor notation and will only take place in case the two variables can not be resolved otherwise.

Eckhardt

medini_1059816043

Hi Echardt,

thanks. I think now it workes. I have now just added the vaiable Teta_U in the Container. Set the checkbox derived (alsoin the container) and the button "use this variable in all children".

Then the failure rate will be changed accordingly.

Just to be sure:

The container inherits the temperatures from the mission profile. and the components below inherit the temperature from the container. Is this correct?

And what do you mean with "date from the working phases is not used"

Which temperature will be taken to calculate the failure rates if I have different temperatures at different phases?

Thanks

Regards

Markus

medini_1023909254

Hi Markus,

in general it should be the opposite order: First " Use ...in all Children" and after that mark the variable at the container as Derived. After that you will observe the following:

At the container it shows like this:

Both variables are derived (indicated by the () ) - and no value is found in the context

At the internal parts it shows like this:

The variables are marked as derived. As no values for them are available in the context AND because the element has a prediction from SN29500,the values from the mission profile are used. Note, if you uncheck the derived at the container, also the contained elements will take over the (default) value from the container.

The usage of the data from MP is as follows:

In fact with SN29500 medini will calculate the failure rate as the weighted average of the Failure Rates from the different Internal Working Cycles.

Eckhardt