It sits in the online casino's site. Some sites require you to play through the bonus once, while others allow you to withdraw directly once you reach a certain balance. For the ones that require you to play through, I just play the bonus through low-volatility slots.
You can record Medication as an Medication event type or a Veterinary event type.
For required tests - you can create a custom Event Type called 'Coggins' and record that. Or there is a genetic test result section under the horse that you can record info.
You can also upload document for the tests you are taking.
There is also a Medication Task List feature. If you have a lot of horses that need meds - this allows you to check them off each day as they are done.
I developed this feature earlier this month but haven't publicised it yet as it is still being tested by the user who requested it.
Happy to have a chat - particularly about what USA users are looking for - just email me via === support at horserecords.info ====
I am constantly searching for this. To point a locally hosting LLM to a locally hosted code repo - and then start improving it from there would be awesome.
Depending on how serious you are about this (and how well you can slap together a few different python packages), it is very doable today.
Get one of the better llama versions fine-tuned on code (e.g. WizardCoder), take your entire code base and create embeddings from it, put those into a vector database.
Now, every time you ask your LLM a question about your code base, you first turn that prompt into an embedding and perform a search on your vector database. The results of that search are appended as context to the actual prompt before passing it to the LLM itself.
There's tons of packages that help with all of that, Langchain and Faiss are probably the most popular right now.
interesting, i'd love to do this too. but it sounds like there aren't any full-featured, opensource packages/projects that do this all-together? I'd love to hack the parts together, but i don't have the time/energy these days to do it.
thanks for the helpful keywords though, it helps point me in the right direction.
Agreed. I have found that generated horses never look right. The legs are routinely wrong. And the horses look more like a cartoon representation than an actual horse.
ChatGPT has been very useful to rearrange text for me. Particularly when a journo wants original content for a question I've already answered.
The code it produces is at a junior level. It _looks_ right at first glance but when you implement it, it is rarely good code and often needs tweaks. It is good at general stuff but the more specific you need it to be, the worse it is.
It's a great project IMHO - the rewriting of text is so, so useful to me and saves a lot of time.
That's true, but producing results that are close and just need tweaks is hugely valuable, as long as you're aware that's what you'll get. It's far faster to review and improve existing code than to start from scratch. Of course you need to be knowledgeable enough to identify if what it gives you is complete garbage that shouldn't be used as a basis, but for a good programmer, it could be a huge time-saver. Especially if you extrapolate into the future. Imaging a chatGPT-like feature built into IDEs, with the ability to generate code not just to a prompt, but in context.
They're very smartly having this work as a tractor attachment so they're not reinventing the literal wheels. For small farms, a scaled-down version could be pushed along like a wheelbarrow or attached to something like an ATV or ride-on mower.
But at the home garden scale, I'd like to see a dog-sized spider-like robot that would roam the block doing this. It can be very hard to keep soil weed free, and then weed it once it isn't.
