Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not require a PDK to be specified in the datasheet. #55

Closed
wants to merge 1 commit into from

Conversation

jwise
Copy link

@jwise jwise commented Apr 21, 2024

Some projects (i.e., PCB or other circuit simulation) do not have a PDK associated with them at all; they will use SPICE primitives, or other SUBCKTs, to do their work. For these projects, there is no need for a PDK key in the config; enable that behavior. This allows CACE to be used without a PDK installed at all.

Some projects (i.e., PCB or other circuit simulation) do not have a PDK
associated with them at all; they will use SPICE primitives, or other
SUBCKTs, to do their work.  For these projects, there is no need for a `pdk`
key in the config; enable that behavior.  This allows CACE to be used
without a PDK installed at all.
@mole99
Copy link
Member

mole99 commented Apr 22, 2024

Thanks for your contribution!
Looks good to me, just needs formatting and it's good to go.

I wonder for how long we will keep/maintain cace_compat, because the JSON format was used before the official release and probably not many datasheets are in this format. Also, there seem to be some deprecated options like foundry in it which I don't see in any of the recent datasheets. But that's for sometime later!

@mole99
Copy link
Member

mole99 commented Apr 30, 2024

@jwise ping

@mole99 mole99 closed this Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants