pzserver 0.2.5__tar.gz → 0.2.7__tar.gz

{pzserver-0.2.5 → pzserver-0.2.7}/.github/workflows/build-documentation.yml

@@ -30,7 +30,7 @@ jobs:
         sudo apt-get install pandoc
     - name: Build docs
       run: |
-        sphinx-build -T -E -b html -d docs/build/doctrees ./docs docs/build/html -D exclude_patterns="notebooks/*.ipynb"
+        sphinx-build -T -E -b html -d docs/build/doctrees ./docs docs/build/html -D exclude_patterns="notebooks/*/*.ipynb"
     - name: Run ghp-import
       run: | 
         ghp-import -n -p -f -x docs/ docs/build/html

{pzserver-0.2.5 → pzserver-0.2.7}/.github/workflows/linting.yml

@@ -31,8 +31,7 @@ jobs:
         pip install .[dev]
         if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
         if [ -f requirements-dev.txt ]; then pip install -r requirements-dev.txt; fi
-    - name: Analyze code with linter
-
-      run: |
-        pylint -rn -sn --recursive=y ./src --rcfile=./src/.pylintrc
+    # - name: Analyze code with linter
+    #   run: |
+    #     pylint -rn -sn --recursive=y ./src --rcfile=./src/.pylintrc
 

{pzserver-0.2.5 → pzserver-0.2.7}/.pre-commit-config.yaml

@@ -123,5 +123,5 @@ repos:
             "-d", # Flag for cached environment and doctrees
             "./docs/build/doctrees", # Directory
             "-D", # Flag to override settings in conf.py
-            "exclude_patterns=notebooks/*.ipynb", # Exclude our notebooks from pre-commit
-          ]
+            "exclude_patterns=notebooks/*/*.ipynb", # Exclude our notebooks from pre-commit
+          ]

{pzserver-0.2.5 → pzserver-0.2.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pzserver
-Version: 0.2.5
+Version: 0.2.7
 Author-email: LIneA <itteam@linea.org.br>
 License: MIT License
         

pzserver-0.2.7/docs/nbs.rst

@@ -0,0 +1,6 @@
+Notebooks
+========================================================================================
+
+.. toctree::
+
+    Tutorial introducing PZ Server lib <notebooks/rst/pzserver_tutorial.rst>

pzserver-0.2.5/docs/notebooks/0_introduction.ipynb → pzserver-0.2.7/docs/notebooks/pzserver_tutorial.ipynb

@@ -8,7 +8,7 @@
     "<img align=\"left\" src = \"images/rubin.png\" width=180 style=\"padding: 30px\"> \n",
     "\n",
     "# Photo-z Server\n",
-    "## Tutorial Notebook 0 - Introduction\n",
+    "## Tutorial Notebook\n",
     "\n"
    ]
   },
@@ -18,7 +18,7 @@
    "source": [
     "Contact author: [Julia Gschwend](mailto:julia@linea.org.br)\n",
     "\n",
-    "Last verified run: **2024-Jul-22**"
+    "Last verified run: **2024-Dec-11**"
    ]
   },
   {
@@ -40,7 +40,7 @@
     "tags": []
    },
    "source": [
-    "The PZ Server is an online service available for the LSST Community to host and share lightweight photo-z (PZ) -related data products. The upload and download of data and metadata can be done at the website [pz-server.linea.org.br](https://pz-server.linea.org.br/) (during the development phase, a test environment is available at [pz-server-dev.linea.org.br](https://pz-server-dev.linea.org.br/)). There, you will find two separate pages containing a list of data products each: one for Rubin Observatory Data Management's official data products and the other for user-generated data products. **The registered data products can also be accessed directly from Python code using the PZ Server's data access API, as demonstrated below.**\n",
+    "The PZ Server is an online service available for the LSST Community to host and share lightweight photo-z (PZ) -related data products. The upload and download of data and metadata can be done at the website [pz-server.linea.org.br](https://pz-server.linea.org.br/) (during the development phase, a test environment is available at [pz-server-dev.linea.org.br](https://pz-server-dev.linea.org.br/)). There, you will find two pages containing a list of data products each: one for Rubin Observatory Data Management's official data products and the other for user-generated data products. **The registered data products can also be accessed directly from Python code using the PZ Server's data access API, as demonstrated below.**\n",
     "\n",
     "The PZ Server is developed and delivered as part of the in-kind contribution program BRA-LIN, from LIneA to the Rubin Observatory's LSST project. The service is hosted in the Brazilian IDAC, not directly connected to the [Rubin Science Platform (RSP)](https://data.lsst.cloud/). However, user authorization requires the same credentials as RSP. For comprehensive documentation about the PZ Server, please visit the [PZ Server's documentation page](https://linea-it.github.io/pz-lsst-inkind-doc/). There, you will also find an overview of all LIneA's contributions related to the PZ production. The internal documentation of the API functions is available on the [API's documentation page](https://linea-it.github.io/pzserver).  "
    ]
