# shibo - @Seve these issues are blocking me from... Channel: #contributor Source: https://discord.com/channels/1233487248129921135/1542507285299859577 Started: 2026-08-27T12:13:15.740000+00:00 Last activity: 2026-08-27T20:29:54.083000+00:00 ## shibo — 2026-08-27T12:13:15.215000+00:00 <@757706909351411845> these issues are blocking me from routing the AM62L board, a lot of progress was made, it's nearly there https://github.com/tscircuit/tscircuit-autorouter/pull/2247 https://github.com/tscircuit/tscircuit-autorouter/pull/2248 https://github.com/tscircuit/tscircuit-autorouter/pull/2249 https://github.com/tscircuit/tscircuit-autorouter/pull/2250 https://github.com/tscircuit/tscircuit-autorouter/pull/2251 ## Seve — 2026-08-27T15:20:31.170000+00:00 no repro? ## Seve — 2026-08-27T15:20:40.575000+00:00 only the first PR is mergable ## Seve — 2026-08-27T15:20:58.773000+00:00 the remainder are super dangerous ## shibo — 2026-08-27T15:32:58.352000+00:00 I have a repro from my board, but I told it to make the repro as small and focused as possible ## shibo — 2026-08-27T15:33:15.333000+00:00 i'll use the real thing this time ## Seve — 2026-08-27T15:34:18.726000+00:00 yes if i had the result i might know a bit better if this was appropriate, there's no dataset to benchmark on, and we don't have bus routing solved outside of the regular autorouter ## Seve — 2026-08-27T15:34:46.704000+00:00 if you show more evidence then that would help, right now all i see is a bunch of ai generated code ## Seve — 2026-08-27T15:35:17+00:00 and #2248 is a major bug ## Seve — 2026-08-27T15:35:21.798000+00:00 AFAIK ## Seve — 2026-08-27T15:45:39.904000+00:00 also i do appreciate the deep dive into this, i think it is the right method, i do this all the time but i often throw out a bunch because of issues doing review.... it is very hard ## shibo — 2026-08-27T17:18:05.860000+00:00 <@757706909351411845> please check again: https://github.com/tscircuit/tscircuit-autorouter/pull/2248 https://github.com/tscircuit/tscircuit-autorouter/pull/2249 https://github.com/tscircuit/tscircuit-autorouter/pull/2251 ## Seve — 2026-08-27T19:04:40.550000+00:00 2248 is definitely better ## Seve — 2026-08-27T19:05:19.885000+00:00 why does it say AM62L? There is no AM62L in the snapshot? is it confused Attachment: CleanShot_2026-08-27_at_12.05.132x.png — https://community.tscircuit.com/media/1542610987872559125 ## shibo — 2026-08-27T19:17:41.883000+00:00 it's from the hdmi that would get connected to the am62l, context poisoning ig ## shibo — 2026-08-27T19:17:51.848000+00:00 please check the other two: https://github.com/tscircuit/tscircuit-autorouter/pull/2249 https://github.com/tscircuit/tscircuit-autorouter/pull/2251 ## Seve — 2026-08-27T19:36:05.161000+00:00 these are definitely getting better ## Seve — 2026-08-27T19:36:14.951000+00:00 i think minor tweaks and we can start merging ## shibo — 2026-08-27T20:10:47.341000+00:00 <@757706909351411845> https://github.com/tscircuit/tiny-hypergraph/pull/173 https://github.com/tscircuit/tscircuit-autorouter/pull/2248 ## Seve — 2026-08-27T20:16:49.662000+00:00 it seems like you want to make it so that certain connections don't traverse certain zs, `portZ` exists on the GraphTopology https://github.com/tscircuit/tiny-hypergraph/blob/main/lib/core.ts#L90 ## Seve — 2026-08-27T20:18:37.494000+00:00 it seems like you want to modify the `TinyHyperGraphProblem` to add support for specifying `routeAllowedZ` ## Seve — 2026-08-27T20:18:46.658000+00:00 ugh dude i don't think this works ## Seve — 2026-08-27T20:18:53.528000+00:00 like do you have any proof that this works? ## shibo — 2026-08-27T20:19:06.831000+00:00 only that small repro ## Seve — 2026-08-27T20:19:17.384000+00:00 i'm saying ## Seve — 2026-08-27T20:19:23.845000+00:00 that limiting the layer of a bus doesn't make sense ## Seve — 2026-08-27T20:19:44.839000+00:00 because a bus always starts on the top or bottom layer, and sometimes you seek to have it traverse in the middle ## Seve — 2026-08-27T20:20:07.327000+00:00 *traverse without layer changes on a signal layer ## Seve — 2026-08-27T20:20:11.026000+00:00 you have no support for that ## Seve — 2026-08-27T20:20:17.172000+00:00 you only have support for complete restriction ## Seve — 2026-08-27T20:20:32.504000+00:00 even in the infinite cost implementation ## Seve — 2026-08-27T20:20:44.020000+00:00 if you can't show me a fully routed board with your custom autorouter, what's the point? ## Seve — 2026-08-27T20:21:17.393000+00:00 MAYBE layer restriction makes sense, or maybe we use explicit autorouting phases for it ## Seve — 2026-08-27T20:21:18.845000+00:00 idk ## shibo — 2026-08-27T20:21:31.223000+00:00 yeah, you need to prove something is usefull otherwise it may slow us down longterm ## shibo — 2026-08-27T20:21:34.604000+00:00 is that what you're saying ## Seve — 2026-08-27T20:21:36.287000+00:00 but there is a near term performance implicaition ## Seve — 2026-08-27T20:21:42.347000+00:00 yes no matter what we are paying in performance ## Seve — 2026-08-27T20:21:50.428000+00:00 i like this general direction, it might be ok ## Seve — 2026-08-27T20:22:18.930000+00:00 `isPortTransitionAllowed` is being called A LOT, you need to profile this ## Seve — 2026-08-27T20:22:41.245000+00:00 if `isPortTransitionAllowed` is effectively 0 cost, then maybe we merge it through ## Seve — 2026-08-27T20:23:01.474000+00:00 it is a good feature but i have no idea if it's going to get us to the finish line, it is a good feature ## Seve — 2026-08-27T20:23:38.468000+00:00 also stop with the ai generated titles and descriptions for this ## shibo — 2026-08-27T20:23:52.357000+00:00 I found out hdmi bus doesn't need to be in only one layer ## shibo — 2026-08-27T20:23:58.266000+00:00 soo ## Seve — 2026-08-27T20:24:29.892000+00:00 yea it can have transitions, but you need to have the same number of vias on each line generally ## Seve — 2026-08-27T20:24:38.370000+00:00 ideally the same layer changes around the same areas of the board ## Seve — 2026-08-27T20:25:05.040000+00:00 you're doing good i'm just having a hard time reviewing these ## shibo — 2026-08-27T20:27:03.445000+00:00 my issue is that I only focus on getting through the immediate obstacles, I don't think of how these changes would affect the tool as a whole and/or longterm ## Seve — 2026-08-27T20:27:23.491000+00:00 you're fine, they're good implementations ## Seve — 2026-08-27T20:27:31.300000+00:00 it's hard to get this stuff working ## Seve — 2026-08-27T20:27:42.906000+00:00 i'm struggling with managing this because it's hard ## Seve — 2026-08-27T20:28:22.550000+00:00 however the autorouter is swappable via `autorouter={{ algorithmFn: ... }}`, so you may find you're able to use a fork or PR build to route a board and that is particularly interesting ## Seve — 2026-08-27T20:28:48.483000+00:00 yea everyone is struggling to make progress here i think ## shibo — 2026-08-27T20:29:31.543000+00:00 but we are getting meaningful progress don't you think ## shibo — 2026-08-27T20:29:37.200000+00:00 worth trying ## Seve — 2026-08-27T20:29:54.083000+00:00 yes we're seeing improvements