Temperature Setting of Different Tasks
Now the best temperature is stated to be 0.3, does this apply across all tasks? Asking since the guideline page on api-docs still suggests a table of different t values for different tasks. Specifically I'm interested in code generation/editing performance, a task where usually you see a lower temperature or even 0.
I am currently testing 0.3, as 0.8 was not working well for coding. A sufficiently complex prompt for this is:
Create a rotating outer pentagon enclosing three progressively smaller pentagons, each missing exactly one side and spinning in alternating directions, each smaller than the pentagon that its inside of. Place five colored balls bouncing inside the innermost pentagon, the balls produce particle effects whenever they collide with walls and the other balls. The balls conform to gravity but are bouncy and rebound off the walls and each other with decent force, but not too much. We should see them casually bouncing off objects they collide with. Code it in HTML5.
I am currently testing 0.3, as 0.8 was not working well for coding. A sufficiently complex prompt for this is:
Create a rotating outer pentagon enclosing three progressively smaller pentagons, each missing exactly one side and spinning in alternating directions, each smaller than the pentagon that its inside of. Place five colored balls bouncing inside the innermost pentagon, the balls produce particle effects whenever they collide with walls and the other balls. The balls conform to gravity but are bouncy and rebound off the walls and each other with decent force, but not too much. We should see them casually bouncing off objects they collide with. Code it in HTML5.
Are you referring to the value you pass to the API call or the actual temperature after the mapping?