@TaoCTakahashi Double check all your axies, and plot the observation inputs into your network. That should make the bugs stand out. At least thatβs where mine were hiding
I'm now thinking the VQ2 floor might be around 14s. Initially I thought 12s. But it has improved so little in days of training, any improvement in speed just runs up against degraded localization. This may be more difficult than I believed.
@kubasienki@anduriltech I presume so, but it's all learned behavior so no way to know for sure.
20 degrees still irks me. Real racing drones use like 45 - 70 degrees. It could have been so much faster
My UTD is dynamic, the sim runs in a separate process from the training. Separate machine, actually. They both run as fast as possible, 6 is just the balance they strike. I have a hard cap at 10, SAC gets weird after that.
And my plan for the physical qualifier is.... no plan. I've been fully focused on getting through the virtuals first. Guess I should get to work...
sim runs at 120sps, I use K=2 for control so training is effectively 60sps. Its not a lot, but for SAC it's plenty. I've always been an SAC guy, never liked PPO. Never tried model-based like Dreamer.
Now that I've worked out all the bugs, training takes ~6 hours from scratch to course completion on a single RTX3090. I run UTD ~6
Moving to rate control means building your own rate controller. I recommend cloning betaflight and telling your agent "implement a rate controller identical to betaflight in this sim". That will avoid a lot of pain. Note that the D term will probably sit at 0 in a sim because no control lag. And yaw is a little weird to get right. Fly it by hand to make sure it feels reasonable before you start training. Easy to waste compute on a broken sim, ask me how I know