Filter löschen
Filter löschen

Info

Diese Frage ist geschlossen. Öffnen Sie sie erneut, um sie zu bearbeiten oder zu beantworten.

Simulation difference between r2007b and r2012b

1 Ansicht (letzte 30 Tage)
Matthieu
Matthieu am 30 Nov. 2012
Geschlossen: MATLAB Answer Bot am 20 Aug. 2021
Hello,
i recently received a new licence for r2012b and i am using simulink models that were developped and used with r2007b.
In particular i have a problem with a small function (which calculates a sliding average when activated and with an external sample number) that we developped using an 'Enable Subsystem' and 'SwitchCases' and Switchcase Action subsystems --> Even if the parameters and models are exactly the same, the outputs of r2007b and r2012b are definitely not the same.
My questions: - is there any known problem due to import in r2012b of r2007b models? - were there any changes in the definition of these blocks and their parameters?
Thanks!
Matthieu
  1 Kommentar
Kaustubha Govind
Kaustubha Govind am 30 Nov. 2012
Matthieu: It might help if you explain how they're different. Is the different of the order of 1e-5 for instance, or significantly different?

Antworten (2)

Andreas Goser
Andreas Goser am 30 Nov. 2012
I have worked on a couple of occasions with the similar symptoms. It is very diffcult to resolve without having the model, whoch is why I recommend contacting Technical Support. This is what root causes I have found in different cases:
  • Difference was caused by different computer architectures (32/64 bit) and there a good numerical reasons why this can happen
  • Difference was caused by different c compilers in cases where e.g Simulink Accelerator was used
  • Difference was caused by different processor manufacturers and their respective BLAS library
  • Difference was caused by a change of a default option of a MATLAB command that was called

Matthieu
Matthieu am 30 Nov. 2012
Thank you for your comment/message.
I just solve the problem (finally!), much easier than what you actually describe Andreas: the parameters of one output port has changed, don't know if it was because of the version change or an unfortunate "set_param" during a previous update... Instead of being reset to 0, the ouput value of an enabled subsystem is held. Hard to find when you have 250 such subsystems! One day lost for such a stupid thing, aarrrrgggg.
Sorry... and thank you for your answers!

Diese Frage ist geschlossen.

Produkte

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by