Hi @collin ,
welcome to the TBP community! I’m happy to read that you have looked through a lot of our resources and are interested in contributing to the project 
It sounds like you have a great background to be able to help us with some of our current issues!
I would say the biggest pain point we have right now that matches what you are interested in is the 3D simulator. Our current simulator (HabitatSim) is coupled to an old Python version and is forcing us to use GPU instances even though all of Monty’s operations are good to parallelize across CPUs. It also doesn’t run on Windows, which makes it hard for Windows users to run some of our benchmark experiments, unit tests, and tutorials (even though Monty code itself does not depend on Windows)
@tslominski wrote out a nice post about this here The Next Monty 3D Environment Simulator
If we could have an alternative simulator integrated in the Monty code base (like Mujoco) it would solve several of our current issues.
GPU acceleration for Monty is interesting, however, we haven’t prioritized it as much so far, as Monty can be run in a parallelized way, eliminating the need for GPUs. Being able to run it on CPUs only has some nice practical advantages. However, we are transitioning to running some of our experiments on GPU instances now (because of the Habitat simulator issues on CPUs) so if you have ideas for making the most of those GPUs by also having Monty make better use of them those are certainly welcome contributions as well. However, we would like to avoid a strict dependency on GPUs.
I’m happy to give more details on either one of those topics although @tslominski is probably the best person to comment more.
Best wishes and looking forward to hearing more from you,
Viviane