Hey all!
I’ve been using Quilter quite a bit during a recent board design project and I’ve tried to upload the board design up to Quilter to see what it does at each phase of the design. This has resulted in me clicking in the UI quite a bit and I have some ideas on things that could be changed or added to make it easier.
Delete All Button for Constraints (Diff. Pairs, Decoupling Caps).
I’ve found that many of my designs fail because the constraints seem to be too tight. Not sure if that’s actually the case, but I’ve found I’ve spent the most “wasted” time in the UI, constantly mashing the delete button to clear out all of one or the other set of constraints that was autogenerated.
Upload or save set of constraints configuration
Since my workflow is something like this:
- Finalize schematic
- Draw board outline and import footprints
- Upload to quilter
- See results
- Place any components I’ve decided have an “idea” place based on quilter’s ideas
- Route critical traces I think should be different than what quilter did
- Upload and repeat steps 3 → 7
I find that I’ve spent a lot of time re-setting the configuration for a “run” of quilter. It would be nice to be able to copy the config from a previous run or export /import it in some way so that once I declare: “this decoupling cap is correct for this pin” I don’t have to always recheck that the auto generated decoupling is correct or re-add it.
Explain Why a Job Fails
I’ve been throwing a lot of stuff at Quilter and interestingly, I’ve found that most of my jobs fail. It’s really not obvious to me why generally, but it seems like the time a job took falls in one of a few buckets which would suggest that there are at least broad categories of “why” for failures. I know this is a big challenge for any generative / ML project, but trying to make an effort to explain why, could greatly accelerate usage of quilter.
For example, all of the screen shot below are my runs with one board file. You can see that some of the failures seem to cap at < 2 hours, while some have run up to 8 hours.
Perhaps broad categories could be like:
- Could not place all components
- Could not route all traces
- Could not solve constraints
- etc
Anyway, it’s a very interesting project and looking forward to seeing it grow.