Added post processing for boxes benchmark

[yaswanth1701]

Test on: Ubuntu 22 and gazebo 11
This is a follow-up PR to #27 and solves #25 . Now instead of calculating error/metric in gazebo api a separate python script has been added. This facilitates simulator-independent metric calculation functionality. The script currently processes the logged data in CSV format for calculations.

Steps to run post-processing with benchmark

cd build
cmake ..
make 
make test

[scpeters]

this looks good, just a few minor comments

also it could be helpful to distinguish more clearly between the two types of csv files we generate:

• the csv converted from mcap for each test case / instance / run
• the csv of postprocessed data for the entire set of tests

[scpeters]

the energy is a scalar, so E0_mag looks like a duplicate of E0 to me (whereas L0 is a Vector3, so L0_mag makes sense)

[yaswanth1701]

also it could be helpful to distinguish more clearly between the two types of csv files we generate:

• the csv converted from mcap for each test case / instance / run
• the csv of postprocessed data for the entire set of tests

Hi Steve sorry for asking again, but are these suggestions regarding the project report or post-processing script? If it is for post-processing, should I consider adding comments and changing the variable naming?

[scpeters]

also it could be helpful to distinguish more clearly between the two types of csv files we generate:

• the csv converted from mcap for each test case / instance / run
• the csv of postprocessed data for the entire set of tests

Hi Steve sorry for asking again, but are these suggestions regarding the project report or post-processing script? If it is for post-processing, should I consider adding comments and changing the variable naming?

I think it can be for both, but more importantly for now is the report

[yaswanth1701]

also it could be helpful to distinguish more clearly between the two types of csv files we generate:

• the csv converted from mcap for each test case / instance / run
• the csv of postprocessed data for the entire set of tests

Hi Steve sorry for asking again, but are these suggestions regarding the project report or post-processing script? If it is for post-processing, should I consider adding comments and changing the variable naming?

I think it can be for both, but more importantly for now is the report

Got it! Thanks

[yaswanth1701]

Hi Steve I just updated the project report can you take a look ?https://gist.github.com/yaswanth1701/d9ac86875046d827d65f6f48963a13c7