I found a solution. I posted it to the File Exchange as linked below. The solution is to use UserData of a block to store the data between runs.
Persistence in Lookup Table Data
3 visualizzazioni (ultimi 30 giorni)
Mostra commenti meno recenti
Jason Nicholson
il 27 Apr 2018
Risposto: Jason Nicholson
il 2 Mag 2018
I load several large multi-dimensional lookup tables in the initialization of a subsystem that has lookup table blocks. The lookup tables are in a library model. When I build a Simulink model from the library, I will have several instances of the library. This means something like ~10-20 large lookup tables. This really seems to slow down the initialization. When I am interactively running the model, I don't care about the extra time. However, I want to call the big model several thousands times in a loop. The biggest cost is the loading the lookup tables and doing a calculation on the lookup tables to reduce them by 1 dimensions that really only needs done the first time the library runs. Is there a clever way for the data to remain persistent from run to run?
- The persistent keyword only works in MATLAB functions. It does not work in Simulink initializations.
- I cannot use the base workspace. I cannot guarantee what will be going on the base workspace because I will share my library.
0 Commenti
Risposta accettata
Più risposte (0)
Vedere anche
Categorie
Scopri di più su Programmatic Model Editing in Help Center e File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!