Advised harness & config?

#6
by kaiami - opened

Please can you advise which harness you used and which configuration of the Q8 model you used for this to work?
In Unsloth it seems unable to successfully one-shot any of your examples, it will usually fail somewhere down the chain with the edit-file tool call, go into a loop or the resulting HTML is incomplete or has errors.
I haven't been able to get anything to successfully work from this so I hope you can provide some insight on what I might be doing wrong 😊

hey! thanks for giving the model a try! :)

i'm using llama.cpp b11889 with its built-in webui, full gpu offload, flash attention enabled and f16 kv cache.

my sampling settings are temperature 0.6, top k 20, top p 0.95 and min p 0. batch size is 512, microbatch size is 128, with just one parallel slot.

one important thing is to set the output limit to -1 (unlimited), otherwise the generation might get cut off before the html is complete. of course, it's still limited by the available context window.

i recommend around 72k context if your hardware can handle it, since some of the training samples go up to 72k tokens. 64k should already cover most cases though.

for my tests, i simply ask the model to generate a complete standalone html file directly in chat. i haven't tested unsloth's edit-file tool workflow, so that might explain some of the issues you're seeing.

also, could you try deleting your current gguf and downloading it again from the model page? you might have downloaded one of the earlier versions, and i've already uploaded improved checkpoints.

let me know if that helps! i'd be happy to figure out what's going wrong if you're still having trouble. thanks again for testing it!

Thanks for your reply, indeed the edit-file tool was the issue, having it generate the HTML inline as a code block worked instead.

kaiami changed discussion status to closed

glad to hear it worked! haha

quite a few people have been running into the same issue, so i'm happy we figured it out.

the model was trained mainly to generate complete responses, so it works best when producing a full html file from scratch. you can also ask it to rewrite the entire html with changes or improvements, and that works too.

the tool calling and edit-file workflows aren't very reliable yet, since the training was focused on complete code generation rather than those kinds of interactions.

that's definitely something i'd like to improve in future training. thanks again for testing and sharing the feedback!

what thinking do you set it to for your results?

Sign up or log in to comment