hyrax.data_sets.hyrax_cifar_data_set
Attributes
Classes
Base class for Hyrax Cifar datasets |
|
Map style CIFAR 10 dataset for Hyrax |
|
Iterable style CIFAR 10 dataset for Hyrax |
Module Contents
- class HyraxCifarBase(config: dict, data_location: pathlib.Path = None)[source]
Base class for Hyrax Cifar datasets
- class HyraxCifarDataSet(config: dict, data_location: pathlib.Path = None)[source]
Bases:
HyraxCifarBase,hyrax.data_sets.data_set_registry.HyraxDataset,torch.utils.data.DatasetMap style CIFAR 10 dataset for Hyrax
This is simply a version of CIFAR10 that is initialized using Hyrax config with a transformation that works well for example code.
We only use the training split in the data, because it is larger (50k images). Hyrax will then divide that into Train/test/Validate according to configuration.
Overall initialization for all DataSets which saves the config
Subclasses of HyraxDataSet ought call this at the end of their __init__ like:
from hyrax.data_sets import HyraxDataset from torch.utils.data import Dataset class MyDataset(HyraxDataset, Dataset): def __init__(config): <your code> super().__init__(config)
If per tensor metadata is available, it is recommended that dataset authors create an astropy Table of that data, in the same order as their data and pass that metadata_table as shown below:
from hyrax.data_sets import HyraxDataset from torch.utils.data import Dataset from astropy.table import Table class MyDataset(HyraxDataset, Dataset): def __init__(config): <your code> metadata_table = Table(<Your catalog data goes here>) super().__init__(config, metadata_table)
- Parameters:
config (dict, Optional) – The runtime configuration for hyrax
metadata_table (Optional[Table], optional) – An Astropy Table with 1. the metadata columns desired for visualization AND 2. in the order your data will be enumerated.
object_id_column_name (Optional[str], optional) – The name of the column containing object IDs. If None, uses the default from config or creates one from the ids() method.
- class HyraxCifarIterableDataSet(config: dict, data_location: pathlib.Path = None)[source]
Bases:
HyraxCifarBase,hyrax.data_sets.data_set_registry.HyraxDataset,torch.utils.data.IterableDatasetIterable style CIFAR 10 dataset for Hyrax
This is simply a version of CIFAR10 that is initialized using Hyrax config with a transformation that works well for example code. This version only supports iteration, and not map-style access
We only use the training split in the data, because it is larger (50k images). Hyrax will then divide that into Train/test/Validate according to configuration.
Overall initialization for all DataSets which saves the config
Subclasses of HyraxDataSet ought call this at the end of their __init__ like:
from hyrax.data_sets import HyraxDataset from torch.utils.data import Dataset class MyDataset(HyraxDataset, Dataset): def __init__(config): <your code> super().__init__(config)
If per tensor metadata is available, it is recommended that dataset authors create an astropy Table of that data, in the same order as their data and pass that metadata_table as shown below:
from hyrax.data_sets import HyraxDataset from torch.utils.data import Dataset from astropy.table import Table class MyDataset(HyraxDataset, Dataset): def __init__(config): <your code> metadata_table = Table(<Your catalog data goes here>) super().__init__(config, metadata_table)
- Parameters:
config (dict, Optional) – The runtime configuration for hyrax
metadata_table (Optional[Table], optional) – An Astropy Table with 1. the metadata columns desired for visualization AND 2. in the order your data will be enumerated.
object_id_column_name (Optional[str], optional) – The name of the column containing object IDs. If None, uses the default from config or creates one from the ids() method.