u/king_1607

I've spent the last month building Yieldsight, a web-based tool that parses STDF files and automatically generates wafer maps, CPK analysis, parametric distributions and yield insights. No scripts, no Excel, no JMP required.

The tool works on synthetic data. But synthetic data only tells you so much.

I need real STDF files from actual ATE machines to know if the parser holds up across different vendors, Teradyne, Advantest, others.

I completely understand that production STDF data is proprietary IP. I'm not asking companies to share confidential data.

What I'm looking for:

• University researchers or PhD students who generate STDF files from lab ATE equipment and would be comfortable sharing anonymized files
• Product engineers or test engineers willing to test the tool with their own data and give honest feedback on whether it actually solves a real problem

In return I'll give free access to anyone who helps, and for university researchers I'll credit your institution on the platform.

Here's the tool if you want to try the sample data first: https://yieldsight-six.vercel.app/

Drop a comment or DM me if you're interested.

I've been speaking with a few wedding planners recently and I keep hearing the same thing, the actual planning and creativity is the fun part, but the business side is a mess.

Things like onboarding new clients, creating and tracking budgets across multiple weddings, chasing vendors for confirmations, building timelines, managing contracts, and keeping clients updated, how are you currently handling all of this?

Are you using a full platform like HoneyBook or Dubsado, or are you still in spreadsheets and Google Docs? What does those tools get wrong for your specific workflow?

Most importantly, what's the one thing you find yourself doing manually every week that you keep thinking should just be automated by now?

Not selling anything here, genuinely trying to understand the real friction before building anything. Would really appreciate honest answers from people actually running their own planning businesses.

I'm building an STDF analytics tool and I'm struggling to find real semiconductor test data to validate the parser against different ATE vendors.

I've been told university labs are a good source since there's no IP concern. If you're a researcher or grad student working with ATE machines and have STDF files you'd be comfortable sharing, even anonymized ones, I'd love to test my parser against them.

In return I'll give you free access to the tool. You upload an STDF file and instantly get wafer maps, CPK analysis, parametric distributions and yield insights. No scripts, no Excel.

If you're interested drop a comment or DM me directly.

I'm building an STDF analytics tool and I'm struggling to find real semiconductor test data to validate the parser against different ATE vendors.

I've been told university labs are a good source since there's no IP concern. If you're a researcher or grad student working with ATE machines and have STDF files you'd be comfortable sharing, even anonymized ones, I'd love to test my parser against them.

In return I'll give you free access to the tool. You upload an STDF file and instantly get wafer maps, CPK analysis, parametric distributions and yield insights. No scripts, no Excel.

If you're interested drop a comment or DM me directly.

I'm building an STDF analytics tool and I'm struggling to find real semiconductor test data to validate the parser against different ATE vendors.

I've been told university labs are a good source since there's no IP concern. If you're a researcher or grad student working with ATE machines and have STDF files you'd be comfortable sharing, even anonymized ones, I'd love to test my parser against them.

In return I'll give you free access to the tool. You upload an STDF file and instantly get wafer maps, CPK analysis, parametric distributions and yield insights. No scripts, no Excel.

If you're interested drop a comment or DM me directly.

Genuinely curious how most of you handle this part of the business.

I've been talking to a few contractors recently and it seems like quoting is either done on paper, in Excel, or through some clunky software that costs a fortune and does way more than anyone actually needs.

Some questions I'm trying to understand:

How long does it take you to put together a quote for a typical job? Do you use any software for it or is it still manual? What's the most frustrating part of your current process? Would you pay for something simple that just handled quotes and invoices cleanly, or do you feel like what you have works fine?

No product to sell here, genuinely trying to understand the workflow before building anything. Would really appreciate honest answers from people actually doing the work.

Genuinely curious how most of you handle this part of the business.

I've been talking to a few contractors recently and it seems like quoting is either done on paper, in Excel, or through some clunky software that costs a fortune and does way more than anyone actually needs.

Some questions I'm trying to understand:

How long does it take you to put together a quote for a typical job? Do you use any software for it or is it still manual? What's the most frustrating part of your current process? Would you pay for something simple that just handled quotes and invoices cleanly, or do you feel like what you have works fine?

No product to sell here, genuinely trying to understand the workflow before building anything. Would really appreciate honest answers from people actually doing the work.

I've spent the last few months building an analytics platform specifically for semiconductor test data. It handles STDF parsing, wafer map visualization, CPK analysis, parametric correlation, and AI-generated insights, built for small fabless teams who don't have a PRE engineer on staff.

The platform is fully deployed and working with sample data. Now I need to test it against real production STDF files before I open it up properly.

If you're a test engineer or work at a small fabless company and have STDF files you'd be willing to share, here's what I'll do in return. I'll run a complete analysis on your data and send you a detailed report covering yield summary, CPK breakdown across parameters, wafer map patterns, and any anomalies the AI flags. Basically a free PRE analysis on your actual data.

You'd also get six months of free access to the platform once it opens.

I understand test data is sensitive. Happy to sign an NDA, use anonymized files, or work with whatever you're comfortable sharing.

If this sounds useful drop a comment or message me directly.

I've spent the last few months building an analytics platform specifically for semiconductor test data. It handles STDF parsing, wafer map visualization, CPK analysis, parametric correlation, and AI-generated insights, built for small fabless teams who don't have a PRE engineer on staff.

The platform is fully deployed and working with sample data. Now I need to test it against real production STDF files before I open it up properly.

If you're a test engineer or work at a small fabless company and have STDF files you'd be willing to share, here's what I'll do in return. I'll run a complete analysis on your data and send you a detailed report covering yield summary, CPK breakdown across parameters, wafer map patterns, and any anomalies the AI flags. Basically a free PRE analysis on your actual data.

You'd also get six months of free access to the platform once it opens.

I understand test data is sensitive. Happy to sign an NDA, use anonymized files, or work with whatever you're comfortable sharing.

If this sounds useful drop a comment or message me directly.

I've been building a yield analytics tool that parses STDF files and automatically generates wafer maps, CPK analysis and flags anomalies. Built it as an outsider coming from a software background, trying to solve a real gap I found in the semiconductor test space.

Here's the thing, I've only tested it with a limited set of STDF files. I have no idea how it behaves with files from different ATE vendors or real production environments.

If anyone here works with STDF files regularly and is willing to throw some files at it, I'd genuinely love to know where it breaks.

If you're interested, drop a comment and I'll reach out directly.

I've been building a yield analytics tool that parses STDF files and automatically generates wafer maps, CPK analysis and flags anomalies. Built it as an outsider coming from a software background, trying to solve a real gap I found in the semiconductor test space.

Here's the thing, I've only tested it with a limited set of STDF files. I have no idea how it behaves with files from different ATE vendors or real production environments.

If anyone here works with STDF files regularly and is willing to throw some files at it, I'd genuinely love to know where it breaks.

If you're interested, drop a comment and I'll reach out directly.

Building an STDF analytics tool and want to test how well it handles files from different ATE vendors. I know STDF is a standard but in practice there are inconsistencies across vendors.

If anyone has sanitized/anonymized STDF files they'd be willing to share, I'd really appreciate it. Happy to share back whatever insights the parser surfaces on your data.

Not selling anything, just trying to build something useful and need real files to know if it actually works.

Building an STDF analytics tool and want to test how well it handles files from different ATE vendors. I know STDF is a standard but in practice there are inconsistencies across vendors.

If anyone has sanitized/anonymized STDF files they'd be willing to share, I'd really appreciate it. Happy to share back whatever insights the parser surfaces on your data.

Not selling anything, just trying to build something useful and need real files to know if it actually works.