{'fraction_non_alphanumeric': 0.012440191387559809, 'fraction_numerical': 0.0, 'mean_word_length': 5.496894409937888, '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}}
Is comprehensive and intuitively usable commissioning software feasible?

The commissioning period is challenging both for provider and user of accelerator operation software. With increasing knowledge of the specific accelerator new functionalities and methods become important. The variety of implemented features grows until certain standard procedures are settled and the programs can be simplified again for the all day tasks. It is not too difficult to provide the requested functionalities and certain handles for a graphical usage for expert users. For the general member of the commissioning crew, however the GUI may consist of huge windows, context dependent presentations, hierarchically structured menu trees or compact screens dominated by (modifier) key and mouse click navigation. Understanding and usability of the programs tends to decrease with the increase of available features. By means of examples like the orbit display and control program the problem is outlined and some guidelines leading out of the dilemma are given.