70 lines
2.3 KiB
Markdown
70 lines
2.3 KiB
Markdown
# Supervisor meeting notes / to-do
|
|
|
|
*Copied verbatim from Cormac's notes, 28/10/2026. Meeting date: [fill in].*
|
|
|
|
SLR
|
|
MLR
|
|
|
|
Zotero
|
|
Endnote
|
|
Better bib tex/text/tec
|
|
|
|
Paired down sir protocol
|
|
|
|
- review question
|
|
- seed set
|
|
- search strings
|
|
— archive, google scholar
|
|
- snowballing
|
|
— what did these guys cite? So on so forth
|
|
— can have criteria for exclusion,
|
|
— probably nothing useful on qknorm pre 2020, can haver a cut off from before that,
|
|
— same goes for Attention is all you need
|
|
|
|
- extraction table
|
|
— here's a "roper paper",
|
|
—— what claim, what questions were asked,
|
|
- what questions are people asking across the literature,
|
|
— is there anything similar to my research question? Put an Asterix on it
|
|
— how does my question differentiate from theirs?
|
|
— maybe im asked for a small model but theyre asking for a large one, maybe its a cost difference
|
|
— if you do find something similar, make sure you can give two sentences on why your paper is different
|
|
|
|
- in an interview, can defend your lit review by saying
|
|
— this is how I found these papers,
|
|
— this is how
|
|
|
|
Semantic scholar
|
|
Some automated tooling
|
|
If you want to use llms for paper search, find a paper that backs up the tactic
|
|
|
|
Based on what you read/find, review if you want to update/change any of your questions.
|
|
|
|
How to ask questions that give you the scope that you want,
|
|
Ask how not if
|
|
|
|
Because theres an experimental component, you could find an interesting surprise during the experiment.
|
|
Pre register hypothesis
|
|
You have a question 1, and then you will have an answer 1 (or a set?)
|
|
|
|
i.e. does this happen? If so? Does this hold?
|
|
|
|
Whenever you do an experimental run, log it: learning rate, size, epochs, dataset, so on so forth
|
|
- make sure you are never in the situation where you are reviewing your work and you cant remember how you came to a result
|
|
- get into a habit of documenting experimental runs
|
|
- perhaps automate it in a nice json/yaml format, with commit SHAs?
|
|
|
|
"Technical spike", a day to get tech stuff set up.
|
|
- nanogpt, tiny stories, etc
|
|
- get a scaffold setup
|
|
|
|
Get dates for due interims and so on
|
|
|
|
Goal for next day:
|
|
- survey for lit done
|
|
- started on snowball
|
|
- timeline up to me
|
|
- maybe I want to do tech spike later/earlier
|
|
— chat about that the next day
|
|
- if theres something I want him to read, send it onto him (early)
|