Jack Xu

Latest gtsam requires Pangolin from Cmakelist response. You can build [Pangolin from source](https://github.com/stevenlovegrove/Pangolin), but Pangolin has some minor issue, fixed in https://github.com/stevenlovegrove/Pangolin/pull/792

[Tip] Since there is no one maintaining the merge, If you are building from source, you can just modify the other two cpp files from this branch.

It seems there is a branch contain this fix: https://github.com/MIT-SPARK/Kimera-VIO/compare/master...feature/hydra

According to https://github.com/MIT-SPARK/Kimera-VIO/pull/187, gtsam version commit: `e5866799dff48239573cdd84964180867e50edd2`

> Hi, can you elaborate on what exactly I need to do in step 2.2(modify Kimera-VIO to match latest GTSAM [TODO])? just replace functions whatever the compiler has thrown error...

> Hi @jaku-jaku I took a brief look at your changes, I think some of the general use functionalities could've be merged here too :) Yeah, but I kinda refactored...

> When i run the sh file it brings the error: running build_ext building 'mujoco_py.cymj' extension > ... > Can someone help? Make sure to install MuJoCo 2.1.x (NOT 2.2.x...

I believe mujoco-py only works with 2.1.x. MuJoCo 2.2.x comes with m1 release support https://github.com/deepmind/mujoco/releases/tag/2.2.1 And MuJoCo 2.2.x comes with native Python bindings officially, so you may refer to migration...

@natolambert > A lot of RL repositories still include mujoco_py as a dependency, so people are going to be dealing with this for years to come. Though I totally agree...

> I updated [my instruction above](https://github.com/openai/mujoco-py/issues/662#issuecomment-996081734) to catch up with the recent Mujoco [v2.2.0 release](https://github.com/deepmind/mujoco/releases/tag/2.2.0). Summary of changes are: > > * Added an instruction to remove previous mujoco-py extensions...