> 300m turbine heights

[grwhumphries]

Have to come up with a way of dealing with scenarios where turbine height is > 300 m. This is going to be a likely scenario in the next couple of years with 20mw + turbines being proposed

[bcaneco]

@grwhumphries

stoch_crm() and band_crm() are guarded against this - the function check_fhd_vs_maxtip() under validate() will throw an error if the maximum height in the provided FHD is below the max tip height. So, it'll be up to the user to provide appropriate flight height profiles for the turbine scenario.

At the moment, the FHD bootstraps shipped with the package go up to 500m - this was inherited from shiny sCRM, where we padded out the datasets with 0s from 300 to 500m. We could implement the same approach here, i.e. automatically pad out the provided fhd data to cover turbine height (under some constraints obviously), but I'm more comfortable leaving the user to decide how to address the issue.

[grwhumphries]

@bcaneco Ah okay. We should briefly pow-wow about this in terms of band_crm() because the FHD that needs to be run (as per guidance) in that function (or in the Band spreadsheet) is the maximum likelihood scenario from the report Annex, which is now shipped in the package (Johnston_Flight_heights_SOSS.rda). However, that only goes up to 300m - so might need to pad that up as well.