Dp point cloud data type, and a separate .py file for datatype #224
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DP_POINT_CLOUDfor point clouds containing images (e.g. diffraction patterns) instead of spectra. Most of the functionalities are similar to the originalPOINT_CLOUD. Visualizer is extended to supportDP_POINT_CLOUDtoo.DataTypeclass out ofdataset.pyinto a new file so that it can be accessed by other modules (specificallydataset_viz.py) without causing cyclical import. It also makes a bit more sense to me thatDataTypeis defined as a standalone enum equally accessible to all modules, instead of as a child class of dataset.py.