Feedback on draft tutorial

[rtapella]

From Grace:

• - does naming it environment.yml vs environment.yaml make a difference? The guide says environment.yaml, but the file in the repo is environment.yml
• - This section tells you to “run_script”, if the script isn’t called called run_script for this example, it is a little confusing to put that in code maybe just say “run your run script, in this example run_gdal.sh”
• - The guide says there is a geotiff input file to test gdal_wrapper with but I don’t see it in the repo
• - I agree with this open issue: Sync command-line run instructions across DPS tutorial and the README.md in this repo #1

There is this note here:
File: build-env.sh - takes conda environment definition from environment.yaml - Have it activate the environment with source activate base (or whatever your env is)

• But the build-env.sh doesn’t have a source activate line

• 1. Maybe for this line “Disk Space is the minimum amount of space you expect—including all inputs, scratch, and outputs—it gives the DPS an approximation to help optimize the run.” give users some advice for what a good baseline is?

• 2. I am confused what this is trying to say: “(you should copy the link and paste it into a new page; if you press register it will be difficult to edit the form and fix any mistakes).” Press register where? You can still go back and edit the form even after pressing “register algorithm”

• 3. In addition to the https://os.zhdk.cloud.switch.ch/envicloud/chelsa/chelsa_V2/GLOBAL/annual/swb/CHELSA_swb_1999_V.2.1.tif example input file, what would an example look like from the ADE? Just /projects/file_path? Maybe just include that even if it seems simple so users know