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

sby doesn't report full path of generated cover trace file names #84

Closed
tudortimi opened this issue Apr 12, 2020 · 2 comments · Fixed by #87
Closed

sby doesn't report full path of generated cover trace file names #84

tudortimi opened this issue Apr 12, 2020 · 2 comments · Fixed by #87
Assignees

Comments

@tudortimi
Copy link

In cover mode, sby prints messages from the engines when a cover trace is available: Writing trace to VCD file: engine_0/trace0.vcd. It's not possible to simply take this name and send it to GTKWave, as the work directory name is missing. User have to add the workdir as a prefix themselves.

Contrast this to prove mode, where the last message in case of a fail is summary: counterexample trace: <workdir>/engine_0/trace.vcd, which contains the full path to the VCD file and can be directly opened in GTKWave.

@ZipCPU
Copy link
Contributor

ZipCPU commented Apr 15, 2020

@tudortimi ,

The primary issue is the difference between the summary trace results and the results of the individual passes from each solve. When run in proof mode, a failure only results in a single VCD file and so it is listed in the summary with it's full path. If you look closer, you'll also see that same VCD file with it's partial path listed above as well, this is the result/output of the solver. When SymbiYosys is run in cover mode, there is no guarantee of a single cover() output--instead there might be many. As an example, one design I'm working with has nearly 300 cover checks. Not having an easy way of generating a cover() summary listing all the successes, cover() doesn't list VCD files upon success.

Dan

@tudortimi
Copy link
Author

I know, but it would still be possible to list all of the generated cover traces at the end. I agree, though, that with a lot of cover properties the list could become pretty big. If this information were dumped into a log file (#79 😉 ), then it would be easier to sift through it.

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 a pull request may close this issue.

4 participants