{'fraction_non_alphanumeric': 0.01968503937007874, 'fraction_numerical': 0.004724409448818898, 'mean_word_length': 5.052380952380952, '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}}
Towards transparent distributed execution in the Tornado framework

Tornado is a new advanced kernel for modelling and virtual experimentation (i.e., any evaluation of a model) in the water quality domain. Although primarily intended for use within this particular domain, the kernel is generic in nature and has a plethora of generally applicable features. Tornado often deals with elaborate models and many of its virtual experiment types are computationally intensive. In order to alleviate the computational burden, there is a strong need for distributed execution. However, since Tornado has a heterogeneous user community consisting of both expert and non-expert users, the distributed execution process should preferably be as transparent as possible. This article focuses on the initial steps that were taken along the road to transparent distributed execution. Main achievement so far is the ability to perform semi-automated distributed execution of workload on the Typhoon cluster and LCG-2 grid infrastructures. Our approach is based on the generation of generic job descriptions and has been shown to offer sufficient transparancy for non-expert users in the scope of a Monte Carlo simulation project that was run on a 16-node Typhoon / 40-node LCG-2 setup.