|
|
|
|
|
by tezza
428 days ago
|
|
Precisely. The tools often hallucinate: including in its instructions higher up even before your prompt portion. Also the behind the scenes stuff not show to the user during reasoning. You see binary failures all the time when doing function calls or JSON outputs. That is… “please call this function” … does not call function “calling JSON endpoint”… does not emit JSON so from the article the tool generates hallucinations that the tool has used external stuff: but that was entirely fictitious. it does not know that this tool usage was fictitious and then sticks by its guns. The workaround is to have verification steps, throw away “bad” answers. Instead of expecting one true output, expect a stream of results which have a yield (agriculture) of a certain amount. say 95% work, 5% garbage. never consider the results truly accurate, just “accurate enough”. Verify always |
|
If tou ask it to draw a schematic thigns somehow get even worse.
But what it is good at is proposing ideas. So if you want to do a thing that could be solved by using a Gilbert cell, the chances it might mention a Gilbert Cell are realistically there.
But I am already having students coming by with LLM slob circuits asking why the don't work..