{'fraction_non_alphanumeric': 0.018002322880371662, 'fraction_numerical': 0.0005807200929152149, 'mean_word_length': 5.1535714285714285, '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}}
The fused fault block approach to fault network modelling

Abstract Fault network modelling of complex faulted structures, those containing hundreds or even thousands of faults, can be an extremely difficult and time-consuming process. Although techniques for mapping and modelling faulted structures have been in existence for nearly forty years, asset teams still struggle to create correct portrayals of such complex faulted reservoirs due to the limitations of the commonly used techniques. We have developed a new approach to fault network modelling, using a new concept of ‘fused’ fault blocks. The identification of fault–fault intersections is based not on a manually drawn fault network or table of relationships, but rather is derived from the fault surfaces themselves. The calculated intersection lines are then used to truncate faults against each other. Because the truncation information can be stored with the fault model, this process yields a repeatable and easily updatable fault model. The name of our technique ‘fused fault blocks’ refers to the fact that when a section of a fault is removed, the two fault blocks that had been created by the fault are then fused together, forming a single fault block. The resultant fault model can then be used to create a 3D reservoir grid, one in which the fault geometry has not been compromised, and therefore better reflects the actual structure. The speed of the fault-building process ‘seconds or minutes, even for models with hundreds of faults’ also allows multiple interpretations, placing the emphasis of the fault network building on the evaluation of the interpretation and the effects of compartmentalization, and not on the manipulation of software.