Simulink Design Verifier taking really long

I am new to using SLDV. Forgive my ignorance in advance.

I am running SLDV on a model with a decent-sized Stateflow chart in it. I'm just using the "Design Error Detection" option with "Run exhaustive analysis". SLDV runs fine and then seems to get stuck on something. It is spending a long time on one objective. By long time I mean 30+ minutes and counting. Wtihout exhaustive analysis, it takes about 15 seconds and recommends I use exhaustive analysis. I set the maximum time to inf to allow it to run as long as it needs. 36 minutes as we speak, and it's still on the same objective.

How can I tell what branch in my logic is causing the delay?

Thanks in advance!

[Pat Canny]

Hi @John Fiaschetti,

No forgiveness required - happy to help!

A few questions and a suggestion:

1. Which checks did you enable? Dead logic? Out of bound array access? (All?)
2. How many objectives were being analyzed? (This should show up under the Progress bar in the window that launches during analysis). Did SLDV make it through most of the objectives before getting stuck?
3. Does the model include any timers? A common example in Stateflow is the use of after() in a transition.
4. Try stopping the analysis and generating results. Even if you stop the tool during analysis, you can still see what was analyzed. This won't guarantee it will be obvious where the tool got stuck, but it may help.

Do you have a point of contact here at MathWorks - maybe someone from our Application Engineering team?

@Pat Canny

Simulink Design Verifier Product Manager

[John Fiaschetti]

Thanks for the reply!

1. I enabled dead logic and exhaustive analysis. Nothing else.
2. In the case of the ultra long test, I had 165 objectives, and it seemed to trip at 57 completed.
3. The offending model does have a couple "after" statements. We don't use absolute time. So, the afters are in "ticks". For exmaple, I have an "after(320,ticks)" on one transition.
4. I did stop it several times to look at what was analyzed. I do not see a way to tell which transition is bogging it down or why that transition is causing that behavior.

For this particualr problem, I do not have a particular AE. I have often worked with Jon Lobo in the past. I try to use help or tech support before going to him.

[Pat Canny]

Hi @John Fiaschetti,

Ah - thanks.

I reached out to some folks you've worked with - is it OK if we reach out to you directly over e-mail?

Thanks.

@Pat Canny

[John Fiaschetti]

Absolutely!

[Pat Canny]

Great! Let me do a little digging internally, then we'll reach out. Expect something in your inbox today, though.

I have a sense it's those timers (the after() statements) that are the issue, but I have a question in to our Development team to clarify something first.

[Adam Duvick]

Hey, Pat. I have a team using Simulink Design Verifier to generate test cases for an execution group of about 80 models. The task is running on a high performance PC, but is still taking about 80 hours to run. Is this normal? My team is wondering if there if there is anything on our configuration that is making the task take longer than is needed.

I am new to this tool myself, so if there is any information that I should provide, please let me know!

Thank you!

[Sobia]

Hi, I am also facing the same issue I am using SLDV test generation and total 321 objectives are to be analyzed out of which 121 objectives are not progressing even after 2 hours time. Kindly let me know what could be the possible reasons for this long run time issue.

Any help is appreciated.

Thanks

Answer 1

[Pat Canny]

I recommend contacting MathWorks Technical Support. This question requires more information.