search

LowellObservatory / NightWatch

A system to display a set of important information at an observatory.
2 stars 0 forks source link

Consider graduating "Camelot" prototypes to fully fledged modules #25

Closed astrobokonon closed 5 years ago

astrobokonon commented 5 years ago

This is really just a style/code quality thing, but the submodules being used for NightWatch presently:

https://github.com/LowellObservatory/Camelot/tree/master/BokehMcBokehface https://github.com/LowellObservatory/Camelot/tree/master/GOESMcGOESface https://github.com/LowellObservatory/Camelot/tree/master/WebcamMcWebcamface https://github.com/LowellObservatory/Camelot/tree/master/RadarLove

Could/should probably be moved into a more descriptive subpackage at some point. Camelot is working just fine for me, though, so I'll only really do it if someone (higher up the food chain) demands it.

astrobokonon commented 5 years ago

Thinking about this more, this is the logical next step really; moving these off into a common/core NightWatch associated module allows much greater abstraction and hopefully some memory savings, as well as stopping my now constant goof of thinking I'm working in plotGOES when really I'm editing plotNEXRAD...

astrobokonon commented 5 years ago

Initial work started by Camelot@adbf491 and I'll build from there.

astrobokonon commented 5 years ago

In the process of moving everything into the NightShift repository.

astrobokonon commented 5 years ago

What a long and strange trip this was. Tons of edge cases, mostly because of my half-hearted attempts of unification of things related to parsing the configuration files. Those are generally still messy and confusing, and probably overlap with the ligmos ones!

Initially in testing as of NightShift@e9c8f11 and DockerDev@cf2fe66

astrobokonon commented 5 years ago

Good enough for now. Before the "final" version it should be looked over again to try to clean up more.