update notebook 2 based on MolSim 2021 feedback

Author: dwhswenson

2_tps_analysis_tutorial.ipynb

@@ -98,9 +98,13 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
+    "From looking at the path tree, we can get a sense of how well our sampling is going. Some questions to consider:\n",
+    "\n",
     "* Do you see acceptance of both forward and backward shots?\n",
     "* How many decorrelated paths do you see? \n",
-    "* How many accepted moves between decorrelated paths? How many total moves?"
+    "* How many accepted moves between decorrelated paths? How many total moves?\n",
+    "\n",
+    "If you don't see acceptance of both forward and backward shots, that might indicate a problem in either the state definitions or in the sampling (which might be remedied by using a more advanced shooting point selection algorithm). The number MC steps between decorrelated paths gives a sense of how quickly your simulation is exploring path space. If you see very few decorrelated paths (or none at all), that may indicate that you should switch to a more advanced algorithm such as spring shooting."
    ]
   },
   {
@@ -152,6 +156,13 @@
     "```"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "Next let's visualize the shooting point from one of your MC steps. There are two reasons we do this: First, this gives you more practice visualizing OPS data with NGLView. Second, this shows you how to extract the shooting point snapshot from a MC step. Analyzing the shooting points can give ideas on how to troubleshoot problems with sampling (e.g., if you had very few accepted backward shots)."
+   ]
+  },
   {
    "cell_type": "code",
    "execution_count": null,
@@ -326,7 +337,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "* Estimate (by eye) what the path length should be if you ensured that fixed-length TPS would include 99% of the paths. How much longer is that than the average path length here?"
+    "* Estimate (by eye) what the path length should be if you ensured that fixed-length TPS would include 99% of the paths. How much longer is that than the average path length here? What does that mean about the simulation time required for fixed-length TPS as compared the flexible-length TPS?"
    ]
   },
   {
@@ -407,7 +418,7 @@
     "* Which one appears to be more frequent? \n",
     "* Do they look like completely separate channels, or does it look like some paths involves parts of both?\n",
     "\n",
-    "Next, you'll find a representative trajectory for each channel. This will just involve trial and error until you find one."
+    "Next, you'll find a representative trajectory for each channel. This will just involve trial and error until you find one. You're likely to also find trajectories that at least partly cross into the other channel -- these two channels are not very strictly separated."
    ]
   },
   {
@@ -438,7 +449,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "If you have the full simulation data, you could visualize these trajectories with NGLView. (Full simulation data not provided online, due to size), using the same approach as above."
+    "If you have the full simulation data, you could visualize these trajectories with NGLView, using the same approach as above. (Full simulation data not provided online, due to size.)"
    ]
   },
   {
@@ -465,7 +476,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.7.3"
+   "version": "3.7.10"
   },
   "toc": {
    "base_numbering": 1,