diff --git a/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/CruiseDataExport-Transect.xlsx b/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/CruiseDataExport-Transect.xlsx new file mode 100644 index 00000000..ed19b38d Binary files /dev/null and b/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/CruiseDataExport-Transect.xlsx differ diff --git a/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/Tutorial.ipynb b/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/Tutorial.ipynb new file mode 100644 index 00000000..bf062b02 --- /dev/null +++ b/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/Tutorial.ipynb @@ -0,0 +1,199 @@ +{ + "cells": [ + { + "cell_type": "markdown", + "id": "37226b47", + "metadata": {}, + "source": [ + "#
Welcome Aboard VirtualShip! 🚢
\n", + "\n", + "Welcome aboard, oceanography students, to your scientific research vessel! We’re thrilled to have you join us for this exciting journey into the depths of the ocean. You will work on this expedition in groups (of 2 or 3 max). You will plan and execute a virtual oceanographic expedition using the VirtualShip software. Follow the steps below to complete the exercise.\n", + "\n", + "Before you begin running your expedition, make sure you have:\n", + "- Signed up for a **GitHub** account and can Access your **Codespaces** Environment. You can find more information and steps [here.](https://virtualship.readthedocs.io/en/latest/user-guide/tutorials/codespaces_guide.html)\n", + "- Filled in your Choice of Month, Year, and CTD Sensor in the Excel file (see `welcome_aboard.docx` on Brightspace for more information).\n", + "- Have the Cruise Coordinate Excel file (`CruiseDataExport-Transect.xlsx`) downloaded on your laptop/PC (you can find it on Brightspace (or Teams)).\n" + ] + }, + { + "cell_type": "markdown", + "id": "0c0da338", + "metadata": {}, + "source": [ + "# Your Virtual Expedition Across the North Sea\n", + "\n", + "Now let’s get started on running your VirtualShip expedition. Follow the steps below to plan your expedition, and launch your simulation.\n", + "\n", + "### Step 1. Register with the Copernicus Marine Data Store\n", + "***\n", + "\n", + "You will need to register for **Copernicus Marine Service** account (see [here](https://data.marine.copernicus.eu/register)) as VirtualShip streams ocean data directly from there. Register and remember your username and password before you start, because you will be asked for your credentials the first time you run an expedition.\n", + "\n", + "### Step 2. Open your GitHub Codespaces Environment and Upload your Cruise Plan\n", + "***\n", + "\n", + "In your Codespaces environment, upload the cruise coordinate excel file. \n", + "\n", + "From now you will work within the Terminal. You can find the Terminal window in the bottom half of your screen ([see here for what it should look like](https://virtualship.readthedocs.io/en/latest/user-guide/tutorials/codespaces_guide.html#using-the-virtualship-simulation-workspace))\n", + "\n", + "We suggest practicing good file management and creating a dedicated folder for your group's expedition data in the workspace. You can do so by running `mkdir {your-group-name}` in the Terminal (replacing `{your-group-name}` with your actual group name) or via the File Explore panel in the Codespaces interface.\n", + "\n", + "Navigate to the directory where your group will be running your expedition. Then upload the cruise file by right clicking in the File Explorer panel (ideally in the directory you created for your group's expedition data) and selecting the \"Upload\" option. You can also simply drag and drop your file to the Codespaces environment. From here you will be able to access your excel file.\n", + "\n", + "### Step 3. Expedition Initialisation\n", + "***\n", + "\n", + "In the Terminal, navigate to the folder where you uploaded your cruise plan using `cd your-folder-name`. This is where you will run your expedition.\n", + "\n", + "Now enter the following command in the Terminal. Make sure to change:\n", + "- `EXPEDITION_NAME` to something more meaningful for your group’s expedition (eg `Expedition_Group1`)\n", + " - For all subsequent commands make sure to replace `EXPEDITION_NAME` with the name you have chosen\n", + "- Verify your excel file is called CruiseDataExport-Transect.xlsx, otherwise change it to what it is called\n", + "- replace 'YYYY-MM-DD HH:MM:SS' with your start date and time (eg '1997-05-01 08:00:00') (Use the choice you selected in the Excel file on the 19th)\n", + "\n", + "```bash\n", + "virtualship init EXPEDITION_NAME --from-mfp CruiseDataExport-Transect.xlsx --start-date 'YYYY-MM-DD HH:MM:SS'\n", + "``` \n", + "\n", + "This will create a folder/directory called `EXPEDITION_NAME` (or what you have changed this to) with a single file: `expedition.yaml.` This file contains details on the ship and instrument configurations, as well as the expedition schedule based on the sampling site coordinates from your cruise file. \n", + "\n", + "### Step 4. Expedition Scheduling & Ship Configuration\n", + "***\n", + "\n", + "The next step is to finalise the expedition schedule plan, including setting times and instrument selection choices for each waypoint. The easiest way to do so is to use the bespoke VirtualShip planning tool. Enter the following command in Terminal (replace EXPEDITION_NAME with the name you selected previously): \n", + "\n", + "```bash \n", + "virtualship plan EXPEDITION_NAME\n", + "```\n", + "\n", + "**Ship Speed**\n", + "- In the planning tool which appears, under Ship Config Editor > Ship Speed & Onboard Measurements, there is an option to change the ship speed. However, for this expedition, you should leave this as the default 10 knots value.\n", + "\n", + "**Onboard Measurements**\n", + "- VirtualShip is capable of taking onboard temperature/salinity measurements and ADCP measurements. For your expedition, you may choose to turn on onboard temperature/salinity measurements if you would like but this is not required. \n", + "\n", + "**Instrument/Sensor Configuration**\n", + "- The most important instrument configuration setting to consider is the list of sensors for each instrument, which controls what type of measurements/variables the instrument records in the simulation and therefore what output data you will receive for each instrument. \n", + "\n", + "- For your expedition you will be working with **CTD**. Click on CTD and select a sensor you would like to use by toggling the respective switches on or off. Remember to only have **one sensor** switched on and this is the sensor you chose previously. (VirtualShip allows expeditions to run with multiple sensors and instruments, but for your research needs a single CTD sensor is most appropriate). \n", + "\n", + "- You do not need to make any other changes to instruments or ship configuration here. \n", + "\n", + "**Waypoint Datetimes**\n", + "- In the Waypoints Section, you will be able to see all your waypoints (sampling stations) as well as your port of departure and arrival. Based on the time you provided in 'YYYY-MM-DD HH:MM:SS' previously, the expedition will begin at that time and each waypoint time will already be pre-filled, based on estimated travel and station durations relative to your start date. \n", + "\n", + "- You will have a default of 45 minutes stationkeeping time at each station. This may be enough for your expedition, but it may not be, so expect to adjust some of your timings once you have chosen your CTD sensor. The ship needs to slow down to a stop, which takes 15 minutes (default in VirtualShip). The CTD is lowered to the configured maximum depth or the sea floor, whichever is shallowest. The time taken therefore depends on the depth in that location and the winch speed (default is 1 m/s in VirtualShip). Remember that the time is doubled as well because the CTD needs to be brought back up. (So for a depth of 100m, it will take 200 seconds for the CTD to go down and back up). The ship needs to speed back up again and set course to the next waypoint, which takes another 15 minutes (default in VirtualShip).\n", + "\n", + "- It is important to ensure that the timings for each station are realistic. There must be enough time for the ship to travel to each site at the prescribed speed (10 knots), and enough time to actually carry out your deployments once you arrive. The expedition schedule will be automatically verified when you press Save Changes in the planning tool\n", + "\n", + "- At each waypoint determine the time, and toggle on the switch for CTD to sample it at each waypoint. \n", + "\n", + "- Remember you have **9 days** for your expedition (from the moment of departure to arrival at port). \n", + "\n", + "**Save Changes**\n", + "- When you are happy with your ship configuration and schedule plan, press Save Changes at the bottom of the planning tool.\n", + "\n", + "- On pressing Save Changes the tool will check the selections are valid (for example that the ship will be able to reach each waypoint in time). If they are, the changes will be saved to the expedition.yaml file, ready for the next steps. If your selections are invalid you should be provided with information on how to fix them.\n", + "\n", + "### Step 5. Run the Expedition\n", + "***\n", + "\n", + "The logistical planning is complete. Now you can now run your virtual expedition and hope for good weather! This stage will take all the measurements at each waypoint in your expedition schedule, using input data sourced from the [Copernicus Marine Data Store](https://data.marine.copernicus.eu/products). \n", + "\n", + "You will need to register for a Copernicus Marine Service account (you can do so [here](https://data.marine.copernicus.eu/register)), if you have not done so already. \n", + "\n", + "You can run your expedition simulation using the command (change `EXPEDITION_NAME` to the name you previously selected):\n", + "```bash\n", + "virtualship run EXPEDITION_NAME\n", + "```\n", + "\n", + "If this is your first time running VirtualShip, you will be prompted to enter your own Copernicus Marine Data Store credentials (these will be saved automatically for future use). Enter your username (not email) and password. (*Note:* You will not see your password when entering it. This is normal.)\n", + "\n", + "Small simulations (e.g. small space-time domains and fewer instrument deployments) will be relatively fast. For large, complex expeditions, it _could_ take up to an hour to simulate the measurements depending on your choices. Waiting for simulation is a great time to practice your level of patience. A skill much needed in oceanographic fieldwork!!\n", + "\n", + "### Step 6. Results\n", + "***\n", + "\n", + "Upon successfully completing the simulation, results from the expedition will be stored in the `EXPEDITION_NAME/results` directory, written in `.parquet` format. You can download the results file to your laptop by right clicking on the ctd.parquet file and selecting download. It is advised to download the file to a new folder on your laptop.\n", + "\n", + "**Congratulations! You have finished your expedition across the North Sea!**\n", + "\n", + "***Share your Expedition Results (ctd.parquet file) by emailing the file to s.r.bhagat@uu.nl. You will have to compress/zip your file to be able to share it. Include your group name, and the month, year, sensor used for your expedition in your email.*** " + ] + }, + { + "cell_type": "markdown", + "id": "4f020dc5", + "metadata": {}, + "source": [ + "## Analysing your Results\n", + "***\n", + "\n", + "You have collected data from your research expedition. Now we will see how to analyse and understand your results. \n", + "\n", + "You can analyse your results in our **post-processing workspace**. You will have to download the `ctd.parquet` file to your local laptop and upload it to a new post-processing workspace. This is a separate, cloud-based JupyterLab environment (hosted on [Binder](https://mybinder.org/)) with all the analysis tools and example tutorials already installed. See the Post-processing Workspace Guide below for how to use it.\n", + "\n", + "[See details here on how to access the post-processing workspace.](https://virtualship.readthedocs.io/en/latest/user-guide/tutorials/binder_guide.html)\n", + "\n", + "You can directly start the workspace by [clicking here](https://mybinder.org/v2/gh/Parcels-code/virtualship-workspace/HEAD?urlpath=lab/tree/welcome.md).\n", + "\n", + "- [See how to Upload your Results data (ctd.parquet) here ](https://virtualship.readthedocs.io/en/latest/user-guide/tutorials/binder_guide.html#upload-your-virtualship-output-files)\n", + "\n", + "- [See how to Analyse your Data here](https://virtualship.readthedocs.io/en/latest/user-guide/tutorials/binder_guide.html#running-the-example-tutorials)\n", + " - Make sure you have uploaded your result file to the workspace. After this under `tutorials` you will find `CTD_transects.ipynb`. Open the file and follow the steps mentioned there to plot and analyse your CTD data. \n", + " - You can run sections of code using Shift+Enter. Be patient while loading and running the file, it may take some time.\n", + "\n", + "**Interpreting your Results**\n", + "***\n", + "\n", + "Here are some questions for you to consider to understand your results:\n", + "- Explain why the data is available at different depths throughout the expedition.\n", + "- Explain the pattern seen for your sensor as you move along the expedition. (Remember you start in the deep shelf and move closer to land (Texel) as the expedition progresses)\n", + "\n", + "- For Oxygen Sensor: \n", + " - Describe the evolution of oxygen along the transect\n", + " - Where is the lowest oxygen found and why do you think this is the case?\n", + "- For Nitrate Sensor:\n", + " - Are there very high nitrate values nearest to land? If so, why do you think so?\n", + "- For pH Sensor:\n", + " - Hypothesize why pH is lower in some spots.\n", + "- For Phytoplankton (/Chlorophyll) Sensor:\n", + " - Where are the highest concentrations of chlorophyll and plankton?" + ] + }, + { + "cell_type": "markdown", + "id": "8e031d2e", + "metadata": {}, + "source": [ + "#
VirtualShip Survey
\n", + "***\n", + "\n", + "The VirtualShip Classroom is developed by researchers at Utrecht University. At the end of your course, please complete our short end-of-course survey. Your experience and participation in the survey will help us improve the learning experience for future students\n", + "\n", + "Before taking part, please read the [**Research Participant Information Sheet**](https://virtualship.readthedocs.io/en/latest/user-guide/user-profiles/educators/information_sheet.html). It explains what taking part in the study involves, how your data will be used and stored, and your rights as a participant (taking part is voluntary).\n", + "\n", + "Once you have finished all VirtualShip activities in your course, fill in the survey here: [**https://survey.uu.nl/jfe/form/SV_0OLu4lKYPyLhAxM**](https://survey.uu.nl/jfe/form/SV_0OLu4lKYPyLhAxM)." + ] + }, + { + "cell_type": "markdown", + "id": "5b373efd", + "metadata": {}, + "source": [ + "**Things Went Wrong:** \n", + "***\n", + "It is possible that you encountered challenges during your expedition and things did not go according to plan. Anything that can go wrong, will go wrong (Murphy's Law). See:\n", + "- [Normalizing failure: when things go wrong in participatory marine social science fieldwork](https://publications.csiro.au/publications/publication/PIcsiro:EP2022-3465).\n", + "- [Emotions and failure in academic life: Normalising the experience and building resilience](https://www.cambridge.org/core/journals/journal-of-management-and-organization/article/emotions-and-failure-in-academic-life-normalising-the-experience-and-building-resilience/91FD71A50A32404D8EDFFB7886FF3521)." + ] + } + ], + "metadata": { + "language_info": { + "name": "python" + } + }, + "nbformat": 4, + "nbformat_minor": 5 +} diff --git a/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/VirtualShip_OceanFuture_2026.pdf b/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/VirtualShip_OceanFuture_2026.pdf new file mode 100644 index 00000000..47e7cd09 Binary files /dev/null and b/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/VirtualShip_OceanFuture_2026.pdf differ diff --git a/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/Welcome_aboard.docx b/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/Welcome_aboard.docx new file mode 100644 index 00000000..4e33955d Binary files /dev/null and b/docs/user-guide/archives/teaching-26-27/UU-oceans-of-future/Welcome_aboard.docx differ