← Back to community index
# contributor·Active

Techmannih - @Seve Should keepouts be drawn usi...

mention Should keepouts be drawn using the courtyard? courtyard rect already supported.

Started by techmannihDec 24, 202596 messages

Discussion

Last active 20 hours ago · plain text
techmannihoriginal post
<@757706909351411845> Should keepouts be drawn using the courtyard? courtyard-rect already supported.
techmannih
Do also need to add support for courtyard-outline and courtyard-polygon?
Seve
Yep courtyard works, we don’t need polygon yet
techmannih
https://github.com/tscircuit/circuit-to-svg/pull/464
techmannih
👉 Nothing is allowed inside a keepout area. ❌ Don’t place tracks ❌ Don’t place copper ❌ Don’t place vias ❌ Don’t place other components
techmannih
<@757706909351411845> https://github.com/tscircuit/circuit-to-canvas/pull/100 https://github.com/tscircuit/core/pull/1814
techmannih
it should be represent in between the pads/ holes?
techmannih
it is looks same in cts right now
Seve
well you should make a proper snapshot test then
Seve
there are plenty of tests that show circuit-to-svg as well
techmannih
yea
Seve
better but you're not supposed to have a dashed border
Seve
yea like that but also a slight transparent red
Seve
as the background
techmannih
cool
Seve
yep
techmannih
<@757706909351411845> https://github.com/tscircuit/props/pull/550 https://github.com/tscircuit/core/pull/1818
techmannih
<@757706909351411845> do not need for pullup and pulldown properties to jumperProps. for this issue? https://linear.app/tscircuit/issue/TSC-277/pullupfor-pullupto-pulldownfrom-pulldownto-for-jumpers-same-as
Seve
there is an issue in the spec, it is technically solvable but i'm cancelling
techmannih
<@757706909351411845> https://github.com/tscircuit/pcb-viewer/pull/592
Seve
I added abse to the review
Seve
i'm not sure?
Seve
depends on how kicad styles bottom silkscreen
Seve
open it in kicad
techmannih
yes
Seve
Check kicad but probably not supposed to be filldd
techmannih
yes sure
Seve
Just open kicad
Seve
Create a courtyard
Seve
Probably is not filled
techmannih
okay
techmannih
true this is not filled
Seve
stroke_width shouldn't exist on pcb_courtyard_outline
Seve
neither should is_stroke_dashed or is_closed
Seve
or color
techmannih
yep
techmannih
i am removing them
techmannih
https://github.com/tscircuit/circuit-json/pull/456
techmannih
<@757706909351411845> i m missing merge access in circuit-json
Seve
merged
Seve
i don't know what you mean because none of these images are labeled
techmannih
in the snapshots of KiCad and circuit-json. In circuit-json, we are using the top courtyard, but in KiCad the bottom courtyard color is being rendered.
Seve
<@1067854999889137715> open excalidraw and annotate the images like so:
Seve
i still don't understand, but if you think it's a real bug you can go directly to PR of course- but it is important to communicate concretely
techmannih
yes there is one more issue in the kicad bottom courtyard is top of top layer courtyard
techmannih
yes and in this snapshot looks like we are using the top courtyard, but in KiCad the bottom courtyard color is being rendered
Seve
<@1067854999889137715> i literally don't know what you're saying- we had this discussion already- i do not know what you're talking about because i do not have the full context of what you have done or seen. _ANNOTATE THE SCREENSHOTS_
Seve
you're saying that blue, in kicad, represents bottom courtyard? So then our top courtyard becomes a bottom courtyard? Yes that seems like a bug
techmannih
Yes — I’m saying that
techmannih
I’ve figured it out now — this isn’t the original issue we thought it was. The actual problem is a layer ordering issue: the bottom courtyard is being rendered above the top courtyard. Because of this, it appears like a courtyard mismatch, but it’s not a color or mapping issue.
techmannih
<@757706909351411845> The courtyard is not working in the docs. Is there any dependency issue? I added support for it everywhere almost 4 days ago. https://github.com/tscircuit/docs/pull/436
Seve
Write a test in the svg.tscircuit.com rrpo
techmannih
https://github.com/tscircuit/svg.tscircuit.com/pull/978
Seve
this should be easy to fix now
techmannih
Can you check it now I have updated https://github.com/tscircuit/docs/pull/764
techmannih
<@757706909351411845> A user created some issue. do we need to take action on them
Seve
Idk evaluate if theyre valid
Seve
We should always examine user reported issues if theyre not slop, that guy is legit
techmannih
exactly yea, I checked his profile. he seems like a good open-source contributor
techmannih
can you check it https://github.com/tscircuit/circuit-json-to-kicad/pull/373 https://github.com/tscircuit/core/pull/2625
techmannih
updated, can you check now
techmannih
<@757706909351411845>
techmannih
These both are the user issue. I add the reference of issue
techmannih
Can you check it https://github.com/tscircuit/core/pull/2631 https://github.com/tscircuit/circuit-json-to-kicad/pull/375
techmannih
Can you check it now https://github.com/tscircuit/core/pull/2631
techmannih
Updated
techmannih
Can you check it now
techmannih
<@757706909351411845> https://github.com/tscircuit/ti/pull/68 we need your suggestion, can you check it
techmannih
https://github.com/tscircuit/easyeda-converter/pull/407 trying to fix easyeda issue, can you check it also
Seve
<@1067854999889137715> unrelated but we discussed figuring out footprinter strings from jlcpcb imports- we still need that- the codebase has massive footprints
techmannih
yea we can use as footprint string footprint="jlcpcb:C44346038"
Seve
<@1067854999889137715> that's not what i mean. We're supposed to automatically derive a footprinter string from jlcpcb footprints via IoU matching
techmannih
yea we have so many different ways to do the same thing that I completely forgot about this one.
techmannih
there's still some work left on this. we still need to automatically load it using AI so it can suggest the closest matching footprinter string from JLCPCB. I'll take a look into that as well.
techmannih
Sorry Sorry we keep getting high priority work, especially TI-related tasks schematic and important fixes, so sometimes things get pushed back
techmannih
BTW we can use qfn40,
Seve
https://github.com/tscircuit/fast-footprint-compare/pull/3
techmannih
Boom 💥
techmannih
Then name should be discover from footprinter. I think?
Seve
? Wdym
techmannih
It should be discover from footprinter?
Seve
Why would we want that, what would that do?
techmannih
I think discovering the footprint string from footprinter which should closely match with jlcpcb part no
Seve
Why would anyone want that
Seve
Please put yourself into the mindset of a user
Seve
Why would anyone want that
Seve
Or youre communicating extremely poorly

Want to add to the conversation?

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