Before setting parameters like that, be sure that your data and model are all in order. If the model is fitting well, but conditional_effects calls are failing, there might be something in your data. But based on this, I’m not sure the model is fitting well.
This is a consequence of some inputs being extremely close together. I am just looking for a way to work with the error message as it is given to me.
‘nug’ is specific to GPs alone in the brms documentation, and modifying jitter is a normal part of exploring GP specifications, so I would hope this has an easy implementation even if documentation for altering this parameter doesn’t exist yet.