updating 103 4 based on melissa comments

Author: christinawilliams

DP1/100_How_to_Use_RSP_Tools/103_Image_access_and_display/103_4_Cutout_exposures.ipynb

@@ -60,7 +60,9 @@
     "\n",
     "IVOA provides the <a href=\"https://www.ivoa.net/documents/SODA/20170517/REC-SODA-1.0.html\">Server-side Operations for Data Access (SODA)</a> protocol to provide these remote data processing operations. This protocol allows users to perform computations (pixel operations, image transformations, etc) on the remote server, which avoids unnecssary data movement. The LSST architecture has a \"VO-first\" approach, meaning that VO standards are implemented in all applicable services, enabling the use of VO tools such as the image cutout service to access LSST data. \n",
     "\n",
-    "The procedure is to identify the remote web location of the image of interest (called a datalink), and use the web service to create a cutout from the linked data remotely, before transfering the cutout to the user on the Rubin Science Platform.\n",
+    "The procedure is to identify the remote web location of the image of interest (called a datalink), and use the web service to create a cutout from the linked data remotely, before transferring the cutout to the user on the Rubin Science Platform.\n",
+    "\n",
+    "This notebook demonstrates two types of cutout services: `cutout-sync-exposure`, which returns the full set of metadata and image extensions that are contained in the `ExposureF` data type (Section 3), and `cutout-sync-maskedimage` which returns the mask extension with the science and variance images (`MaskedImageF` data type; Section 4). These two cutout services are ideal for generating a small number of cutouts if needing to use LSST pipelines to run analysis on the cutouts. Another cutout service `cutout-sync` exists to generate bulk cutouts, which minimizes data transfer by just returning the image extension and header of minimal metadata, and if not needing to use LSST Pipelines for their analysis. See tutorial notebook 103.9 for a demonstration of how to generate bulk cutouts with the cutout service.\n",
     "\n",
     "Further details and information can be found at <a href=\"https://www.ivoa.net/documents/DataLink/20211115/WD-DataLink-1.1-20211115.html\"> the IVOA data link documentation</a>, where it says Access Data Services. Rubin-specific documentation for these can also be found in <a href=\"https://dmtn-238.lsst.io/\">this document describing the RSP DataLink service implementation strategy</a>. \n",
     "\n",
@@ -72,7 +74,7 @@
    "id": "72fa86ab-0996-4637-9a99-d94b2084b786",
    "metadata": {},
    "source": [
-    "**Related tutorials:** Tutorial notebook 103.5 demonstrates how to perform bulk cutouts using the cutout service that returns only the image extension to minimize the data transferred. "
+    "**Related tutorials:** See also the 103-series tutorial on image stamps, which demonstrates how to perform bulk cutouts using the cutout service that returns only the image extension to minimize the data transferred. "
    ]
   },
   {
@@ -324,7 +326,7 @@
    "id": "d945e191-7ee4-458a-bb0f-fb00cd219e30",
    "metadata": {},
    "source": [
-    "Lastly, call the Rubin Image Cutout Service. This notebook demonstrates two types of cutout services: `cutout-sync-exposure`, which returns the full set of metadata and image extensions that are contained in the `ExposureF` data type (Section 3), and `cutout-sync-mask` which returns the mask extension with the science and variance images (`MaskedImageF` data type; Section 4). See tutorial notebook 103.5 for a demonstration of how to generate bulk cutouts with the cutout service `cutout-sync`, which minimizes data transfer by just returning the image extension and header of minimal metadata. \n",
+    "Lastly, call the Rubin Image Cutout Service.  This section will demonstrate `cutout-sync-exposure`, which returns the full set of metadata and image extensions that are contained in the `ExposureF` data type. \n",
     "\n",
     "To use the cutout service in this example, the IVOA procedure `cutout-sync-exposure` is called using `get_adhocservice_by_id`. It is done by feeding the data link created above (called `dl_result`) to `from_resource`. Since the Rubin DP1 imaging is proprietary it is necessary to again provide the authorization for the current RSP session. Do this using the `get_pyvo_auth` function."
    ]
@@ -707,7 +709,7 @@
    "source": [
     "## 4. Masked image cutouts\n",
     "\n",
-    "As mentioned in Section 3, there are three types of cutout services. Demonstrated above is the default `cutout-sync` which returns just the image extension. The cells above demonstrated the `cutout-sync-exposure` service that returns an `ExposureF` type image with all LSST image extensions. The `cutout-sync-maskedimage` service that returns an `MaskedImageF` type containing the LSST image, variance, and bitmask. \n",
+    "As mentioned earlier, there are three types of cutout services. Demonstrated above in Section 3 is the `cutout-sync-exposure` service that returns an `ExposureF` type image with all LSST image extensions. The `cutout-sync-maskedimage` service that returns an `MaskedImageF` type containing the LSST image, variance, and bitmask. But, unlike `ExposureF`, the `MaskedImageF` is missing the full range of metadata that may be needed to perform science on the images, including the WCS model and bounding box, the photometric calibration and physical filter used, optical models including the PSF and aperture correction map, telemetry and detector. \n",
     "\n"
    ]
   },