Feedback loop

#1
by PartyParrot - opened

The model makes many mistakes like undefined variables which it could catch itself if it had a feedback loop. I'd suggest downloading headless Chrome to run the code and catch any errors, and then rendering the scene to a file (maybe with multiple viewing angles) and then ingesting the image file to check whether it looks right.

I tried to build such a feedback loop myself using unsloths mmproj, but the model got stuck repeating itself. It might help to add feedback loops to the training data.

Another idea to improve the training with feedback loops is to corrupt a good scene and instruct the model to fix it.

yeah, you're right about those issues. i'm seeing around a 60% one-shot success rate on complex scenes so far. sometimes it generates unused variables or declares the same variable twice and breaks the code, especially at higher temperatures

i'm finishing another checkpoint today and then moving on to rl, where the model will get feedback from actually running and rendering the scenes

the errors you mentioned definitely happen, and i'm hoping the feedback loop will help reduce them. i also like your idea of training it to fix intentionally broken scenes

yeah, you're right about those issues. i'm seeing around a 60% one-shot success rate on complex scenes so far. sometimes it generates unused variables or declares the same variable twice and breaks the code, especially at higher temperatures

i decided to release this early because, compared to the base 4b model, which struggled to even generate a decent chair in my tests, this already felt like a pretty big step forward. but training is still ongoing

i'm finishing another checkpoint today and then moving on to rl, where the model will get feedback from actually running and rendering the scenes

the errors you mentioned definitely happen, and i'm hoping the feedback loop will help reduce them. i also like your idea of training it to fix intentionally broken scenes

Sign up or log in to comment