@@ -51,14 +51,7 @@
    "source": [
     "### How to upload a data product on the PZ Server website\n",
     "\n",
-    "To upload a data product, click on the button **NEW PRODUCT** on the top left of the **User-generated Data Products** page and fill in the Upload Form with relevant metadata. Alternatively, the user can upload files to the PZ Server programmatically via the `pzserver` Python Library (described below). \n",
-    "\n",
-    "The photo-z-related products are organized into four categories (product types):\n",
-    "\n",
-    "- **Spec-z Catalog:** Catalog of spectroscopic redshifts and positions (usually equatorial coordinates).\n",
-    "- **Training Set:** Sample for training photo-z algorithms (tabular data). It usually contains magnitudes, errors, and true redshifts.\n",
-    "- **Photo-z Validation Results:** The Results of a photo-z validation procedure (free format). They usually contain photo-z estimates (single estimates and/or PDFs) of a validation set, photo-z validation metrics, validation plots, etc.\n",
-    "- **Photo-z Table**: This category is for the results of a photo-z estimation procedure. Ideally, the data should be in the same format as the photo-z tables delivered by the DM as part of the LSST data releases. If the data is larger than the file upload limit (200MB), the product entry will store only the metadata, and instructions on accessing the data should be provided in the description field. Storage space can be provided exceptionally for larger tables, depending on the science project justification (to be evaluated by IDAC's management committee).  "
+    "To upload a data product, click the button **NEW PRODUCT** on the top left of the **User-generated Data Products** page and fill in the Upload Form with relevant metadata. Alternatively, the user can programmatically upload files to the PZ Server via the `pzserver` Python Library (described below). "
    ]
   },
   {
@@ -92,22 +85,24 @@
    "source": [
     "### Installation\n",
     "\n",
-    "**For regular users**\n",
-    "\n",
-    "The PZ Server API is avalialble on **pip** as  `pzserver`. To install the API and its dependencies, type, on the Terminal:  \n",
+    "The PZ Server API is avalialble on **pip** as  `pzserver`. To install the API and its dependencies, type on the Terminal:  \n",
     "\n",
     "```\n",
     "$ pip install pzserver \n",
-    "``` "
+    "```\n",
+    "\n",
+    "Or in a notebook code cell: "
    ]
   },
   {
    "cell_type": "code",
    "execution_count": null,
-   "metadata": {},
+   "metadata": {
+    "scrolled": true
+   },
    "outputs": [],
    "source": [
-    "! pip install pzserver "
+    "#! pip install pzserver"
    ]
   },
   {
@@ -116,22 +111,8 @@
     "jp-MarkdownHeadingCollapsed": true
    },
    "source": [
-    "**For developers**  \n",
-    "\n",
-    "Alternatively, if you have cloned the repository with:\n",
-    "\n",
-    "```\n",
-    "$ git clone https://github.com/linea-it/pzserver.git  \n",
-    "``` \n",
-    "\n",
-    "To install the API and its dependencies, type:\n",
-    "\n",
-    "```\n",
-    "$ pip install .[dev]\n",
-    "```\n",
-    "\n",
     "--- \n",
-    "OBS: You might need to restart the kernel on the notebook to incorporate the new library. "
+    "OBS: Depending on your Jupyter Lab version, you might need to restart the kernel to incorporate the new library. "
    ]
   },
   {
@@ -182,7 +163,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "For convenience, the token can be saved into a file named as `token.txt` (which is already listed in the .gitignore file in this repository). "
+    "For convenience, the token can be saved as `token.txt` (which is already listed in the .gitignore file in this repository). "
    ]
   },
   {
@@ -207,7 +188,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The object `pz_server` just created above can provide access to data and metadata stored in the PZ Server. It also brings useful methods for users to navigate through the available contents. The methods with the preffix `get_` return the result of a query on the PZ Server database as a Python dictionary, and are most useful to be used programatically (see details on the [API documentation page](https://linea-it.github.io/pzserver/html/index.html)). Alternatively, those with the preffix `display_` show the results as a styled [_Pandas DataFrames_](https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.html), optimized for Jupyter Notebook (note: column names might change in the display version). For instance:\n",
+    "The object `pz_server` created above can provide access to data and metadata stored in the PZ Server. It also brings additional methods for users to navigate through the available content. The methods with the prefix `get_` return the result of a query on the PZ Server database as a Python dictionary and are most useful to be used programmatically (see details on the [API documentation page](https://linea-it.github.io/pzserver/html/index.html)). Alternatively, those with the prefix `display_` show the results as a styled [_Pandas DataFrames_](https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.html), optimized for Jupyter Notebook (note: column names might change in the display version). For instance:\n",
     "\n",
     "Display the list of product types supported with a short description;"
    ]
@@ -231,7 +212,9 @@
   {
    "cell_type": "code",
    "execution_count": null,
-   "metadata": {},
+   "metadata": {
+    "scrolled": true
+   },
    "outputs": [],
    "source": [
     "pz_server.display_users()"
@@ -259,13 +242,14 @@
    "source": [
     "---\n",
     "\n",
-    "Display all data products available (WARNING: this list can rapidly grow during the survey's operation). "
+    "Display all available data products (WARNING: This list can rapidly grow during the survey's operation). "
    ]
   },
   {
    "cell_type": "code",
    "execution_count": null,
    "metadata": {
+    "scrolled": true,
     "tags": []
    },
    "outputs": [],
@@ -277,16 +261,18 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The information about product type, users, and releases shown above can be used to filter the data products of interest for your search. For that, the method `list_products` receives as argument a dictionary mapping the products attributes to their values. "
+    "The information about product type, users, and releases shown above can be used to filter the data products of interest for your search. For that, the method `list_products` receives as an argument a dictionary mapping the product's attributes to their values. "
    ]
   },
   {
    "cell_type": "code",
    "execution_count": null,
-   "metadata": {},
+   "metadata": {
+    "scrolled": true
+   },
    "outputs": [],
    "source": [
-    "pz_server.display_products_list(filters={\"release\": \"LSST DP0\", \n",
+    "pz_server.display_products_list(filters={\"release\": \"LSST DP0.2\", \n",
     "                                 \"product_type\": \"Training Set\"})"
    ]
   },
@@ -294,13 +280,15 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "It also works if we type a string pattern that is part of the value. For instance, just \"DP0\" instead of \"LSST DP0\": "
+    "It also works if we type a string pattern that is part of the value. For instance, just \"DP0\" instead of \"LSST DP0.2\": "
    ]
   },
   {
    "cell_type": "code",
    "execution_count": null,
-   "metadata": {},
+   "metadata": {
+    "scrolled": true
+   },
    "outputs": [],
    "source": [
     "pz_server.display_products_list(filters={\"release\": \"DP0\"})"
@@ -310,13 +298,14 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "It also allows the search for multiple strings by adding the suffix `__or` (two underscores + \"or\") to the search key. For instance, to get spec-z catalogs and training sets in the same search (notice that filtering is not case sensitive):"
+    "It also allows the search for multiple strings by adding the suffix `__or` (two underscores + \"or\") to the search key. For instance, to get spec-z catalogs and training sets in the same search (notice that filtering is not case-sensitive):"
    ]
   },
   {
    "cell_type": "code",
    "execution_count": null,
    "metadata": {
+    "scrolled": true,
     "tags": []
    },
    "outputs": [],
@@ -328,18 +317,19 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "To fetch the results of a search and attribute to a variable, just change the preffix `display_` by `get_`, like this:  "
+    "To fetch the results of a search and attribute to a variable, just change the prefix `display_` by `get_`, like this:  "
    ]
   },
   {
    "cell_type": "code",
    "execution_count": null,
    "metadata": {
+    "scrolled": true,
     "tags": []
    },
    "outputs": [],
    "source": [
-    "search_results = pz_server.get_products_list(filters={\"product_type\": \"results\"}) # PZ Validation results\n",
+    "search_results = pz_server.get_products_list(filters={\"product_type\": \"results\"}) \n",
     "search_results"
    ]
   },
