{'fraction_non_alphanumeric': 0.013972055888223553, 'fraction_numerical': 0.0, 'mean_word_length': 5.783783783783784, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Leveraging IVI for instrument wrapper development

Most Automatic Test System environments create an abstraction layer that sits between the test program and the instruments drivers, a wrapper. This paper provides an overview of existing wrapper implementations, describes the benefits of abstraction layers, primarily to facilitate instrument replacement, and explores using the architecture defined by IVI to implement wrappers. Use of both existing IVI classes and new custom classes are discussed.