Fix ArchiveDataframe link in visualize docstrings

ribs/visualize/_cvt_archive_3d_plot.py

@@ -155,10 +155,10 @@ def cvt_archive_3d_plot(
             this argument instead of the data currently in the archive. This
             data can be obtained by, for instance, calling
             :meth:`ribs.archives.ArchiveBase.data` with ``return_type="pandas"``
-            and modifying the resulting :class:`ArchiveDataFrame`. Note that, at
-            a minimum, the data must contain columns for index, objective, and
-            measures. To display a custom metric, replace the "objective"
-            column.
+            and modifying the resulting
+            :class:`~ribs.archives.ArchiveDataFrame`. Note that, at a minimum,
+            the data must contain columns for index, objective, and measures. To
+            display a custom metric, replace the "objective" column.
         measure_order (array-like of int): Specifies the axes order for plotting
             the measures. By default, the first measure (measure 0) in the
             archive appears on the x-axis, the second (measure 1) on y-axis, and

ribs/visualize/_cvt_archive_heatmap.py

@@ -103,10 +103,10 @@ def cvt_archive_heatmap(archive,
             this argument instead of the data currently in the archive. This
             data can be obtained by, for instance, calling
             :meth:`ribs.archives.ArchiveBase.data` with ``return_type="pandas"``
-            and modifying the resulting :class:`ArchiveDataFrame`. Note that, at
-            a minimum, the data must contain columns for index, objective, and
-            measures. To display a custom metric, replace the "objective"
-            column.
+            and modifying the resulting
+            :class:`~ribs.archives.ArchiveDataFrame`. Note that, at a minimum,
+            the data must contain columns for index, objective, and measures. To
+            display a custom metric, replace the "objective" column.
         transpose_measures (bool): By default, the first measure in the archive
             will appear along the x-axis, and the second will be along the
             y-axis. To switch this behavior (i.e. to transpose the axes), set

ribs/visualize/_grid_archive_heatmap.py

@@ -91,10 +91,10 @@ def grid_archive_heatmap(archive,
             this argument instead of the data currently in the archive. This
             data can be obtained by, for instance, calling
             :meth:`ribs.archives.ArchiveBase.data` with ``return_type="pandas"``
-            and modifying the resulting :class:`ArchiveDataFrame`. Note that, at
-            a minimum, the data must contain columns for index, objective, and
-            measures. To display a custom metric, replace the "objective"
-            column.
+            and modifying the resulting
+            :class:`~ribs.archives.ArchiveDataFrame`. Note that, at a minimum,
+            the data must contain columns for index, objective, and measures. To
+            display a custom metric, replace the "objective" column.
         transpose_measures (bool): By default, the first measure in the archive
             will appear along the x-axis, and the second will be along the
             y-axis. To switch this behavior (i.e. to transpose the axes), set

ribs/visualize/_parallel_axes_plot.py

@@ -83,10 +83,10 @@ def parallel_axes_plot(archive,
             this argument instead of the data currently in the archive. This
             data can be obtained by, for instance, calling
             :meth:`ribs.archives.ArchiveBase.data` with ``return_type="pandas"``
-            and modifying the resulting :class:`ArchiveDataFrame`. Note that, at
-            a minimum, the data must contain columns for index, objective, and
-            measures. To display a custom metric, replace the "objective"
-            column.
+            and modifying the resulting
+            :class:`~ribs.archives.ArchiveDataFrame`. Note that, at a minimum,
+            the data must contain columns for index, objective, and measures. To
+            display a custom metric, replace the "objective" column.
         measure_order (list of int or list of (int, str)): If this is a list
             of ints, it specifies the axes order for measures (e.g. ``[2, 0,
             1]``). If this is a list of tuples, each tuple takes the form

ribs/visualize/_sliding_boundaries_archive_heatmap.py

@@ -69,10 +69,10 @@ def sliding_boundaries_archive_heatmap(archive,
             this argument instead of the data currently in the archive. This
             data can be obtained by, for instance, calling
             :meth:`ribs.archives.ArchiveBase.data` with ``return_type="pandas"``
-            and modifying the resulting :class:`ArchiveDataFrame`. Note that, at
-            a minimum, the data must contain columns for index, objective, and
-            measures. To display a custom metric, replace the "objective"
-            column.
+            and modifying the resulting
+            :class:`~ribs.archives.ArchiveDataFrame`. Note that, at a minimum,
+            the data must contain columns for index, objective, and measures. To
+            display a custom metric, replace the "objective" column.
         transpose_measures (bool): By default, the first measure in the archive
             will appear along the x-axis, and the second will be along the
             y-axis. To switch this behavior (i.e. to transpose the axes), set