You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The modular approach of the ebus toolbox can often fail, if a single modul fails/ throws an exception. This can happen especially in fast developing environments like ours, e.g. incompatible version of spice ev<--> ebus toolbox. In my opinion modules, e.g. cost_calculation, should take care of catching errors on a macro scale to allow simulations to finish even if the single module fails. Warnings should be printed accordingly.
The text was updated successfully, but these errors were encountered:
The modular approach of the ebus toolbox can often fail, if a single modul fails/ throws an exception. This can happen especially in fast developing environments like ours, e.g. incompatible version of spice ev<--> ebus toolbox. In my opinion modules, e.g. cost_calculation, should take care of catching errors on a macro scale to allow simulations to finish even if the single module fails. Warnings should be printed accordingly.
The text was updated successfully, but these errors were encountered: