tscircuit community
← Back to community index
# contributor·Active

Seve - For sure one of the reasons AI switches ...

For sure one of the reasons AI switches to "manual" routing is when the autorouter produces DRC errors. It is like "uhh that's impossible to resolve" so it stops trying to use the autorouter. We may be able to tell it about reroute autorouting phases as a workaround, not sure. Pr

Started by SeveSep 19, 202634 messages

Discussion

Last active last month · plain text
Seveoriginal post
For sure one of the reasons AI switches to "manual" routing is when the autorouter produces DRC errors. It is like "uhh that's impossible to resolve" so it stops trying to use the autorouter. We may be able to tell it about reroute autorouting phases as a workaround, not sure. Probably should just make sure we're not outputting drc errors haha
shibo
yeah, but we're not trying to fix DRC errors while making board, I say we add a hint when it runs the check you say "You have * DRC errors, you may want to use the reroute autorouting phases feature as a workaround"
Seve
yea that's a good idea
shibo
<@757706909351411845> still wip with issues, please give an initial quick review, I think this could be good for the next TI demo if it works correctly
shibo
https://github.com/ShiboSoftwareDev/subtract-component-from-circuit-json
shibo
it performs inflation and intercepts the components you want to subtract
Seve
TSX can be rendered with boolean props- the goal is to have parameterized dev boards that can be rendered https://customize-am62a-reference-design.vercel.app
Seve
The issue is this is very slow, we also arent converting the boards well- missing teardrops etc
Seve
<@778624824875941908> you have to watch the attio calls, this was in the last ti call,
Seve
Idk why the source code for this isnt on github tho- will fix that
Seve
I mean unless youre saying its better to not render conditionally for some reason, like it is more optimized to remove from circuit json
Seve
Conditional tsx makes a lot more sense to me, but there’s an optimizatiom issue and the source for that vercel page needs to get on github, but it is just rendering tsx conditionally
shibo
ooh, so instead of creating a tool, we just create the tsx board with parameters for what components to include?
shibo
yeah that is way better
shibo
I'm still going through the meetings, a lot of interesting stuff
shibo
tsx is so powerful now that you think about it
Seve
Yea the issue is the tsx can be slow to render but yea
Seve
Id rather have it in tsx so we can omit sheets and run validation if necessary
shibo
we could prebuild all options
Seve
There are probably too many but yea maybe
shibo
in the ti website where they have the references if they would use tsx, they could prebuild any combination of configurations
Seve
You should just recreate that demo page, it only takes a second and im afk
Seve
The tsx is hard to generate because altium
Seve
But you can try to get trace hovering working didnt work for me
shibo
altium-to-tscircuit?
Seve
I think due to teardrop
Seve
Maybe
Seve
Not sure, if ai does the conversion thats also ok
Seve
Altium to tscircuit is a good idea tho
shibo
we have a repo called circuit-json-to-tscircuit which is very incomplete, should we do altium-to-circuit-json then circuit-json-to-tscircuit? or create a new repo called altium-to-tscircuit directly?
shibo
i use a browser called zen, it hides the sidebar with the vertical tabs and when you hover near the edge it pops up, making them vertical allows you to know what each tab has
shibo
<@757706909351411845> Live site: [customize-am62a-reference-design-red.vercel.app](https://customize-am62a-reference-design-red.vercel.app/) Repository: [ShiboSoftwareDev/customize-am62a-reference-design](https://github.com/ShiboSoftwareDev/customize-am62a-reference-design)

Want to add to the conversation?

Reply in Discord so your notes stay connected to the source.
Continue in Discord ↗