wheatley
wheatley copied to clipboard
kneasle
An AI for Ringing Room that can ring any number of bells to increase the scope of practices.
When connecting to ringing room, Wheatley should check the socket io version. Probably information if minor version differs, warning or error for the major version. https://github.com/lelandpaul/ringingroom/pull/173 I imagine there'll be...
Allow an option for Wheatley to recognise either bell rung in a handbell pair held by one ringingroom account, when running in handbell mode, in order to allow more smoothly...
I think the best strategy for this is to have Wheatley want to return to the set peal speed - so if people slow down temporarily, Wheatley will gradually return...
Advantages over the current API: - Good default calls (which are consistent with [Blueline](https://rsw.me.uk/blueline/methods/)) - Autocorrection for slightly incorrect or incomplete method names - Much better up-to-date-ness of the library...
This will help #65 because if fewer human ringers are ringing, they will make up a much smaller proportion of the dataset, and Wheatley will therefore pay them less attention.
This means you can't ring things like anti-April-Day (Grandsire with Plain Bob calls). A solution could be that we turn `generator_from_special_title` into a function that takes a method title and...
As the ringing room api gets added and becomes more stable we should move to using it Endpoint | Method | Description -- | -- | -- /api/tokens | POST...
Because `Go` and `Stand` have two changes warning, there's a possibility that an early call will take place straight away and scupper the ringing. I think the best way to...
If few human ringers are ringing, the sensitivity controls should automatically be adjusted towards having Wheatley be less sensitive to human ringers.
A sensitivity arg would, I think, be between `0.0` and `1.0` and will override the other regression parameters with something that will result in a reasonable estimate for that level...