update

examples/notebooks/comparison_trajectory_calculators.ipynb

@@ -35,7 +35,7 @@
    },
    "source": [
     "# Different ways to obtain the Trajectory\n",
-    "This example builds upon the <project:direct_reconstruction> example and demonstrates three ways\n",
+    "This example builds upon the <project:direct_reconstruction.ipynb> example and demonstrates three ways\n",
     "to obtain the trajectory information required for image reconstruction:\n",
     "- using the trajectory that is stored in the ISMRMRD file\n",
     "- calculating the trajectory using the radial 2D trajectory calculator\n",
@@ -107,7 +107,7 @@
    "id": "6",
    "metadata": {},
    "source": [
-    "### Using KTrajectoryRadial2D - Trajectory\n",
+    "### Using KTrajectoryRadial2D - Specific trajectory calculator\n",
     "For some common trajectories, we provide specific trajectory calculators.\n",
     "These calculators often require only a few parameters to be specified,\n",
     "such as the angle between spokes in the radial trajectory. Other parameters\n",
@@ -143,7 +143,7 @@
    "id": "8",
    "metadata": {},
    "source": [
-    "### Using KTrajectoryPulseq\n",
+    "### Using KTrajectoryPulseq - Trajectory from pulseq sequence file\n",
     "This will calculate the trajectory from the pulseq sequence file\n",
     "using the PyPulseq trajectory calculator. This method\n",
     "requires the pulseq sequence file that was used to acquire the data.\n",
@@ -223,20 +223,26 @@
    ]
   },
   {
-   "cell_type": "code",
-   "execution_count": null,
+   "cell_type": "markdown",
    "id": "13",
    "metadata": {},
-   "outputs": [],
    "source": [
-    "# Tada! We have successfully reconstructed images using three different trajectory calculators.\n",
-    "# ```{note}\n",
-    "# Which of these three methods is the best depends on the specific use case:\n",
-    "# If a trajectory is already stored in the ISMRMRD file, it is the most convenient to use.\n",
-    "# If a pulseq sequence file is available, the trajectory can be calculated using the PyPulseq trajectory calculator.\n",
-    "# Otherwise, a trajectory calculator needs to be implemented for the specific trajectory used.\n",
-    "# ```"
+    "Tada! We have successfully reconstructed images using three different trajectory calculators.\n",
+    "```{note}\n",
+    "Which of these three methods is the best depends on the specific use case:\n",
+    "If a trajectory is already stored in the ISMRMRD file, it is the most convenient to use.\n",
+    "If a pulseq sequence file is available, the trajectory can be calculated using the PyPulseq trajectory calculator.\n",
+    "Otherwise, a trajectory calculator needs to be implemented for the specific trajectory used.\n",
+    "```"
    ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "14",
+   "metadata": {},
+   "outputs": [],
+   "source": []
   }
  ],
  "metadata": {

examples/notebooks/direct_reconstruction.ipynb

@@ -53,7 +53,6 @@
     "import tempfile\n",
     "from pathlib import Path\n",
     "\n",
-    "import mrpro.algorithms.dcf\n",
     "import zenodo_get\n",
     "\n",
     "dataset = '14617082'\n",
@@ -115,12 +114,13 @@
    "source": [
     "## Setup the DirectReconstruction instance\n",
     "We create a `~mrpro.algorithms.reconstruction.DirectReconstruction` and supply ``kdata``.\n",
-    "`~mrpro.algorithms.reconstruction.DirectReconstruction` uses the information in `kdata` to\n",
+    "`~mrpro.algorithms.reconstruction.DirectReconstruction` uses the information in ``kdata`` to\n",
     " setup a Fourier transfrm, density compensation factors, and estimate coil sensitivity maps.\n",
     "(See the *Behind the scenes* section for more details.)\n",
     "\n",
     "```{note}\n",
-    "You can also directly set the Fourier operator, coil sensitivity maps, dcf, etc. of the reconstruction instance.\n",
+    "You can also directly set the Fourier operator, coil sensitivity maps, density compensation factors, etc.\n",
+    "of the reconstruction instance.\n",
     "```"
    ]
   },