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
{{ message }}
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.
Reported by maplesoft on 30 Jan 2017 14:16 UTC
A number of exported FMUs contain data for local variables in the reference files. Since these local variables are internal to the FMU and are listed under 'protected' section during Import, the importing tools may not allow access to such variables including for the purposes of plotting. We propose that the local variables should not be included in the reference CSV files, only outputs and states.
Comment by karl.wernersson on 15 Jun 2017 14:31 UTC
As the compliance checker as far as I know don't support support picking which variables to store besides output or all, it might be even better to restrict to only outputs if we are going to restrict it.
Reported by maplesoft on 30 Jan 2017 14:16 UTC
A number of exported FMUs contain data for local variables in the reference files. Since these local variables are internal to the FMU and are listed under 'protected' section during Import, the importing tools may not allow access to such variables including for the purposes of plotting. We propose that the local variables should not be included in the reference CSV files, only outputs and states.
Migrated-From: https://trac.fmi-standard.org/ticket/408
The text was updated successfully, but these errors were encountered: