I think I have found a reasonable tradeoff between simplicity and flexibility now. The basic philosophy is that all classes and functions shall be accessible from the main import of oslo_method_python.
I have removed the OsloMethod class. The MatrixAnalysis class remains. It is right now the only way to access the unfold() and first_generation_method() methods, but I plan to move those out as standalone functions. Then the MatrixAnalysis class will only serve as a convenient wrapper for e.g. error propagation, but the advanced user can choose to make each function call in the analysis explicitly and call the matrices what he or she wants.
Issue by jorgenem Wednesday Jan 09, 2019 at 13:27 GMT Originally opened as https://github.com/oslocyclotronlab/ompy/pull/12
I think I have found a reasonable tradeoff between simplicity and flexibility now. The basic philosophy is that all classes and functions shall be accessible from the main import of oslo_method_python.
I have removed the OsloMethod class. The MatrixAnalysis class remains. It is right now the only way to access the unfold() and first_generation_method() methods, but I plan to move those out as standalone functions. Then the MatrixAnalysis class will only serve as a convenient wrapper for e.g. error propagation, but the advanced user can choose to make each function call in the analysis explicitly and call the matrices what he or she wants.
jorgenem included the following code: https://github.com/oslocyclotronlab/ompy/pull/12/commits