Merge pull request #361 from cecilehannay/main

troubleshooting section - final changes

Author: cecilehannay

notebooks/troubleshooting/exercises/troubleshooting_cam.ipynb

@@ -47,11 +47,7 @@
   {
    "cell_type": "markdown",
    "id": "e4e74779-4778-446a-be7e-50e0c1ee125e",
-   "metadata": {
-    "jupyter": {
-     "source_hidden": true
-    }
-   },
+   "metadata": {},
    "source": [
     "<div class=\"alert alert-warning\">  \n",
     "<details> \n",
@@ -162,24 +158,41 @@
     "\n",
     "Instead, examine the log files in `RUNDIR`.\n",
     "\n",
-    "What you should find in your run directory is three log files. \n",
-    "- One for the coupler ``cpl.log.*``,\n",
-    "- one for CAM ``atm.log.*`` \n",
-    "- and one for CESM ``cesm.log.*``.\n",
+    "What you should find in your run directory is **CESM log files**. It should look like: \n",
+    "```\n",
+    "atm.log.6612071.desched1.260701-115945\n",
+    "cesm.log.6612071.desched1.260701-115945\n",
+    "diags.log.6612071.desched1.260701-115945\n",
+    "drv.log.6612071.desched1.260701-115945\n",
+    "glc.log.6612071.desched1.260701-115945\n",
+    "ice.log.6612071.desched1.260701-115945\n",
+    "lnd.log.6612071.desched1.260701-115945\n",
+    "logfile.000000.out\n",
+    "med.log.6612071.desched1.260701-115945\n",
+    "mpibind.6612071.log\n",
+    "ocn.log.6612071.desched1.260701-115945\n",
+    "rof.log.6612071.desched1.260701-115945\n",
+    "wav_in.log\n",
+    "wav.log.6612071.desched1.260701-115945\n",
+    "```\n",
+    "\n",
+    "You will also see many files named:\n",
+    "\n",
+    "```text\n",
+    "PET*.ESMF_LogFile\n",
+    "```\n",
+    "\n",
+    "These are **ESMF log files** written by individual MPI tasks. They are usually **not** the first place to look when debugging a typical CESM runtime failure.\n",
+    "\n",
     "\n",
-    "Somewhere in these log files is information about what has gone wrong, but it is often not entirely\n",
+    "\n",
+    "Somewhere in the **CESM log files** is information about what has gone wrong, but it is often not entirely\n",
     "straightforward to find. \n",
     "- Often at the bottom of the log file, there are errors that are not relative to your problem because\n",
     "they are just demonstrating that individual processes are exiting. \n",
     "- Often the relevant error lies above this and can sometimes be found by searching for the first occurrence of ERROR or ABORT or cesm.exe. \n",
     "\n",
-    "In this case, searching for the first occurrence of ERROR in ``cesm.log.*`` gives us some relevant information. We find\n",
-    "```\n",
-    "ERROR: FLDLST: 1 errors found, see log\n",
-    "```\n",
-    "This tells us is that something has gone wrong with the list of output variables that we have asked for.\n",
-    "\n",
-    "More information can then be found in the CAM log file ``atm.log.*``.\n",
+    "In this case, the end of ``atm.log.*`` gives us some relevant information. \n",
     "Look at the very end of that file and you should see\n",
     "```\n",
     "FLDLST: T2M in fincl(1, 2) not found\n",
@@ -214,14 +227,6 @@
     "\n",
     "This is the same workflow you will use to diagnose many runtime errors in CESM."
    ]
-  },
-  {
-   "cell_type": "code",
-   "execution_count": null,
-   "id": "569d13e0-9a28-4356-b828-bd102a74d7a3",
-   "metadata": {},
-   "outputs": [],
-   "source": []
   }
  ],
  "metadata": {