-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update/validator #48
Update/validator #48
Conversation
@ClemensLinnhoff can you review please? |
Yes, I will review this next week. |
I cannot extract the small_test sample trace file.
|
When running osi-validation with a different trace file, I get the following error:
I am using pip 20.0.2 and python3.8 in venv. |
Please implement a build check for the GitHub CI pipeline. The travis build check does not seem to work. |
The links in the Readme to the documentation do not work. This way, I don't know, which trace file formats are supported. For the .osi trace file:
For the .txth trace file:
|
You write in this PR, to run osi-validation with
However, the --data option is not listed in the README. |
Good point! I will migrate the CI from travis to github workflow. |
Can you try?:
I will commit the decoded trace to the repo to avoid this issue. |
With
|
Ah, instructions for the protoc compiler are missing in the readme |
…s. Used Python 3.8 in workflow. Signed-off-by: Carlo van Driesten <[email protected]>
Signed-off-by: Carlo van Driesten <[email protected]>
Signed-off-by: Carlo van Driesten <[email protected]>
Signed-off-by: Carlo van Driesten <[email protected]>
!!!! setup.py does have a different requirements list then the requirements.txt !!!! |
|
Signed-off-by: ClemensLinnhoff <[email protected]>
@vkresch you have removed lzma encoding but it is still present in the OSI repository: https://github.com/OpenSimulationInterface/open-simulation-interface/blob/master/format/OSITrace.py Update: Please create a ticket in OSI to remove lzma there in the scripts as well |
… Fix requirements Signed-off-by: Carlo van Driesten <[email protected]>
Signed-off-by: Carlo van Driesten <[email protected]>
… instructions Signed-off-by: Carlo van Driesten <[email protected]>
@vkresch my mission was successful. I killed the tests because of the minimum proto version from the OSI repository :)) |
Nice :) this was my concern with the bumping. |
…n in requirements.txt and setup.py Signed-off-by: Carlo van Driesten <[email protected]>
You downloaded a different (unknown) version of the protoc compiler in the ci workflow. I now updated it to be the same as in the osi repository. |
Twitter showing this after my review: |
Thanks for the fix! |
…ump year in license, add git+osi requirement Signed-off-by: Carlo van Driesten <[email protected]>
Signed-off-by: Carlo van Driesten <[email protected]>
@jdsika looks like I do not have permission to merge the PR. I noticed an issue with the parallel run option and fixed it. Please review it again. Thanks! |
Resolves #49
Resolves #46
Resolves #45
Resolves #44
Resolves #43
Resolves #42
Resolves #31
Change Notes:
rules
folder fromrequirements-osi-3
folderHow has it been tested?
I tested the rules with defining the x position range of all moving objects and it gave me validation errors outside this range for the
small_test.txt
. In the test trace there is only one moving object which moves in the positive x direction. To reproduce go intoosi_common.yaml
and change to this:Validation Result:
Mention a member
@jdsika please check the latest update
in terminal you should be able to install with:
$ pip install .
and to run with:
$ osivalidator --data data/small_test.txt --rules rules/
Check the checklist
To Fix
Enable reading human readable trace filesEnable setting a rule to define, if a field is required. Giving a warning for every missing field is not really effective.-> Enable setting a rule to define, if a field is required #51Fix that when a rule is deleted, it is not checked anymore.-> A field removed from the rules is still tested #52Fix logging to correctly differentiate between error and warning analog to test results.-> Fix logging to correctly differentiate between error and warning analog to test results #53