In general fault dictionaries can be made any number of ways: by hand, through simulation, or from a tester machine. Sproing is set up to read Nemesis generated fault dictionaries. So any input to Sproing has to be in this specific format (as described in the File Descriptions: Pre-Input file section). Ideally one would feed Sproing tester data, and a composite bridging fault dictionary. A composite bridging fault dictionary usually consists of information from both stuck-at signatures, and information from a bridgeIDDQ dictionary. The IDDQ dictionary is not required, a simple stuck-at dictionary will work fine, but more restricted vectors (see match restriction) are identified through the IDDQ tests.
Up next are examples of stuck-at, bridgeIDDQ, and bridge fault configuration files for Nemesis. But there is a slight conundrum, these files, and the options needed to get Nemesis to generate them, arenít in any official Nemesis documentation. The documentation that exists is useful, and explains much about Nemesis, and itís file formats, in general .Running Nemesis is easy: