I haven't exactly chosen my specific loss function yet. From what people have told me looking up iBots loss and DinoV2's loss as well as a loss from a paper by Google might be helpful I think. But I might just end up summing multiple loss functions if they're useful and then check if they work.
As for my objective, I don't really have a specific application in my mind rn other than a chatbot of sorts (with moderate-high capability of logic/reasoning) but on my CPU.
Currently this is a rough idea of how I want it to work tbh:
- Write a query about what it needs to find the answer for given question from the web
- Know when it has obtained the info from the web after looking up the first link and reading its contents otherwise discard it and change query and try again.
- After finding it's content answer the asked common sense/logical reasoning question.
E.g: Q. How should I take a rectangle door outside if all I have is a square window? Possible queries:
- Can rectangle fit into square?
- Rectangles shape
- Squares shape
- Standard window size
- Standard door size Etc
Possible/acceptable answers:
-
Sorry from what I've seen I couldn't find the answer. (This option would be choosen if the model doesn't find the answer in a limit of n queries)
-
Rectangles are more general than squares and windows are generally smaller than doors so depending on your exact size you might just be able to fit it through but if the door size and window size are anything standard I don't think you'll be able to fit it through.
for me the approach can be generalized to different tasks
Can you elaborate?