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

Non-schematic projects still try to generate a netlist #54

Open
jwise opened this issue Apr 21, 2024 · 4 comments
Open

Non-schematic projects still try to generate a netlist #54

jwise opened this issue Apr 21, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@jwise
Copy link

jwise commented Apr 21, 2024

It would be nice to be able to use CACE for all sort of circuit characterization, not just magic-flow IC characterization. For instance, there are PCB designs that may have no layout, and testbench designs that have no schematic and only a netlist.

Currently, CACE will try to process a schematic into a netlist (and will fail if it does not), even if a netlist already exists. The desired behavior is that if a netlist exists, and a schematic does not, it should simply attempt to use the netlist that is already there.

@mole99 mole99 added the enhancement New feature or request label Apr 22, 2024
@mole99
Copy link
Member

mole99 commented Apr 22, 2024

I think a workaround for now could be to place an empty schematic with an older timestamp than the netlist. Then CACE should not try to generate a new netlist.

@RTimothyEdwards
Copy link
Collaborator

@mole99 : We did that workaround yesterday; yes, it definitely works to touch an empty schematic and then touch the netlist. But it's an awful hack. The fix is just a few conditionals in the cace_regenerate.py code.

@jwise
Copy link
Author

jwise commented Apr 22, 2024

Yeah, I think my big problem with that is that if the timestamps get out of sync in some way (i.e., I check things into git, and then check them out, or something?), then I would end up with my netlist getting blown away.

@mole99
Copy link
Member

mole99 commented Apr 24, 2024

Hi @jwise, could you check if #56 fixes this for you? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants