For some data-sets some link functions may not work and throw an error, which currently causes fit_regression to stop. When testing the available link functions in betareg, when one of these fails, the error should be caught rather than stop the function. Alternatively, the list of link functions can be passed as argument so that the user can skip some if they are causing problem. The latter solution is easier to program but requires 1. that the user realises which one is the link function causing problem, and 2. probably requires multiple runs of fit_regression to find which ones to retain and which ones to drop out. The first option (to programmatically catch the error and remove the offending link function(s) is more elegant and functional I think.
For some data-sets some link functions may not work and throw an error, which currently causes fit_regression to stop. When testing the available link functions in betareg, when one of these fails, the error should be caught rather than stop the function. Alternatively, the list of link functions can be passed as argument so that the user can skip some if they are causing problem. The latter solution is easier to program but requires 1. that the user realises which one is the link function causing problem, and 2. probably requires multiple runs of fit_regression to find which ones to retain and which ones to drop out. The first option (to programmatically catch the error and remove the offending link function(s) is more elegant and functional I think.