Re-use script from OSI repo

[jdsika]

I am asking myself, if we should have a script in OSI handling traces and in this repo again? Souldn't we have ONE place that shows how to handle traces and then re-use it?
https://github.com/OpenSimulationInterface/open-simulation-interface/blob/master/format/OSITrace.py

[jdsika]

• Compare read/write methods in OSI and osi-validation
• Improve OSITrace.py class in OSI repo (and examples demonstrating it in osi repo)
• Enable lzma support
• Add test files (different proto versions): 3.0.0, 3.15.x, latest
• Create PR in OSI
• Remove write scripts reading/writing in osi-validation
• Use class from osi repo

see OpenSimulationInterface/open-simulation-interface#758

[jdsika]

It would be nice if the different osi trace formats described iun the documentation do also have script examples along with them.

[jdsika]

@ClemensLinnhoff Protobuffer changed its version schema (OMG). The question: why?
https://github.com/protocolbuffers/protobuf/releases/tag/v25.2

What does that mean for the "on the wire compatibility"? What breaks?

[jdsika]

CMAKE says protobuf 2.6.1: https://github.com/OpenSimulationInterface/open-simulation-interface/blob/master/CMakeLists.txt

[ClemensLinnhoff]

@ClemensLinnhoff Protobuffer changed its version schema (OMG). The question: why? https://github.com/protocolbuffers/protobuf/releases/tag/v25.2

What does that mean for the "on the wire compatibility"? What breaks?

They changed it in v21. It says in the release notes:

• Versioning scheme is changing to decouple major versions for languages
• Minor and patch versions will remain coupled

That means, that it is 3.21.0 for C++ but 4.21.0 for python.

Why you ask? Probably because they don't like the people who have to work with protobuf 😄

[ClemensLinnhoff]

CMAKE says protobuf 2.6.1: https://github.com/OpenSimulationInterface/open-simulation-interface/blob/master/CMakeLists.txt

Well 2.6.1 is now almost 10 years old. Should it be updated in the CMakeLists? Or do we want to support 10 year old trace files?

[ClemensLinnhoff]

@jdsika I have generated some test trace files, e.g. with different protobuf versions. Where would you put them? Should we put them in the open-simulation-interface repo to perform unit tests on OSITrace and the formatting tools? Or should we put them in the osi-validation repo to test the validator?

Of course we could also put them in the open-simulation-interface and use them also for the validator.
And if we put them there, would you put them in the tests folder or in the format folder? Or in a completely separate trace_file_examples folder?