@@ -354,7 +344,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The default method to upload a data product to the PZ Server is the upload tool on PZ Server website, as shown above. Alternatively, data products can be sent to the host service using the `pzserver` Python library. \n",
+    "As shown above, the default method to upload a data product to the PZ Server is the upload tool on the PZ Server website. Alternatively, the `pzserver` Python library can send data products to the host service. \n",
     "\n",
     "First, prepare a dictionary with the relevant information about your data product: "
    ]
@@ -403,7 +393,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The metadata of a given data product is the information provided by the user on the upload form. This information is attached to the data product contents and is available for consulting on the PZ Server page or using this Python API (`pzserver`). \n",
+    "The metadata of a given data product is the information the user provides on the upload form. This information is attached to the data product contents and is available for consulting on the PZ Server page or using this Python API (`pzserver`). \n",
     "\n",
     "All data products stored on PZ Server are identified by a unique **id** number or a unique name, a _string_ called **internal_name**, which is created automatically at the moment of the upload by concatenating the product **id** to the name given by its owner (replacing blank spaces by \"_\", lowering cases, and removing special characters). "
    ]
@@ -444,7 +434,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "To download any data product stored in the PZ Server, use the `PzServer`'s method `download_product` informing the product's **internal_name** and the path to where it will be saved (the default is the current folder). This method downloads a compressed .zip file which contais all the files uploaded by the user, including data, anciliary files and description files. The time spent to download a data product depends on the internet connection between the user and the host. Let's try it with a small data product. "
+    "To download any data product stored in the PZ Server, use the `PzServer`'s method `download_product` informing the product's **internal_name** and the path to where it will be saved (the default is the current folder). This method downloads a compressed .zip file, which contains all the files uploaded by the user, including data, ancillary files, and description files. The time spent downloading a data product depends on the internet connection between the user and the host. Let's try it with a small data product. "
    ]
   },
   {
@@ -468,7 +458,7 @@
     "\n",
     "### How to share data products with other RSP users\n",
     "\n",
-    "All data products uploaded to the PZ Server are imediately available and visible to all PZ Server users (people with RSP credentials) through the PZ Server website or via the API. Besides informing the product **id** or **internal_name** for programatic access, another way to share a data product is providing the product's URL, which leads to the product's download page. The URL is composed by the PZ Server website address + **/products/** + **internal_name**:\n",
+    "All data products uploaded to the PZ Server are immediately available and visible to all PZ Server users (people with RSP credentials) through the PZ Server website or via the API. One way to share a data product is by providing the product's URL, which leads to the product's download page. The URL is composed by the PZ Server website address + **/products/** + **internal_name**:\n",
     "\n",
     "https://pz-server.linea.org.br/product/ + **internal_name** \n",
     "\n",
@@ -501,7 +491,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Another feature of the PZ Server API is to let users retrieve the contents of a given data product to work on memory (by atributing the results of the method `get_product()` to a variable in the code). This feature is available only for tabular data (product types: **Spec-z Catalog** and **Training Set**). \n",
+    "The `pzserver` library allows users to retrieve the contents of a given data product to work on memory using the method `get_product()`. This feature is available only for tabular data (product types: **Spec-z Catalog** and **Training Set**). \n",
     "\n",
     "By default, the method `get_product` returns an object from a particular class, depending on the product's type. The classes `SpeczCatalog` and `TrainingSet` are simple extensions of `pandas.DataFrame` (via class composition) with a couple of additional attributes and methods, such as the attribute `metadata`, and the method `display_metadata()`. Let's see an example: "
    ]
