3 ms·
The thing about data sheets is you have to watch out for your own assumptions when reading them. If it doesn't explicitly say it'll do X... it won't, no matter
by mikewarot 2y ago
The thing about data sheets is you have to watch out for your own assumptions when reading them. If it doesn't explicitly say it'll do X... it won't, no matter how common it is in other parts of the same type.
It might help but you have to be the backstop when it comes to the final call. Measuring the false positive/false negative rate could be tedious, but it's important to have a good estimate of, in order to use it wisely.
- pera 2y agoYeah, I see what you mean, like if I want to find for instance "a sub milliampere X" but in the pdf it only says uA then it would be impossible for an LLM to suggest that
- pera 2y ago> respond with true or false: is 1234uA submilliampere? > True. 1234 microamperes (uA) is equal to 1.234 milliamperes (mA), which is sub-milliampere.
- pulvinar 2y agoInteresting. I found that GPT-4 gets this wrong quite consistently, and o1-preview gets it right. It takes a moment to think it through and so isn't tripped up by relying on heuristics.
- mystified5016 2y ago> If it doesn't explicitly say it'll do X... it won't Unfortunately, that is only true until it isn't. Most datasheets are not as complete as you would like, and many are just incorrect. It's up to you to take the incomplete information and make a judgement call as an engineer. Undocumented features are not uncommon.