edit output animation and link to Vesnas tutorial

Author: reint-fischer

docs/examples/tutorial_output.ipynb

@@ -106,7 +106,7 @@
    "source": [
     "pset.execute(\n",
     "    parcels.kernels.AdvectionRK4,\n",
-    "    runtime=np.timedelta64(24, \"h\"),\n",
+    "    runtime=np.timedelta64(48, \"h\"),\n",
     "    dt=np.timedelta64(5, \"m\"),\n",
     "    output_file=output_file,\n",
     ")"
@@ -363,7 +363,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Trajectory plots like the ones above can become very cluttered for large sets of particles. To better see patterns, it's a good idea to create an animation in time and space. To do this, matplotlib offers an [animation package](https://matplotlib.org/stable/api/animation_api.html). Here we show how to use the [**FuncAnimation**](https://matplotlib.org/3.3.2/api/_as_gen/matplotlib.animation.FuncAnimation.html#matplotlib.animation.FuncAnimation) class to animate parcels trajectory data.\n",
+    "Trajectory plots like the ones above can become very cluttered for large sets of particles. To better see patterns, it's a good idea to create an animation in time and space. To do this, matplotlib offers an [animation package](https://matplotlib.org/stable/api/animation_api.html). Here we show how to use the [**FuncAnimation**](https://matplotlib.org/3.3.2/api/_as_gen/matplotlib.animation.FuncAnimation.html#matplotlib.animation.FuncAnimation) class to animate parcels trajectory data, based on [this visualisation tutorial](https://github.com/Parcels-code/10year-anniversary-session5/blob/eaf7ac35f43c222280fa5577858be81dc346c06b/animations_tutorial.ipynb) from 10-years Parcels. \n",
     "\n",
     "To correctly reveal the patterns in time we must remember that the `obs` dimension does not necessarily correspond to the `time` variable ([see the section of Trajectory data structure above](#Trajectory-data-structure)). In the animation of the particles, we usually want to draw the points at each consecutive moment in time, not necessarily at each moment since the start of the trajectory. To do this we must [select the correct data](#Conditional-selection) in each rendering.\n"
    ]
@@ -396,7 +396,7 @@
    "outputs": [],
    "source": [
     "# Number of timesteps to animate\n",
-    "nframes = 13  # use less frames for testing purposes\n",
+    "nframes = 25  # use less frames for testing purposes\n",
     "nreducedtrails = 1  # every 10th particle will have a trail (if 1, all particles have trails. Adjust for faster performance)\n",
     "\n",
     "\n",