@@ -529,7 +519,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The tabular data is allocated in the attribute `data`, which is a `pandas.DataFrame`. "
+    "The tabular data is allocated in the attribute `data`, a `pandas.DataFrame`. "
    ]
   },
   {
@@ -579,7 +569,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "In the prod-types you will see details about these specific classes. For those who prefer working with `astropy.Table` or pure `pandas.DataFrame`, the method `get_product()` gives the flexibility to choose the output format (`fmt=\"pandas\"` or `fmt=\"astropy\"`).     "
+    "For those who prefer working with `astropy.Table` or pure `pandas.DataFrame`, the method `get_product()` gives the flexibility to choose the output format (`fmt=\"pandas\"` or `fmt=\"astropy\"`).     "
    ]
   },
   {
@@ -608,14 +598,251 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "### Specific features for each product type \n",
+    "---\n",
+    "\n",
+    "Next, let's explore specific features for each product type...  "
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {
+    "execution": {
+     "iopub.execute_input": "2024-12-11T14:43:17.277296Z",
+     "iopub.status.busy": "2024-12-11T14:43:17.276646Z",
+     "iopub.status.idle": "2024-12-11T14:43:17.345452Z",
+     "shell.execute_reply": "2024-12-11T14:43:17.344690Z",
+     "shell.execute_reply.started": "2024-12-11T14:43:17.277264Z"
+    }
+   },
+   "source": [
+    "## Spec-z Catalogs "
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {
+    "execution": {
+     "iopub.execute_input": "2024-12-11T14:44:23.295109Z",
+     "iopub.status.busy": "2024-12-11T14:44:23.294100Z",
+     "iopub.status.idle": "2024-12-11T14:44:23.394796Z",
+     "shell.execute_reply": "2024-12-11T14:44:23.393752Z",
+     "shell.execute_reply.started": "2024-12-11T14:44:23.295078Z"
+    }
+   },
+   "source": [
+    "In the context of the PZ Server, Spec-z Catalogs are defined as any catalog containing spherical equatorial coordinates and spectroscopic redshift measurements (or, analogously, true redshifts from simulations). A Spec-z Catalog can include data from a single spectroscopic survey or a combination of data from several sources. To be considered a single Spec-z Catalog, the data should be provided as a single file to PZ Server's upload tool. For multi-survey catalogs, adding the survey name or identification as an extra column is recommended. \n",
+    "\n",
+    "\n",
+    "Mandatory columns: \n",
+    "* Right ascension [degrees] - `float`\n",
+    "* Declination [degrees] - `float`\n",
+    "* Spectroscopic or true redshift - `float`\n",
+    "\n",
+    "Recommended columns: \n",
+    "* Spectroscopic redshift error - `float`\n",
+    "* Quality flag - `integer`, `float`, or `string`\n",
+    "* Survey name (recommended for compilations of data from different surveys)"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "Let's see an example of Spec-z Catalog: "
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "gama = pz_server.get_product(14)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "gama.display_metadata()"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "The attribute `data`, which is a `DataFrame` preserves the `plot` method from Pandas.   "
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "Display basic statistics"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "gama.data.describe()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "gama.data.plot(x=\"RA\", y=\"DEC\", kind=\"scatter\")  "
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "gama.data.hist('Z')"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {
+    "execution": {
+     "iopub.execute_input": "2024-12-11T14:48:50.817530Z",
+     "iopub.status.busy": "2024-12-11T14:48:50.816805Z",
+     "iopub.status.idle": "2024-12-11T14:48:50.887900Z",
+     "shell.execute_reply": "2024-12-11T14:48:50.886976Z",
+     "shell.execute_reply.started": "2024-12-11T14:48:50.817502Z"
+    }
+   },
+   "source": [
+    "## Training Sets \n",
+    "    \n",
+    "In the context of the PZ Server, Training Sets are defined as the product of matching (spatially) a given Spec-z Catalog (single survey or compilation) to the photometric data, in this case, the LSST Objects Catalog. The PZ Server API offers a Training Set Maker tool that allows users to build customized Training Sets based on the available Spec-z Catalogs (details below).    \n",
+    "\n",
+    "\n",
+    "_Note 1: Training sets are commonly split into two or more subsets for photo-z validation purposes. If the Training Set owner has previously defined which objects should belong to each subset (training and validation/test sets), this information must be available as an extra column in the table or as clear instructions for reproducing the subset separation in the data product description._\n",
     "\n",
-    "Please take a look at the other tutorial notebooks with particular examples of how to use the `pzserver` library to access and manipulate data from the PZ Server.   \n",
+    "  \n",
+    "_Note 2: The PZ Server only supports catalog-level Training Sets. Image-based Training Sets, e.g., for deep-learning algorithms, are not supported yet._\n",
+    "\n",
+    "\n",
+    "Mandatory column: \n",
+    "* Spectroscopic (or true) redshift - `float`\n",
+    "\n",
+    "Other expected columns\n",
+    "* Object ID from LSST Objects Catalog - `integer`\n",
+    "* Observables: magnitudes (and/or colors, or fluxes) from LSST Objects Catalog - `float`\n",
+    "* Observable errors: magnitude errors (and/or color errors, or flux errors) from LSST Objects Catalog - `float`\n",
+    "* Right ascension [degrees] - `float`\n",
+    "* Declination [degrees] - `float`\n",
+    "* Quality Flag - `integer`, `float`, or `string`\n",
+    "* Subset Flag - `integer`, `float`, or `string`\n"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "For example: "
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "train_goldenspike = pz_server.get_product(9)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {
+    "tags": []
+   },
+   "outputs": [],
+   "source": [
+    "train_goldenspike.display_metadata()"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "Display basic statistics"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "train_goldenspike.data.describe()"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "train_goldenspike.data.hist('redshift', bins=20)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "train_goldenspike.data.hist('mag_i_lsst', bins=20)"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "## Training and Validation Results\n",
     "\n",
+    "The results of training or validating PZ algorithms can not be loaded into memory directly but can be downloaded to the local work directory. "
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "pz_server.download_product(\"182_example_tpz_training_results\", save_in=\".\") "
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "## PZ Server Pipelines (under development) \n",
     "\n",
+    "Spec-z Catalogs and Training Sets can be created using the cross-matching pipelines available on the PZ Server. Any catalog built by the pipeline is automatically registered as a regular user-generated data product and is the same as the uploaded ones. \n"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
     "--- \n",
     "\n",
-    "### Users feedback \n",
+    "## User feedback \n",
     "\n",
     "Is something important missing? [Click here to open an issue in the PZ Server library repository on GitHub](https://github.com/linea-it/pzserver/issues/new). "
    ]
@@ -623,9 +850,9 @@
  ],
  "metadata": {
   "kernelspec": {
-   "display_name": "Python 3 (ipykernel)",
+   "display_name": "LSST",
    "language": "python",
-   "name": "python3"
+   "name": "lsst"
   },
   "language_info": {
    "codemirror_mode": {
@@ -637,7 +864,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.10.10"
+   "version": "3.11.9"
   },
   "nbsphinx": {
    "execute": "never"