[x] At the bare minimum, it should include objectives for the tutorials, the basic purpose of each tutorial or at least categories of tutorials as this list grows, and whatever software or levels of access might be required for all of the tutorials
[ ] Under each tutorial, I would then separately call out EXACTLY what software and access is required to make things work. And then the individual tutorials don’t even explain what’s going on, it’s just a mess of code that doesn’t do anything. I click the tab ‘using phenotype data’, and the first thing on the page is “BETYdb”, with no context. Then I copy that block of code in and get all kinds of errors. I assume I need to be logged in somewhere else, or I need to have a specific key that I download from somewhere, but this is not explained here. If it is explained elsewhere, it needs to be replicated the first time someone walks through a tutorial, because this is where people will want to start.
[ ] In general, there are no explanations in the tutorials, only code and some plots. These are not tutorials, if anything they are example scripts taken out of context. Code isn’t commented very much either, which is a cardinal sin in programming tutorials.
[ ] In the ‘using sensor metadata’ tab, I have no idea what to do with the link that you present for
[ ] If I grab one of the IDs below it, that doesn’t do me any good. In general, I have no idea what I’m supposed to be doing with the link and sample line of code you’ve got there – is that something I’m supposed to type into an R terminal? I’m fairly certain that this does nothing, which is what happens if I just download R and paste it in there. What do I need to do to make this work, and where is it explained in this entire book?