PhotonVision
Robustly remember previous pipeline, resolution, etc. between system shutdowns
Based on #271 and reports on CD, pipeline and resolution could change between start up. More digging to be done
Tentative thoughts...
- Crank up the priority/frequency of the save-to-disk
- Add some form of a watchdog mechanism to check whether things are saved to disk, or at least flag when a save hasn't happened in a while?
- Add a UI thingy which tells the user how long its been since last save. This won't actually fix anything, but just make it easier for end users to make reproducible test cases where they change settings, but don't see a save occur.
One thing that might be nice, on initialization, explicitly log what resolution, pipeline, etc. are being loaded (and make sure these are forcefully loaded on the back end as well just to be sure. Right now I only see explicit setting of exposure.
We've been having this problem lately. On the latest version. No matter what we change, the settings always revert to the last state just before the problem started happening. It's just a few settings and it's manageable but it's annoying. ;)
I'll get some. Is there a way to easily reset the database? I'm fine with Linux commands if need be.
This is the most surefire way as of rn:
sudo service photonvision stop
sudo rm -rf /opt/photonvision/photonvision_config
sudo service photonvision start```
FYI, we ended up putting in a spare server which is now working fine. Still have the old one.
No matter what we change, the settings always revert to the last state just before the problem started happening.
Could you elaborate a bit more on what that means? I'm trying to figure out what I should be ctrl-f-ing for in the log you sent
Ok, for example the 'Top Camera' reverts from using 3-D to using 2-D. That's the most annoying thing that was happening because we wouldn't be able to get pose from it at the beginning of a match.