How to provide test set files?

[claudiolorini]

Hello Dominik,

i've downloaded your code, compiled and executed 'build_and_test.sh', (no error messages received)
and tried to run it for one of my orcad projects (see attachment):

../build/cli/OpenOrCadParser-cli -i SE_PAC_00.DSN -e -0 . -v

i see that things happens but i'm not able to understand if the results are meaningful.
I have a lot of projects designed with orcad, how can i provide some of them as a test set?

SE_PAC_00.DSN.zip

C.

[Werni2A]

Hi Claudio, you are probably the first one testing this project in real life. I really appreciate any new test files since the whole project requires them for verification purposes.

You can provide them by

1. Create a new GitHub repository or use an existing one
2. Upload your files
3. That's basically it on your side
4. I will fork your repository and add it to the repos.yaml file
5. New test runs will automatically check results against your designs

I should probably add a page to the documentation describing this process in more detail.

I will take a look if SE_PAC_00.DSN.zip already works or fails and let you know. The CLI tool prints the information it parses from the binary files to the terminal. This is not very useful for most users. You could redirect the output to a file and check for errors or information you want to process yourself. In the long term I want to implement an importer for KiCad but I haven't started it yet. Until then the only thing you can do is parse the output text file or link against the library and process it in you own software.

[claudiolorini]

i've placed some test bench files here:

https://github.com/claudiolorini/OOPTB

[Werni2A]

@claudiolorini Thank you. I incorporated your files into the next PR. I took a closer look into TB9.DSN. There are a few issues related to packages with the suffix _pDboPackage_Copy_0000. Do you remember if you created the schematic and symbols from scratch in the OrCad version you used? Or rather reused symbols from older designs? I guess that these _pDboPackage_Copy_0000 packages are temporary copies of old packages before they get converted to later file format versions. I've seen this naming a lot in the last days. The old file format is not supported yet, therefore I could understand the failure but I'm not sure yet.

BTW. this string is so unique that search engines find desings/libraries pretty accurately. Though one needs a search engine that indexes binary files. E.g. https://duckduckgo.com/?t=ffab&q=%22pDboPackage_Copy%22&ia=web

Google does not work and I'm not sure about others. But that is a nice way of finding new test designs.

[claudiolorini]

we currently use v16.6, all tb files should be not newer than that.
It's very likely the designs contains lots of stuff copied from other designs, but since is very old stuff i can't remember exactly.

[Werni2A]

95 files out of 139 files that are included in SE_PAC_00.DSN are processed correctly. This however, does not indicate that the meaning of every bit is known. The rest fails somewhere due to features that are not yet implemented in the parser and misinterpreted data.

If you are willing to help out, you can check which parts fail by searching for ERROR REPORT in the text file and check if this part uses something special compared to others. E.g. at the moment only homogeneous parts are supported, heterogeneous will fail. Knowing which feature might be missing is a huge time safer. You could also check the correctness of the parsed information by comparing it against the OrCad settings.

PS I ran ./build/cli/OpenOrCadParser-cli -i ../SE_PAC_00.DSN -v >> SE_PAC_00.txt