-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generalize the Data object #28
Conversation
… to be removed in future versions of sasdata
…(instrument and sample) classes to their own python file
… (Plottable) that all plottable objects inherit from. Add subclasses for 1D, 2D, SESANS, and Slit-Smeared data
… all data objects inherit from
…precation warnings
Cool, I have a workshop tomorrow and Friday, but I might find some time to look somewhere. |
I think its going in the right direction. Would be good to have a chat about it soon. |
… behavior to log warnings instead of throwing errors.
…mpatibility and deprecation purposes. Added type hinting, py2->py3 fixes, and deprecation warnings and documentation.
…7-generalize-1d-2d-data
Working on cleanup in preparation for Contributor Camp XII: @krzywon I'm assuming this kind of change should probably go into 6.0? in which case we may need to prioritize it as such? or is that not the case? |
Ideally, yes, but realistically, probably won't make it in. |
Superseded by #79 |
@lucas-wilkins - this is a start to what I am imagining for how the data object should be refactored. I need this to finish the separation of SasView/sasview#1802 related to unit conversions but want a third set of eyes (@pkienzle already took a quick look and gave his input) to take a look at the direction I am taking.
Once finished, this will fix #17, and fix #19.