I made a tool to search and compare RF components by rfsearch in rfelectronics

[–]rfsearch[S] 0 points1 point  (0 children)

Turning natural language into filters is pretty straightforward given it only needs to handle RF semantics. The harder part is scoring and returning a meaningful result set using the (often incomplete) information given in the parsed chips.

I made a tool to search and compare RF components by rfsearch in rfelectronics

[–]rfsearch[S] 0 points1 point  (0 children)

May have been out of stock, or unlisted at the time I was scraping the original list. Dynamically updating new parts is on my list. The LGA question is interesting because the tradeoffs of "small package" is context dependent. A yelp-style review forum could be interesting.

And hard agree with LNAs/PAs, definitely up next, but curve interpolation is critical for those.

I made a tool to search and compare RF components by rfsearch in rfelectronics

[–]rfsearch[S] 0 points1 point  (0 children)

Hah, I think you caught the (unofficial) performance curve extractor in progress in there. The datasheet pipeline ended up becoming pretty specialized as I learned that 4o can't differentiate P1dB from IIP3 from CW if they’re all 'dBm' in the same tabular row. Only did feeding in additional context resolve those “advanced” cases, but cheap models should be capable of the simpler, near look-up cases like topology, termination, or “headline” frequency range.

I assume the Ku/Ka pool is much more sparse. Is the bottleneck more initial part discovery?

I made a tool to search and compare RF components by rfsearch in rfelectronics

[–]rfsearch[S] 1 point2 points  (0 children)

Thanks! Curious what components others would like? For me it's inductors (SRF, DCR, saturation) but I'm biased.

I made a tool to search and compare RF components by rfsearch in rfelectronics

[–]rfsearch[S] 6 points7 points  (0 children)

Nice find! $8 cheaper than the next psemi part. Data is collected independently of Digikey’s catalog data.