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

Prevent concurrent runs from interfering with one another #38

Closed
infinitymdm opened this issue Apr 24, 2024 · 2 comments
Closed

Prevent concurrent runs from interfering with one another #38

infinitymdm opened this issue Apr 24, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@infinitymdm
Copy link
Collaborator

infinitymdm commented Apr 24, 2024

Concurrent characterization runs using the same config file currently write out results to the same filename, overwriting previous results. This means that the results of all but the final characterization run are entirely lost. Provide a mechanism to allow the results of concurrent runs to be written to different paths.

(There may also be an issue here re. ngspice, as the ngspice-shared PySpice backend uses a singleton for the ngspice instance. This may take some looking into, or it might be a non-issue.) This is not a problem.

@thesourcerer8
Copy link
Contributor

From my point of view, we need the possiblity to just specify a single .yml file (which contains a single cell) on the commandline. I currently dont see a need to run several characterizations concurrently for the same cell.

@infinitymdm
Copy link
Collaborator Author

This should have been closed with #41; not sure why it didn't automatically close. You can specify where you want the output liberty file with the -o switch, and cells can be selected either by a) specifying a path to a config file with just the cells you want or b) using the -f switch to filter a larger yaml file for the cells you want to run.

This issue was closed.
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

No branches or pull requests

2 participants