---
# System prepended metadata

title: Paul Supervision Meeting - 12th October
tags: [Topic A, Topic B, Topic C]

---

Paul Supervision Meeting - 12th October
===
###### tags: `Topic A` `Topic B` `Topic C`

:::info
- **Location:** Zoom
- **Date:** 12th October 2021 10:30 AM
- **Attendees:** Paul, Matt
- **Apologies:** None
:::

:::warning
Why do we have this template?

- Provide a structure for our meetings.
- Provide a way for us to collaboratively note-take during the meetings.
- Give a nice summary of the discussion for anyone unable to attend the meeting.
- Give some content which can then be attached to the ePortfolio entry for the meeting.
:::
---


# Updates since the last meeting.
:::info
Jot down 3-4 bullet points as updates on progress since the last meeting.

This can replace "for info" items which you would like to inform us of, but we do not need to directly discuss.
:::


- [ ] I have pushed my ds2 local setup to Githup
- [ ] I have formally requested for a 2 months extension from the PG school for the submission of my 3rd year progression report.
- [ ] C
- [ ] D

# *"The Worry List"*

:::info
- Jot down a list of any outstanding issues or queries.
- If you are able to, give an estimate of how much of our meeting time you would like to dedicate to this. 
- Order your items in priority order. This will allow us to make sure we cover off the most important issues first.
:::

- [ ] Ability to generated a huge state size withing 5-10mins when running Query3Stateful workload (15 minutes)
- [ ] Submission of Year 3 progression report (5 minutes)
    - [ ] Asking for two months, and aim to finish in one month
- [ ] C


# Short-term plans for next steps
:::info
- Jot down what you plan to work on next.
- The timescales will typically be between now and the next meeting.
- This can be high level. We'll prioritise these items on the call, change some of them, and we'll put them in the Actions list.
:::

- [ ] Initial focus on getting results.
- [ ] B
- [ ] C
- [ ] D

# Deadlines on the horizon

:::info
We will update this section periodically, so we are all aware of any upcoming deadlines. This can include publication submissions, University deadlines, or other important dates.

The longer ahead we can have visibility of these deadlines, the better we're able to support you (e.g. by reviewing drafts).
:::

- TBC
- TBC
- TBC
- 

# Meeting notes

:::info
**Please note:** We will populate this section collaboratively during the meeting.
:::

- Notes
- Notes
- Notes

# Actions
:::info
All of our actions should have the following things:
- An owner, the person leading on the activity.
- Sufficient detail so we can remember what we are supposed to do.
- A deadline for completion.
:::
:::info
These actions will appear in the next meeting notes either as an update since last time (if completed), on the worry list (if we have run into issues), or in the short-term plans (if we've had to push this item forward).
:::

- [ ] **PO** to send **MF** a copy of the Year 3 Progression guidelines
- [ ] **PO** email PGR inbox to ask about the extension process. Mention you've spoken to MF who is supportive. Ask for 2 months, they can always ask for it sooner.
- [ ] **PO** to document the code changes and upload code to Github.
- [ ] **MF** to run code (Friday PM)