Updating markdown about data in S3 bucket

content/notebooks/data_discovery_and_access/data_discovery_and_access.ipynb

@@ -256,11 +256,11 @@
    "metadata": {},
    "source": [
     "The `fs.ls()` command allows us to list the contents of the URI. In the above example, the `roman-sci-test-data-prod-summer-beta-test` S3 bucket contains three directories:\n",
-    "- `ROMANISIM` contains the simulated WFI-imaging mode Roman Space Telescope data used in this suite of notebooks\n",
-    "- `STIPS` contains data for the Space Telescope Image Product Simulator (STIPS) notebook (Notebook link: [stips.ipynb](../stips/stips.ipynb))\n",
+    "- `AAS_WORKSHOP` contains the simulated WFI Roman Space Telescope data used in this suite of notebooks\n",
+    "- `STIPS` contains example simulated data from the Space Telescope Image Product Simulator (STIPS; Notebook link: [stips.ipynb](../stips/stips.ipynb))\n",
     "- `OPEN_UNIVERSE` contains data from the OpenUniverse 2024 Matched Rubin and Roman Simulation preview provided by NASA/IPAC Infrared Science Archive (IRSA) at Caltech. \n",
     "\n",
-    "In the next subsection we will explore opening data files made using Roman I-Sim, which are stored in the `ROMANISIM` S3 directory. These simulations are saved in the same file formats as observed Roman data will be and thus are useful to help develop file ingestion pipelines. Unfortunately, Roman I-Sim has not been used to extensively simulate survey data. \n",
+    "In the next subsection we will explore opening data files made using Roman I-Sim, which are stored in the `AAS_WORKSHOP` S3 directory. These simulations are saved in the same file formats as observed Roman data will be and thus are useful to help develop file ingestion pipelines. Unfortunately, Roman I-Sim has not been used to extensively simulate survey data. \n",
     "\n",
     "In the final subsection, we will explore how to open the OpenUniverse preview data (in the `OPEN_UNIVERSE` S3 directory). The OpenUniverse collaboration has simulated extensive datasets from two core community surveys: the High Latitude Time Domain and Wide Area Surveys (HLTDS and HLWAS). Though they have only provided a preview of the full simulation suite, the quantity of data is still sufficient to start creating data pipelines to analyze Roman data.\n",
     "\n",
@@ -273,10 +273,15 @@
    "source": [
     "### Opening Roman I-Sim Models\n",
     "\n",
-    "Diving into the `ROMANISIM` directory, we find three folders:\n",
-    "- `CATALOGS_SCRIPTS`: contains stellar and galactic catalogs used to create the simulated data stored in the other directories\n",
-    "- `DENSE_REGION`: contains calibrated and uncalibrated simulated data of dense stellar fields obtained with different filters for all the eighteen WFI detectors. The data are separarted into two directories, each with a different pointings. Filenames in these directories use the prefixes `r0000101001001001001*` and `r0000101001001001002*`, which correspond to the use of the F158 and F129 optical elements respectively.\n",
-    "- `GALAXIES`: contains one calibrated, simulated image of a galaxy field obtained using the F158 optical element.\n",
+    "Diving into the `AAS_WORKSHOP` directory, we find many files:\n",
+    "- `*_uncal.asdf`: Level 1 (L1; ucalibrated ramp cube) files.\n",
+    "- `*_cal.asdf`: Level 2 (L2; calibrated rate image) files.\n",
+    "- `*_i2d.asdf`: Level 3 (L3; resampled image) files.\n",
+    "- Some additional miscellaneous files for various tutorials.\n",
+    "\n",
+    "As you can see, Roman WFI data are stored in Advanced Scientific Data Format (ASDF) files. See the tutorial notebook [Working with ASDF](../working_with_asdf/working_with_asdf.ipynb) for more information. Regarding file names, note that the first element (separated by underscores) of the file name string of L1 and L2* files denotes programmatic information (e.g., program ID, visit ID, etc.), while the second element gives the exposure number in within the visit. Thus, `r0003201001001001004_0001_wfi02_cal.asdf` and `r0003201001001001004_0002_wfi02_cal.asdf` are L2 files from the same visit but represent exposures 1 and 2, respectively, of the detector WFI02. For simulated data such as the files used for these tutorials, the first element of the file name string has been chosen simply be an example. See the [Roman I-Sim](../romanisim/romanisim.ipynb) tutorial notebook for how these files were generated.\n",
+    "\n",
+    "\\* **Note:** Archival L3 product file names are still being finalized. The L3 file in the S3 bucket has a generic file name (`my_roman_mosaic_i2d.asdf`) that does not follow any naming convention.\n",
     "\n",
     "Below, we use `roman_datamodels` to read the ASDF file corresponding to the dense region as an example. To simplify the workflow we are providing a URI to the sample Roman data. During operations, the data would be referenced using the URI when perform queries through MAST or other data access methods that are currently under development.\n",
     "\n",
@@ -289,7 +294,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "asdf_file_uri = asdf_dir_uri + 'ROMANISIM/DENSE_REGION/R0.5_DP0.5_PA0/r0000101001001001001_01101_0001_WFI01_cal.asdf'\n",
+    "asdf_file_uri = asdf_dir_uri + 'AAS_WORKSHOP/r0003201001001001004_0001_wfi11.asdf'\n",
     "\n",
     "with fs.open(asdf_file_uri, 'rb') as f:\n",
     "    dm = rdm.open(f)\n",
@@ -471,9 +476,9 @@
  ],
  "metadata": {
   "kernelspec": {
-   "display_name": "Roman Calibration latest (2024-03-25)",
+   "display_name": "Python 3 (ipykernel)",
    "language": "python",
-   "name": "roman-cal"
+   "name": "python3"
   },
   "language_info": {
    "codemirror_mode": {
@@ -485,7 +490,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.9"
+   "version": "3.11.11"
   }
  },
  "nbformat": 4,