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

Automativ Sanity Check?

medini_1068027459

Hi,

we just started scripting in medini and have done some basic scripting in js in one of our projects. The script we wrote basically only reads information from the project, so it shouldn't alter it in any way. I've attached it for double checking.

Now, when we run the script "Restructure HW Model" (provided by Medini) on our Model the Sanity Checker throws the error:

'0' target elements for 'Trace'

This does not happen in projects, in which we didn't start srcipting yet. I've looked at the code of the "Restructure HW Model" script and i don't see anything that would tell me, a sanity checker was implemented. Does Medini somehow call the sanity checker automatically? And what does the error mean?

Thank you for your Help!

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Since 23.2 there indeed is a new option to run sanity checks automatically, and I think by default it is enabled for scripting to find problems early enough.

Please check your preferences:

Regards

Jan

All comments

medini_1024169437

Since 23.2 there indeed is a new option to run sanity checks automatically, and I think by default it is enabled for scripting to find problems early enough.

Please check your preferences:

Regards

Jan

medini_1023909254

Hello Lukas,

besides changing the strictness of the Sanity Check as proposed by Jan, It would of course be good to find out why the sanity check is complaining at all. Do you have a small sample project which we could use to find this out?

Eckhardt

medini_1068027459

Update on this situation:
in the example project the restructuring doesn't work. If you pull one of the components out of its group and try to restructure it, so that it ends up back in that group, it won't actually end up there. This probably results in the error message by the sanity checker.

So somehow the script does not, what it's supposed to do here.

medini_1023909254

Hi Lukas,

I actually just had a look on the project and did (without any further action) a Sanity Check. That does reveal quite a number of issues with the DC Sheet:

Moreover, the Cover Page of the DC Sheet does also not look complete - the sections on Safety Goals, Target Values and Variants are missing there completely. So for me it looks like the script is not working due to the issues with the DC Sheet.

Eckhardt

medini_1023909254

One additional remark: As the Sanity Check after Script execution does throw an exception, all changes done by the script are rolled back. So therefor you will not see any changes when components should be moved in a container

Eckhardt

medini_1061274069

Hi I am working with Lukas Geiger,

when performing a consistency check of our project there is 1 error:

The XML code of this error is attached in "Error Log.txt"

However when using the settings for after script execution on min or low, the HW model is correctly restructured.

medini_1061274069

Performing a quick fix (deletion) of this error after consistency check seems so solve the issue also for after script execution on max:

medini_1023909254

Hello Tim,

that is of course a different project -but the error you are having was also showing up in Lukas' project. At the end it looks like tracing of Safety Goals (and additionall usage of Safety Goals in DC Sheets in Lukas' project ). At least in Lukas project there are in fact no safety goals - so I do not know what happened here. Did you manually delete the SG - or perform some Compare&Merge Action? Where are your projects located - on a shared drive/OneDrive or similar managed location?

Eckhardt

medini_1068027459

In my best intentions, i dumbed the project down (manually) to what i believed was the necessary information to solve the problem. This was shortsighted. The problem Tim describes is far more accurate and should be the one adressed.

medini_1023909254

Hi Lukas & Tim,

well, actually when deleting SG from the project in medini, it should point you that the goals are used in the DC Sheet and you first have to un-associate them there. Anyway, can you elaborate more on the questions I had in my previous message "Did you manually delete the SG - or perform some Compare&Merge Action? Where are your projects located - on a shared drive/OneDrive or similar managed location?"

As the project looks at least partially corrupted, it would be good to find the reason

Eckhardt

medini_1068027459

So, i deleted them manually, yes. But this does not seem to be the issue, as the error also showed up in Tims project, where the Safety Goals are there.

We currently manage the projects only on shared drive if no work is done on them. This means, that we import the project from the shared drive to the local default Workspace, perform changes on the project there, and export it again to the shared drive.

Tim provided the xml-output (called "Error Log.txt") from the error, that showed up in his project, above. Might that be of any help?

Regards,

Lukas