Matching simulation comparison tool

[taylanisikdemir]

What changed?
Adding a new tool which runs all the matching simulation configs, parses their result and generates a CSV file.
Example: https://gist.github.com/taylanisikdemir/b039e6156289e4ccf76121c33cb845ba

Note: Each simulation run spits a txt file containing oneline and multiline measurements that are generated from the json formatted event logs using jq/awk etc. Parsing those outputs required some regex magic. Alternative is to load all the event logs into a sqlite table and then run queries on top instead of parsing outputs of jq in this tool. I will look into this option soon.

Why?
Without such tool, it's hard to compare simulation results.

How did you test it?
Run all the scenarios and compare:

go run tools/matchingsimulationcomparison/*.go --out simulation_comparison.csv

If you have already run some scenarios before and made changes in the output/comparison then run in Compare mode

go run tools/matchingsimulationcomparison/*.go --out simulation_comparison.csv \
    --ts 2024-09-12-18-16-44 \
    --mode Compare

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.10%. Comparing base (04add2d) to head (bb71f22).
Report is 5 commits behind head on master.

Additional details and impacted files

see 7 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 04add2d...bb71f22. Read the comment docs.