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
Is your feature request related to a problem? Please describe.
The current implementation has different input file parameter names. E.g. XodrFile or XoscFile. One of the base requirement is that the whole framework is standard agnostic. And e.g. the report GUI needs to show the input file. With different parameter names, the report GUI needs to know about the different standards, what we do not want.
Describe the solution you'd like
Unified parameter InputFile as parameter for the checker bundles.
This is already documented in the current architecture documentation.
Additional context
There is also a discussion about addition files, which will be necessary to access/handled during the check of an input file. An example is the XODR file when checking an OpenSCENARIO XML file. This may be later added as parameter in the configuration. But this topic is not part of this issue. See #117
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The current implementation has different input file parameter names. E.g.
XodrFile
orXoscFile
. One of the base requirement is that the whole framework is standard agnostic. And e.g. the report GUI needs to show the input file. With different parameter names, the report GUI needs to know about the different standards, what we do not want.Describe the solution you'd like
Unified parameter
InputFile
as parameter for the checker bundles.This is already documented in the current architecture documentation.
Additional context
There is also a discussion about addition files, which will be necessary to access/handled during the check of an input file. An example is the XODR file when checking an OpenSCENARIO XML file. This may be later added as parameter in the configuration. But this topic is not part of this issue. See #117
The text was updated successfully, but these errors were encountered: