diff --git a/docs/source/_static/css/custom.css b/docs/source/_static/css/custom.css new file mode 100644 index 000000000..39757f3ee --- /dev/null +++ b/docs/source/_static/css/custom.css @@ -0,0 +1,7 @@ +html[data-theme="light"] { + /***************************************************************************** + * main colors + */ + --pst-color-primary: rgb(19,7,83); + --pst-color-secondary: rgb(252,177,62); +} diff --git a/docs/source/conf.py b/docs/source/conf.py index 0a1369cc5..a530cb453 100644 --- a/docs/source/conf.py +++ b/docs/source/conf.py @@ -74,7 +74,11 @@ # Add any paths that contain custom static files (such as style sheets) here, # relative to this directory. They are copied after the builtin static files, # so a file named "default.css" will overwrite the builtin "default.css". -html_static_path = [] +html_static_path = ["_static"] + +html_css_files = [ + "css/custom.css", +] # Don't show module names in front of class names. add_module_names = False diff --git a/docs/source/datasets/datasets.rst b/docs/source/datasets/datasets.rst index eab15d100..93beeed59 100644 --- a/docs/source/datasets/datasets.rst +++ b/docs/source/datasets/datasets.rst @@ -24,7 +24,7 @@ By default datasets are downloaded to ``~/.meerkat/datasets/{name}/{version}``. dp = mk.datasets.get("imagenette", dataset_dir="/local/download/of/imagenette/full") -You can also configure Meerkat to use a different default root directory. By setting the ``mk.config.root_dir = "/local/download/of"``, the default location for datasets will be ``/local/download/of/datasets/{name}/{version}``. +You can also configure Meerkat to use a different default root directory. By setting the ``mk.config.datasets.root_dir = "/local/download/of"``, the default location for datasets will be ``/local/download/of/datasets/{name}/{version}``. *How does Meerkat's dataset registry fit in with other dataset hubs?* The purpose of the Meerkat dataset registry is to provide *code* for downloading datasets and loading them into :class:`~meerkat.DataPanel` objects. The Meerkat registry, like `Torchvision Datasets `_, doesn't actually host any data. In contrast, dataset hubs like `HuggingFace Datasets `_ and `Activeloop Hub `_ are great community efforts that *do* host data. So, the Meerkat registry is complementary to these hubs: in fact, we can currently load any dataset in the HuggingFace hubs directly through our registry. For example, we can load the `IMBD dataset `_ hosted on HuggingFace with ``mk.datasets.get("imdb")``. @@ -37,7 +37,7 @@ In contrast, dataset hubs like `HuggingFace Datasets -#T_83701 .col-1 { +#T_9ab09 .col-1 { max-width: 50%; } - +
- - - + + + - - + - - + - - + + + + + + + + + + + + + + + + + + + - - + - - + - - + - - + - - + + + + + + + - - + - - + + + + + + +
 tagsversionshomepagetagsversionshomepage
celeba + celeba
image
face recognition
 +
main
linklink
imagenet + coco +
+
image
object recognition
+
+ 		+
+
2014
+
+ 		link
expw +
+
image
classification
+
+ 		+
+
main
+
+ 		link
fer +
+
image
facial emotion recognition
+
+ 		+
+
plus
+
+ 		link
imagenet
image
classification
 +
ilsvrc2012
linklink
imagenette + imagenette
image
classification
 +
full
320px
160px
linklink
mirflickr + mirflickr
image
retrieval
 +
25k
linklink
ngoa +
+
art
+
+ 		+
+
main
+
+ 		link
pascal + pascal
image
object recognition
 +
2012
linklink
fer +
+
image
facial recognition
algorithmic bias
+
+ 		+
+
plus
+
+ 		link