What feature would you like to propose?
It will be nice if the PyCytoData object can track which preprocessing steps have been previously performed. This will allow user to use the generic .preprocess() method without specifying the necessary steps or risking applying the same steps twice.
How do you envision this feature to be implemented?
We can easily add an additional attribute and store a dictionary. Perhaps a .summary() will make sense overall as well!
Are there any existing alternatives or workarounds?
No. Currently, users have to specify everything or run the defaults.
What else would you like us to know?
We need to think about how the default method handles the tasks because this can become a breaking change. At the very least, providing the information to the user and throwing a warning are safe at this stage. If we do a major upgrade in the future, we can deprecate and update. This is partially inspired by stantargets, but I don't expect we do extensive static code analysis or anything of the sort.
What feature would you like to propose?
It will be nice if the
PyCytoDataobject can track which preprocessing steps have been previously performed. This will allow user to use the generic.preprocess()method without specifying the necessary steps or risking applying the same steps twice.How do you envision this feature to be implemented?
We can easily add an additional attribute and store a dictionary. Perhaps a
.summary()will make sense overall as well!Are there any existing alternatives or workarounds?
No. Currently, users have to specify everything or run the defaults.
What else would you like us to know?
We need to think about how the default method handles the tasks because this can become a breaking change. At the very least, providing the information to the user and throwing a warning are safe at this stage. If we do a major upgrade in the future, we can deprecate and update. This is partially inspired by stantargets, but I don't expect we do extensive static code analysis or anything of the sort.