Currently, there is an implicit barrier between classes that define how to get certain value (Pds3, Spice, ISIS3cube, etc) and the classes that simply pack them into a valid ALE label (Driver, RadialDistortion, Framer, LineScanner, etc.) such that the former are private variables (prefixed with an underscore) and the latter are not (no underscore prefix). Should we make this more explicit?
Before we had a key list which was determined to add unnecessary complexity. The low hanging fruit is to basically separate the two into different .py file so that the division is a bit more obvious.
Kelvinrr
commented
5 years ago
Currently, there is an implicit barrier between classes that define how to get certain value (Pds3, Spice, ISIS3cube, etc) and the classes that simply pack them into a valid ALE label (Driver, RadialDistortion, Framer, LineScanner, etc.) such that the former are private variables (prefixed with an underscore) and the latter are not (no underscore prefix). Should we make this more explicit?
Before we had a key list which was determined to add unnecessary complexity. The low hanging fruit is to basically separate the two into different
.pyfile so that the division is a bit more obvious.