use yaml file for AutomationHAT GPIO pin number assignment

[lspitler]

To change the GPIO pin assignments currently one has to hack the __init__ function of:
https://github.com/AstroHuntsman/huntsman-dome/blob/develop/domehunter/__init__.py

Better to specify a yaml file that contains GPIO pin assignments.

Optional: see this file for how to implement GPIO pin assignments as a separate class:
https://github.com/panoptes/POCS/blob/develop/pocs/dome/astrohaven.py

[AnthonyHorton]

@wtgee might encourage us to use the config server from panoptes-utils for this: https://github.com/panoptes/panoptes-utils/tree/develop/panoptes/utils/config

[wtgee]

Yes, we'll want to figure out if the config server is the best option for Huntsman. I think it could be as it simplifies a lot, but there's some question of whether we want to use it in a piecemeal fashion or want one giant config server.

…

On Mon, Aug 12, 2019, 12:32 Anthony Horton ***@***.***> wrote: @wtgee <https://github.com/wtgee> might encourage us to use the config server from panoptes-utils for this: https://github.com/panoptes/panoptes-utils/tree/develop/panoptes/utils/config — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22?email_source=notifications&email_token=AAARIUH4462QOAU6Q5FWCL3QED7WNA5CNFSM4IJPMWG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4BVFPY#issuecomment-520311487>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAARIUGPLJDFUUTVJJW66YTQED7WNANCNFSM4IJPMWGQ> .

[lspitler]

Interesting idea. Normally for such a simple subsystem, I'd say its overkill, but it is an elegant solution in terms of long-term maintainability. I gather we'd be running a server for the Lens Pis anyways?

@wtgee I guess you must know you're well past the point where it must be tempting to fork off e.g. config-server (and a lot of your other utils) as its own repo (pyamlserver?) so someone doesn't need to install all of POCs to use this handy util.

[wtgee]

On Wed, Aug 14, 2019, 04:39 Lee Spitler ***@***.***> wrote: Interesting idea. Normally for such a simple subsystem, I'd say its overkill, but it is an elegant solution in terms of long-term maintainability. I gather we'd be running a server for the Lens Pis anyways? @wtgee <https://github.com/wtgee> I guess you must know you're well past the point where it must be tempting to fork off e.g. config-server (and a lot of your other utils) as its own repo (pyamlserver?) so someone doesn't need to install all of POCs to use this handy util.

It has been split out of POCS for a while now and is a part of panoptes-utils although I have been tempted to split from that as well. —

…

You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22?email_source=notifications&email_token=AAARIUB7BEA237KOZ4JNSGLQEMZYNA5CNFSM4IJPMWG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4HF5TQ#issuecomment-521035470>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAARIUGQV2RWAW7ZLPE7HPTQEMZYNANCNFSM4IJPMWGQ> .

[fergusL]

Should also read in calibrated az_to_ticks from yaml file instead of triggering a calibration run when gotoaz() is called and dome_az is None.
see original comment from @AnthonyHorton
#26 (comment)