Add support for external PyTorch Dataset objects (#382) #383
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.

Problem
Currently, Baler only supports loading data from numpy arrays stored in .npz files. This limits the tool's flexibility, especially when working with datasets that require custom loading or preprocessing, or when trying to use standard PyTorch datasets from libraries like torchvision.
Solution
This PR adds support for loading and using external PyTorch
torch.utils.data.Datasetobjects directly with Baler. The implementation allows users to:Implementation Details
load_external_datasetfunction indata_processing.pythat takes a PyTorch Dataset and returns train and validation DataLoadersperform_traininginbaler.pyto detect and load external datasets when providedtrainfunction intraining.pyto accept DataLoaders directly as an alternative to numpy arraysDocumentation Added
docs/guides/external_dataset.mddocs/guides/external_dataset_example.pyTesting
Unit tests verify that:
Limitations
Closes
Closes #382