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

Result browser gives error message #747

Closed
tband opened this issue Mar 11, 2021 · 9 comments · Fixed by #776
Closed

Result browser gives error message #747

tband opened this issue Mar 11, 2021 · 9 comments · Fixed by #776
Assignees
Labels
Milestone

Comments

@tband
Copy link

tband commented Mar 11, 2021

klayout klayout_debug.gds -m klayout_debug.out
Warning: Obviously reaching end of shapes list before the specified number of shapes was read - parsing next category. (line=578)
ERROR: Expected an unsigned long integer value here: -4000 -242 .. (line=579)

This is a results database from Calibre nmDRC so could it be that the syntax has changed? I've created a small testcase that reproduces the issue. I did limit the rdb to only two results. When I delete the second one, klayout opens normally.

klayout_rdb_issue.tar.gz

@klayoutmatthias
Copy link
Collaborator

Thanks at lot for the test case. I'll take at look at this problem.

@tband
Copy link
Author

tband commented Mar 19, 2021

Let me know if you need more examples. I have a rdb now for which I saved all check results one by one. Some checks fail to load while others just load fine. Can't seem to find what the difference is between the failing and correctly loading ones.
I now use calibredrv as a workaround, but prefer klayout :-)

@klayoutmatthias klayoutmatthias self-assigned this Mar 21, 2021
@klayoutmatthias klayoutmatthias added this to the 0.26.12 milestone Mar 21, 2021
@klayoutmatthias
Copy link
Collaborator

klayoutmatthias commented Mar 22, 2021

@tband I found some time to look into this issue.

Basically I think that there is something wrong with the DB file.

My understanding of the format is this:

XP3004 1000                           # Header + 1/DBU
4XV5.SZ1                              # Check name (Category)
112 112 4 Mar 11 12:19:02 2021        # Number of markers (112), ?, Lines of comment (4), timestamp
4XV5.SZ1 {@ stripped                  # Comment (here: 4 lines) 
    E = NOT A
    E
}
p 1 4                                 # polygon #1 with 4 points
CN XP3004 c 1 0 0 1 0 0 0             # cell name "property"
-100580 -100580                       # points in DBU units
-100180 -100580
-100180 -100180
-100580 -100180
...

But when I look at line 569++, I see this:

IND.WLX
15 15 7 Mar 11 12:19:59 2021                   # 7 lines of comment???
IND.WLX {@ stripped
    E = NOT A
    E
}
p 1 70
CN match_balun_2t1t1t3t c 0 1 -1 0 314295 42060 1
-6895 -14240
-4000 -14240
-4000 -24230
...

Which is somewhat inconsistent. There are 4 lines of comment. That's why the reader reads 7 lines and comes out at the wrong place.

What tool is generating this file? Maybe there is something wrong there?

Kind regards,

Matthias

@tband
Copy link
Author

tband commented Mar 24, 2021 via email

@klayoutmatthias
Copy link
Collaborator

I don't see the image :(

@tband
Copy link
Author

tband commented Mar 27, 2021

image
I replied to the mail. Apparently the images gets scrubbed.

@klayoutmatthias
Copy link
Collaborator

Hi,

Lines starting with // should alread be skipped automatically (#522). This went into 0.26.6. So you mean you just delete the two lines starting with // and everything works?

That's basically what the reader does by itself. Are you using a version later than 0.26.6?

Thanks,

Matthias

@tband
Copy link
Author

tband commented Apr 18, 2021 via email

@klayoutmatthias
Copy link
Collaborator

klayoutmatthias commented Apr 18, 2021

I see, thanks for the information.

This basically means that the fix of #522 is not applicable. Originally, the problem was a Tanner specific one. So maybe Tanner has a different opinion about how to read RVE files. Or rather the dropping of comment lines should not happen inside the description text.

@klayoutmatthias klayoutmatthias linked a pull request Apr 18, 2021 that will close this issue
klayoutmatthias added a commit that referenced this issue Apr 19, 2021
No comment skipping in descriptions - fixed #747
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants