Structure of Prefs, defaults, & setup

[sneakers-the-rat]

Better document the parameters in prefs -- finish restructuring of setup routine to further separate prefs, keep a list of default prefs like pvp https://github.com/CohenLabPrinceton/pvp/blob/7d772f093a5706266d372aab2d32535200eeb250/pvp/common/prefs.py#L48 so docs can be generated from docstrings more easily.

Specifically, better document the structure of hardware prefs and how that interacts with the HARDWARE descriptor in a task heading as mentioned here: https://groups.google.com/g/autopilot-users/c/_MqzLDDq3CE/m/AvrIWcwbAAAJ

Currently script, their descriptions, and their names are split across multiple files, these should be unified into a single dict for maintainability/elegance/it just sorta sucks this way.

Prefs should also have a better 'getter' method that returns default values when unset in prefs, or kindly return Nones rather than AttributeErrors

[sneakers-the-rat]

lol what the fuck up its me yer big patchi boi here to close this fuckin issue

• prefs are now self documenting which also gives them the extra special qualities of being standardized with sensible defaults. we call it NEW PREFS and we LOVE new prefs. note that this is a BREAKING change because prefs now go like prefs.get('KEY') instead of prefs.KEY which was always fragile and implicit anyway. b87a3fc
• what the fuck we also unified scripts and fixed setup? b87a3fc#diff-247bb8e19fc170654b4b7ca0fb0e490d76c23f42fbc702a5b6923ab7aeebb0ed also related to Programmatic Setup #33
• better document the parameters in prefs - you better bet we fuckin did it by redesigning the whole dang thing and figuring out an ancient sphinx riddle. ec6d5a7
• hardware prefs documented here: f3a7609

SO I AM CLOSING THIS ISSUE WITH A VENGEANCE