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
Describe the solution you'd like
A clear and concise description of what you want to happen.
The ability to parse(and act on)and create any meta-data, related to a specific SSP or FMU, expressed in the SRMD format of the SSP Traceability specification. Examples of relevant meta-data are: generation date and time, repository tags, OMSimulator version, etc. However, the end user should be able to specify what information to store.
The text was updated successfully, but these errors were encountered:
@arun3688 I am thinking something like the api for the exportSSVTemplate command. Currently there is not a way in SSP to add a reference to the resulting SRMD file, except for through vendor specific annotations, but I believe there will be a solution in SSP 2.0. Maybe that proposal could be used?
Describe the solution you'd like
A clear and concise description of what you want to happen.
The ability to parse(and act on)and create any meta-data, related to a specific SSP or FMU, expressed in the SRMD format of the SSP Traceability specification. Examples of relevant meta-data are: generation date and time, repository tags, OMSimulator version, etc. However, the end user should be able to specify what information to store.
The text was updated successfully, but these errors were encountered: