A method for zoning and repairing a mine slope area
Patent Information
- Application Number
- CN202610930522.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-26
- Publication Date
- 2026-10-20
AI Technical Summary
[0003]在这种分区并存、相互拼接的治理格局下,矿山边坡地区暴露出一个难以忽视的技术问题,即碎石滩专用生态修复结构在与相邻裸岩边坡或回填区的拼接界面处,缺乏专门面向界面的分区划分和构造布置方法,现有技术多仅针对碎石滩自身给出治理结构,而对其与周边分区的过渡带如何划分、如何统一设计并无系统规范
本发明公开一种矿山边坡地区的分区修复治理方法,通过识别碎石滩分区与相邻裸岩边坡分区或回填体分区的边界生成界面原始数据,并按坡面类型差异与高程关系划分界面模式,构建界面分区单元;再以界面模式为索引从界面规则库中选取对应修复方案,形成包含修复构造参数与预期表现的界面修复计划;在运行阶段对各界面进行稳定性与排水能力观测,形成实际表现并与预期表现比较,在界面模式层级更新修复目标与构造参数,同步反馈至界面规则库和修复计划,实现界面修复方案的迭代优化;本方法解决不同分区交界处修复结构不连续的问题,提高界面带稳定性、排水连续性及长期修复可靠性。
Smart Images

Figure REF-OBJ-1782390887189-000002
Abstract
Description
Technical Field
[0001] This invention relates to the field of ecological restoration engineering technology, and more specifically, to a method for zoned restoration and management of mine slope areas. Background Technology
[0002] In existing mine slope management practices, for scree slopes—special slopes formed by the long-term accumulation of boulders and gravel—green mine slope scree slope management and ecological restoration schemes have been proposed. These schemes improve the stability and landscape effect of such slopes by reshaping the scree piles, laying ecological substrates, and planting suitable vegetation. Meanwhile, other slope types within the same mine slope area are typically treated with different restoration methods. For example, exposed rock faces may be anchored, shotcreted, and seeded with vegetation; backfilled slopes may be trimmed, shaped, and protected with geotechnical engineering. Consequently, within the same mine slope area, multiple zones often coexist, including scree slope ecological restoration zones, exposed rock slope support zones, and backfill remediation zones. These zones are spatially interconnected, especially at the junctions between the scree slope and the adjacent exposed rock slope or backfilled slope, creating numerous demarcation zones.
[0003] Under this governance pattern of coexisting and interlocking zones, a significant technical problem has emerged in mine slope areas: the lack of specific zoning and structural layout methods for the ecological restoration structure of scree slopes at the interface with adjacent bare rock slopes or backfill areas. Existing technologies mostly only provide governance structures for the scree slopes themselves, without systematic specifications for how to divide and uniformly design the transition zone between them and surrounding zones. This results in the fact that although various functional and restoration zones are arranged on a planar scale, the restoration layer often fails to form a continuous and consistent structure and drainage system at the boundary between the scree slope zone and other zones. The stability and durability of the interface zone cannot be effectively guaranteed by existing zoning methods, becoming a weak link restricting the overall effectiveness of zoned restoration and governance in mine slope areas.
[0004] To address the aforementioned problems, a technical solution is provided. Summary of the Invention
[0005] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a method for zoned restoration and management of mine slope areas. This method generates raw interface data by identifying the boundaries between gravel beach zones and adjacent zones. Interface patterns are then defined and interface zoning units are constructed based on slope type combinations and elevation relationships. Interface restoration schemes are selected from an interface rule base using these interface patterns as indexes, forming an interface restoration plan that includes structural parameters and expected performance in stability and drainage capacity. During the operational phase, interface stability and drainage are monitored to generate actual performance, which is then compared with expected performance. Restoration targets and structural parameters are updated based on the interface patterns and synchronously fed back to the interface rule base and interface restoration plan, enabling continuous optimization of the interface restoration scheme to address the problems mentioned in the background art.
[0006] To achieve the above objectives, the present invention provides the following technical solution: S1, identify the boundary between the scree beach zone and other zones, generate the original interface data based on the slope type and elevation relationship on both sides of the boundary, and assign an interface number to each boundary. S2. Based on the differences in slope type and elevation relationship reflected in the original interface data, the interface numbers with the same characteristics are clustered into interface patterns. The interface patterns are used to divide the interface partition units and inherit the original interface data. S3 uses the interface mode as the search condition, automatically selects the corresponding interface repair scheme from the interface rule base, writes the interface repair scheme into each interface partition unit to form an interface repair plan and records the expected performance. S4. Record the operation of the interface partition unit according to the interface repair plan, compare the recorded results with the expected performance of the interface mode in the interface repair plan, adjust the corresponding interface repair scheme for inconsistent interface modes, and update the interface rule base and interface repair plan in sync.
[0007] Furthermore, in step S1, when identifying the boundary between the scree slope zone and other zones, the contact lines between the scree slope zone grid and the adjacent bare rock slope zone grid and backfill zone grid in the digital terrain model of the mine slope are extracted. Each contact line is determined as a boundary, and the vertex coordinate sequence of the boundary polyline, the slope type code on both sides, and the elevation value of the corresponding vertex are recorded along the boundary. At the same time, a unique interface number is generated for each boundary and written into the interface original data record.
[0008] Furthermore, in step S1, in order to generate the original interface data, the following steps are also included: based on the elevation of the vertices on both sides of each boundary, calculate the average elevation of the scree beach side and the average elevation of the other partition side respectively, form the overall elevation difference between the two, and divide the overall elevation relationship of the boundary into three states: upstream side is above, both sides are at the same height, and upstream side is below, according to the elevation change trend along the boundary direction. At the same time, according to the elevation change trend along the boundary direction, divide the elevation gradient into three states: overall rising, overall horizontal, and overall falling, and store the two types of state values together in the original interface data.
[0009] Furthermore, in step S2, when clustering interface numbers into interface patterns, an ordered feature group is formed by the slope type code on the gravel beach side, the slope type code on the other side, the overall elevation relationship status value, and the elevation gradient status value in the original interface data corresponding to each boundary. Interface numbers with identical feature groups are merged into the same interface pattern, and a unique interface pattern number is assigned to each different feature group. At the same time, the interface pattern number and the interface number are stored together in the interface partition unit to establish a one-to-one correspondence.
[0010] Furthermore, in step S3, when constructing the interface rule base, a rule base record is set for each interface mode number. The rule base record includes at least the interface repair scheme identifier corresponding to the interface mode number, the mode layer stability target index, the mode layer drainage capacity target index, and the repair construction parameter combination. When executing step S3, the corresponding rule base record is retrieved from the interface rule base using the interface mode number as an index. The interface repair scheme identifier and repair construction parameter combination in the record are written into the interface partition unit with the same interface mode number to form an interface repair plan unit.
[0011] Furthermore, in step S3, when recording the expected performance, for each interface repair plan unit, the stability target index and drainage capacity target index of the mode layer in the interface rule base are read and combined with the elevation gradient of the interface. The expected performance of stability is obtained by reducing the mode layer stability target index according to the monotonically decreasing ratio when the absolute value of the elevation gradient increases, and the expected performance of drainage capacity is obtained by amplifying the mode layer drainage capacity target index according to the monotonically increasing ratio when the absolute value of the elevation gradient increases. These are written into the interface repair plan unit together with the interface repair scheme.
[0012] Furthermore, in step S4, when recording the operation of the interface partition unit, a batch number of the operation record is set for each interface repair plan unit in ascending order of integers. In each batch, stability observations and drainage observations are collected. Within the same interface mode, the minimum and maximum values of stability observations and drainage observations of all observation batches are statistically analyzed. The stability observations and drainage observations of the current batch are converted into actual stability performance indicators and actual drainage capacity performance indicators in a linear ratio where the minimum value corresponds to zero and the maximum value corresponds to one, and then stored in the operation record.
[0013] Furthermore, in step S4, when comparing the recorded results with the expected performance in the interface repair plan, first at the interface repair plan unit level, the stability deviation is obtained by subtracting the corresponding expected stability performance from the actual stability performance index of each batch, and the drainage capacity deviation is obtained by subtracting the corresponding expected drainage capacity performance from the actual drainage capacity performance index of each batch. Then, at the interface mode level, the arithmetic mean of the stability performance index and drainage capacity performance index of all interface repair plan units belonging to the same interface mode and all participating batches is calculated respectively to obtain the corresponding mode layer stability performance average and mode layer drainage capacity performance average.
[0014] Furthermore, in step S4, when adjusting the interface repair scheme for inconsistent interface modes, in the stability direction, the original mode layer stability target index and the average value of the actual stability performance of the mode layer are arithmetically averaged to obtain a new mode layer stability target index. In the drainage direction, the original mode layer drainage capacity target index and the average value of the actual drainage capacity performance of the mode layer are arithmetically averaged to obtain a new mode layer drainage capacity target index. Based on the difference between the original target index and the average value of the actual performance of the mode layer, stability adjustment coefficients and drainage adjustment coefficients are constructed. The stability-related parameter groups and drainage-related parameter groups in the repair construction parameter combination are amplified or reduced by a uniform ratio to generate a new repair construction parameter combination.
[0015] Furthermore, in step S4, when synchronously updating the interface rule base and interface repair plan, the mode layer stability target index and mode layer drainage capacity target index in the rule base record corresponding to each interface mode are replaced with new mode layer target indices. The repair construction parameter combination in the record is replaced with new repair construction parameter combination. The repair construction parameter field of all interface repair plan units with the same interface mode number is synchronously replaced. At the same time, according to the established expected performance calculation relationship in step S3, the expected stability performance and expected drainage capacity performance are recalculated with the new mode layer target index and interface elevation gradient, and the original expected performance fields are overwritten to form an updated interface repair plan set for use in the next round of operation records.
[0016] The technical effects and advantages of the zonal restoration and management method for mine slope areas proposed in this invention are as follows: This invention discloses a method for zoned restoration and management of mine slopes. It generates raw interface data by identifying the boundaries between scree slope zones and adjacent bare rock slope zones or backfill zones, and constructs interface zoning units by dividing the interface patterns according to differences in slope type and elevation relationships. Then, using the interface patterns as indexes, corresponding restoration schemes are selected from an interface rule base to form an interface restoration plan containing restoration structural parameters and expected performance. During the operational phase, the stability and drainage capacity of each interface are observed, and the actual performance is compared with the expected performance. The restoration goals and structural parameters are updated at the interface pattern level and synchronously fed back to the interface rule base and restoration plan, achieving iterative optimization of the interface restoration scheme. This method solves the problem of discontinuous restoration structures at the boundaries of different zones, improving the stability of the interface zone, drainage continuity, and long-term restoration reliability. Attached Figure Description
[0017] Figure 1 This is a schematic flowchart of a method for zoned restoration and management of mine slopes according to the present invention. Detailed Implementation
[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0019] Example 1: Figure 1 This invention provides a method for zoned restoration and management of mine slope areas, comprising: S1 identifies the boundaries between the scree beach zone and other zones, generates raw interface data based on the slope type and elevation relationship on both sides of the boundary, and assigns an interface number to each boundary.
[0020] S2, based on the differences in slope type and elevation relationship reflected in the original interface data, cluster the interface numbers with the same characteristics into interface patterns, divide the interface partition units by interface patterns and inherit the original interface data.
[0021] S3 uses the interface mode as the search condition, automatically selects the corresponding interface repair scheme from the interface rule base, writes the interface repair scheme into each interface partition unit to form an interface repair plan, and records the expected performance.
[0022] S4. Record the operation of the interface partition unit according to the interface repair plan, compare the recorded results with the expected performance of the interface mode in the interface repair plan, adjust the corresponding interface repair scheme for inconsistent interface modes, and update the interface rule base and interface repair plan in sync.
[0023] During long-term mining and backfilling processes, several restoration zones have formed on the slopes of mines, including gravel beach slope zones, bare rock slope zones, and backfill slope zones. Each zone already possesses relatively complete restoration measures within its area; for example, the gravel beach zone is equipped with ecological substrates and vegetation structures, the bare rock slope zone with anchoring and shotcreting, and the backfill slope zone with slope trimming and geotechnical protection. These three types of zones are spatially connected by boundary lines, forming a real interface zone between the gravel beach zone and the upper bare rock slope zone or the lateral backfill slope zone. The stability and drainage behavior of this interface zone are controlled by both the slope types on both sides and the elevation relationship between them. A complete description of the interface structure cannot be provided solely based on the restoration structure within a single zone. To provide a foundation for subsequent interface pattern clustering and interface restoration rule retrieval, step S1 requires establishing complete raw interface data within the mine slope area, including interface geometry, interface number, the combination of slope types on both sides of the interface, and the elevation relationship between the two sides of the interface.
[0024] Therefore, step S1 uses slope units as the basic data carrier. Through a series of processes such as slope unit division and attribute organization, slope unit adjacency determination, interface boundary element construction, interface boundary line aggregation and numbering, slope type statistics on both sides of the interface, elevation representative value calculation, elevation difference and elevation gradient calculation, and interface original data unit construction, the boundary lines that were originally only expressed at the partition outline level are transformed into calculable and categorizable structured data at the interface level, providing a continuous and reliable data chain for subsequent steps.
[0025] A1 Slope Unit Division and Basic Attribute Compilation.
[0026] First, a Cartesian coordinate system is established within the restoration area of the mine slope, using the entire restoration area as the calculation region. The calculation region is then divided into several interconnected slope units, each representing a slope segment with a finite range in planar dimensions and finite elevation variations. The planar dimensions of the slope units are determined through analysis of digital elevation data and on-site topographic features. This ensures that the elevation and slope variations within each slope unit can be described by a single representative value in engineering analysis, avoiding the need to cross a complete topographic step or obvious slope break, thus giving subsequent calculations engineering significance.
[0027] For each slope unit, record four types of basic data items: The first type of data item is the planar coordinates of the slope element center, that is, the coordinate values of the center point in the horizontal and vertical directions. The position of the center point can be calculated by averaging the coordinates of the vertices of the polygon surrounding the slope element, or it can be given directly by regular mesh generation.
[0028] The second type of data item is the representative elevation value of the slope unit. To obtain this representative value, several elevation sampling points are set up within the slope unit, and the elevation measurement values of each sampling point are read. The elevation values of all sampling points are summed, and then the summation result is divided by the number of sampling points to form the representative elevation value of the slope unit. This allows the representative elevation value of the unit to comprehensively reflect the elevation status within the unit, rather than the local status of a single measuring point.
[0029] The third type of data item is the slope type code. Based on the engineering properties of the slope surface, an integer code is assigned to mark the type. For example, a gravel beach slope has code one, a bare rock slope has code two, and a backfill slope has code three. If other special engineering slope types exist, the code values can be further expanded. The slope type code describes the engineering structural attributes of the slope unit and is not entirely consistent with the management and division of the restoration zones.
[0030] The fourth type of data item is the repair partition marker. The repair partition marker uses an integer to represent the partition affiliation; for example, the gravel beach repair partition is marked as one, and any other repair partition is marked as zero. This marker allows for clear differentiation between gravel beach repair partition units and other repair partition units in subsequent steps.
[0031] By dividing the slope into units and organizing the basic attributes, each location in the mine slope area is mapped to a slope unit with clear coordinates, representative elevation values, slope type codes, and repair zone markers, providing a data foundation for subsequent identification of the interface between the scree slope zone and other zones.
[0032] Determining the Adjacency Relationship of Slope Elements and Constructing Interface Boundary Elements for A2 Slope Surfaces.
[0033] After obtaining the geometric contours and basic properties of all slope elements, it is necessary to identify the spatial adjacency relationships between slope elements to provide a basis for constructing interface boundary elements.
[0034] First, a closed polygon boundary is defined for each slope element, consisting of several vertices connected end-to-end in sequence. Then, an adjacency table is constructed, using all slope element numbers as rows and columns. For any two different slope elements, if their boundary polygons share a common boundary segment, and this common segment is not a single point but a segment with actual length, then they are recorded as adjacent in the adjacency table. If they only touch at one point or do not touch at all, they are recorded as non-adjacent in the corresponding position.
[0035] After determining the adjacency relationship, an interface boundary element between the scree beach restoration zone and other restoration zones can be constructed based on the adjacency relationship table and the restoration zone marker. Specifically, all slope unit pairs are traversed. When the restoration zone marker of one slope unit is scree beach and the restoration zone marker of the other slope unit is other zones, and both are recorded as adjacent in the adjacency relationship table, an interface boundary element is defined on their common boundary segment.
[0036] Each interface boundary element needs to record the following: First, the slope element number, corresponding slope type code, and representative elevation value on one side of the scree slope restoration zone. Second, the slope element number, corresponding slope type code, and representative elevation value on the other side of the restoration zone. Third, the coordinate values of the two endpoints of the common boundary segment in the plane coordinate system. Fourth, the length of the common boundary segment. The segment length is calculated by the distance between the two endpoints. The calculation involves first finding the difference between the two endpoints in the horizontal and vertical coordinates, squaring each difference, summing the sums, and then taking the square root of the sum to obtain the actual length of the common boundary segment.
[0037] Through the above steps, all common boundary segments between all gravel beach restoration zone slope units and other restoration zone slope units are converted into a set of interface boundary elements, with each interface boundary element corresponding to a real zone boundary segment.
[0038] A3 Interface Boundary Element Connectivity Aggregation and Interface Boundary Line Numbering.
[0039] The interface boundary element set only reflects single line segment information. In order to obtain interface objects that are continuously unfolded in space, it is necessary to aggregate the interface boundary elements that are connected to each other into interface boundary lines according to their connectivity, and to number each interface boundary line.
[0040] The specific method involves organizing the endpoint coordinates of all interface boundary elements into an endpoint set, treating each endpoint as a node in the graph structure, and each interface boundary element as an edge connecting two nodes. Any two interface boundary elements sharing an endpoint are considered to belong to the same connected cluster in a connectivity sense. By traversing all interface boundary elements and endpoint nodes, several connected clusters can be identified, each corresponding to a continuous or polygonal interface boundary line.
[0041] For each connected cluster, the endpoints of each boundary element are arranged sequentially along the line to form a sequence of vertices of a polygonal line. This polygonal line is a boundary line. The total length of the boundary line is formed by adding the lengths of the line segments of all the boundary elements that constitute the boundary line. In this way, each boundary line has a definite geometric shape and total length.
[0042] To facilitate retrieval using interface numbers in subsequent steps, all interface boundary lines need to be sorted and assigned unique numbers. The sorting rule is as follows: for each interface boundary line, select the point with the smallest vertical coordinate value from all its polyline vertices as the starting point. If multiple vertices have the same vertical coordinate value, select the vertex with the smallest horizontal coordinate value from these vertices as the starting point. Then, arrange all interface boundary lines in ascending order of their starting point vertical coordinates. When two interface boundary lines have completely identical starting point vertical coordinates, arrange them in ascending order of their starting point horizontal coordinates. After sorting, assign interface numbers from one to the total number of numbers in the sorting order. Each number corresponds to a unique interface boundary line.
[0043] Through this process, the original set of interface boundary elements, which consisted of several discontinuous line segments, was transformed into several continuous interface boundary lines. Each interface boundary line has a clear number, a sequence of polyline vertices, and a total length, providing a basis for the next step of statistically analyzing slope type and elevation data at the interface level.
[0044] Construction and quantity statistics of slope unit sets on both sides of the A4 interface.
[0045] Geometrically, the interface boundary line is composed of multiple interface boundary elements, each corresponding to a slope unit in a scree slope restoration zone and a slope unit in another restoration zone. To calculate representative slope types and elevations at the interface level, it is necessary to first summarize the set of slope units on both sides of each interface boundary line that participate in the interface formation.
[0046] For each interface boundary line, read all interface boundary element numbers belonging to that boundary line. Summarize the scree slope unit numbers recorded in these interface boundary elements, remove duplicates, and form a scree slope unit set. Summarize the other slope unit numbers recorded in the same batch of interface boundary elements, remove duplicates, and form a set of other slope units.
[0047] For the scree slope unit set, the number of slope units contained within it is counted. This number represents the number of slope units participating in the interface formation on the scree slope restoration zone side within the boundary line. Similarly, the number of units is counted for slope unit sets on other restoration zones side, representing the number of slope units participating in the interface formation on the other restoration zones side within the boundary line. Since the boundary elements are constructed from pairs of adjacent slope units, the number of units in both sets is greater than zero.
[0048] Through this process, each interface boundary line obtains a set of gravel beach side slope units and a set of other repair zone side slope units, as well as the corresponding quantity statistics, providing a complete set of objects for type statistics and elevation calculation on both sides of the interface.
[0049] The slope type on both sides of the A5 interface represents the code.
[0050] The interface repair scheme needs to be selected based on the combination of slope types on both sides of the interface. Therefore, a single code is needed at the interface level to represent the representative slope type near the interface zone on each side. To this end, the occurrence frequency of each slope type code is counted for each interface boundary line in the scree slope unit set and the slope unit set of other repair zones.
[0051] First, determine the complete set of all possible slope type codes. For example, code 1 represents a scree slope, code 2 represents a bare rock slope, code 3 represents a backfill slope, and the remaining codes are reserved for other engineering slope types. Within the scree slope unit set, count the number of slope units with each slope type code. Specifically, iterate through the scree slope unit set, read the slope type code for each slope unit, and record the cumulative count for each code to form the type count distribution on the scree slope side of the interface boundary line.
[0052] After obtaining the distribution of the number of occurrences of different slope types, the slope type code with the highest frequency is selected as the representative slope type on the scree slope side. If two or more codes have the same number of occurrences and both reach the maximum value, the code with the lowest value is selected as the representative slope type code.
[0053] The same statistical method is used in the slope unit sets of other repair zones. The slope type codes of each slope unit are categorized and counted to form the type frequency distribution of the other repair zones along this interface boundary line. Similarly, the code with the highest frequency is selected as the representative slope type code. When multiple codes have the same frequency and are all at the maximum value, the code with the lowest value is selected as the representative slope type code for that side.
[0054] Through this statistical process, each boundary line corresponds to two sides that obtain a unique representative slope type code. In this way, each interface can be described at the type level by a pair of integer codes, such as scree slope side as scree slope code one, other sides as bare rock slope code two, or other combinations, providing a discrete attribute basis for subsequent interface pattern division.
[0055] Calculation of the representative elevation values and elevation difference on both sides of the A6 interface.
[0056] The stability and drainage behavior of the interface zone are not only related to the slope type, but also closely related to the vertical elevation relationship between the scree slope side and other restoration zone sides. Therefore, it is necessary to calculate a representative elevation value for both sides at the interface level and obtain the elevation difference accordingly.
[0057] For each boundary line, the representative elevation value of each slope unit in the scree slope unit set is read. These representative elevation values are summed, and the sum is divided by the number of scree slope units to obtain the average representative elevation value of the scree slope side of that boundary line. This average representative elevation value reflects the overall elevation level of the scree slope restoration zone within that boundary line and eliminates the interference of local undulations of individual slope units on the overall assessment.
[0058] The calculation is performed in the same manner for the slope unit sets of other repair zones. The representative elevation value of each slope unit is read, all representative elevation values are summed, and then the sum is divided by the number of slope units in other repair zones to obtain the average representative elevation value for the other repair zones along the interface boundary line. This average value represents the overall elevation level of that side within the interface range.
[0059] After obtaining the representative average elevation values on both sides, the elevation difference between the two sides of the interface boundary line is calculated by subtracting the average elevation of the scree slope restoration zone from the average elevation of the other restoration zone side. A positive elevation difference indicates that the other restoration zone side is generally above the scree slope restoration zone side, and water flow tends to move from the other restoration zone side to the scree slope restoration zone side under gravity. A negative elevation difference indicates that the scree slope restoration zone side is generally above the other restoration zone side, and water flow tends to move from the scree slope restoration zone side to the other restoration zone side under gravity. The absolute value of the elevation difference reflects the degree of overall elevation separation between the two sides, providing a quantitative basis for the layout of the interface drainage structure and retaining structure.
[0060] A7 Elevation Gradient Calculation.
[0061] Using only the elevation difference cannot reflect the distribution of elevation changes along the length of the interface. Even with the same elevation difference, the intensity of elevation change per unit length can vary significantly depending on the total length of the interface boundary. Therefore, it is necessary to combine the elevation difference with the total length of the interface boundary to form an elevation gradient that reflects the intensity of elevation change per unit length.
[0062] For each interface boundary line, using the total length of the interface boundary line calculated in the preceding steps, the average elevation difference between the two sides is divided by the total length of the interface boundary line to obtain the elevation gradient value. The elevation gradient value represents the average elevation change per unit length of plane along the interface boundary line. The sign of the elevation gradient is the same as the sign of the elevation difference. A positive elevation gradient indicates that the elevation increases per unit length when moving along the interface direction from the scree slope restoration zone side to other restoration zones side; a negative elevation gradient indicates that the elevation decreases per unit length in the same direction of movement. The larger the absolute value of the elevation gradient, the more drastic the elevation change per unit length; an absolute value close to zero indicates a moderate elevation change per unit length.
[0063] By calculating the elevation gradient for each interface boundary line, it is possible to distinguish between interfaces with abrupt elevation changes and interfaces with gradual elevation transitions in subsequent interface pattern division, providing an accurate basis for the hierarchical design of interface support structures and drainage structures.
[0064] A8 interface for constructing raw data units and forming data sets.
[0065] After completing the calculations of the interface geometry, interface number, representative slope types on both sides of the interface, representative elevation values, elevation difference, and elevation gradient, the above data needs to be recorded centrally according to the interface boundary line to form the original interface data unit.
[0066] For each interface boundary line, a raw interface data unit is constructed. This data unit should contain at least the following: First, the interface number, used to uniquely identify this interface boundary line among all interfaces. Second, the geometric information of the interface boundary line, including the sequence of polyline vertices and the total length, used to represent the spatial location and geometric shape of the interface. Third, the representative slope type code of the scree slope restoration zone and other restoration zone representative slope type codes, used to reflect the combination of engineering structural attributes on both sides of the interface. Fourth, the representative average elevation values of the scree slope restoration zone and other restoration zone average elevation values, used to express the elevation levels on both sides of the interface. Fifth, the average elevation difference and elevation gradient on both sides, used to describe the relative positional relationship of the interface in the vertical direction and the intensity of elevation change per unit length.
[0067] All original interface data units corresponding to the interface boundary lines are aggregated to form an original interface data set. In subsequent steps, the geometric shape, type combination, and elevation relationship of any interface boundary line can be quickly retrieved from the original interface data set by the interface number, providing a unified data foundation for interface pattern division, selection of interface repair rules, and performance recording and comparison during operation.
[0068] Through the complete processing in step S1, all the real contact boundaries between the gravel beach restoration zone and other restoration zones in the mine slope area have been transformed from simple geometric partition lines into a set of original interface data units with data items such as interface number, geometric polyline, slope type on both sides, average elevation on both sides, elevation difference on both sides, and elevation gradient. This makes the interface zone a basic data object that can directly participate in classification calculation and restoration scheme matching, providing complete and consistent input conditions for subsequent interface pattern clustering and automatic selection of interface restoration and governance schemes.
[0069] In step S1, the identification of all interfaces between the scree slope zone and other zones in the mine slope area was completed, and the interface number, interface geometry, slope type codes on both sides of the interface, and relevant parameters of the elevation relationship on both sides of the interface were recorded for each interface. In mine engineering design, different combinations of slope types and different elevation relationships will impose completely different requirements on the stability structure, drainage structure, and vegetation structure at the interface. If a single interface is still used as the smallest design unit, the interface rule base can only store scattered entries, making it difficult to form a unified and reusable repair mode.
[0070] However, the actual number of interfaces in a mine slope area may reach dozens or even hundreds. Many of these interfaces are completely identical in engineering attributes. For example, a scree slope might face bare rock, with the overall elevation on one side of other zones being higher and continuously rising along the interface direction. If separate repair plans are set for each of these interfaces, it would increase the design workload and hinder evaluation and adjustments during later operation and maintenance. Step S2 requires using the original interface data generated in Step S1 to extract a limited number of interface patterns that represent the engineering characteristics, without changing the original parameter values. All interfaces are then grouped under these patterns, and a corresponding pattern number is attached to each interface. This allows subsequent steps to call the rule base according to the pattern and uniformly write the repair plan at the interface partition unit level.
[0071] Preparation for B1 pattern feature construction.
[0072] In all the interface records formed in step S1, for each interface, four types of information directly related to pattern division are selected as the raw materials for pattern feature construction.
[0073] The first type of information is the representative slope type code on one side of the scree beach section; The second type of information is the representative slope type code on one side of other restoration zones; The third type of information is the difference in average elevation between the two sides; The fourth type of information is the elevation gradient along the interface direction.
[0074] B2 slope type combination identifier construction.
[0075] The interface mode first needs to reflect the engineering attributes on both sides at the slope type level, so a slope type combination identifier is constructed for each interface.
[0076] On the same interface, the slope type code representing the scree slope side and the slope type code representing the other restoration zone side have a clear order in an engineering sense; the former always represents the scree slope side, and the latter always represents the other side. In step S2, these two codes are arranged into a two-length encoding sequence in a fixed order, which is denoted as the slope type combination identifier.
[0077] For example, when one side of the scree slope is coded as a scree slope and the other side is coded as a bare rock slope, the slope type combination identifier is clearly marked as the combination of "scrub slope to bare rock". After performing this coding operation on all interfaces, the interfaces can be divided into several limited combinations at the type level, such as "scrub slope to bare rock", "scrub slope to backfill", "scrub slope to other slope types", etc.
[0078] B3 elevation difference state value construction.
[0079] The combination of slope types can only express the differences in engineering attributes on both sides of the interface, but it cannot indicate which side is upstream in elevation. In order to make the interface mode have a clear vertical relationship at the elevation level, step S2 needs to convert the average elevation difference between the two sides into a state value with clear engineering meaning.
[0080] For each interface, read the average elevation difference between the two sides recorded in step S1. Based on the sign of this difference, map it to three non-overlapping states.
[0081] When the average elevation value of the other restoration zone side is greater than the average elevation value of the scree beach side, the elevation difference state is recorded as "the other zone side is on top", and the value is marked with a positive one, indicating that the interface presents an upward structure from the scree beach side to the other zone side in terms of overall elevation.
[0082] When the average elevation values on both sides are exactly equal, the elevation difference state is recorded as "the overall average elevation is the same", and the value is marked as zero, indicating that there is no difference between upstream and downstream in the overall elevation of the interface.
[0083] When the average elevation value of the other restoration zone side is less than the average elevation value of the scree beach side, the elevation difference state is recorded as "the other zone side is below", and the value is marked with negative one, indicating that the interface presents a descending structure from the scree beach side to the other zone side in terms of overall elevation.
[0084] Through this ternary state value expression method, each interface is characterized as one of three types at the overall elevation relationship level, which allows the interface pattern to be organized in a finite state form without losing the ability to judge upstream and downstream.
[0085] B4 elevation gradient state value construction.
[0086] The elevation difference state value reflects the overall elevation relationship between the two sides, but it cannot express the trend of elevation change along the length of the interface. Some interfaces have a small overall elevation difference, but the local elevation changes along the interface direction are very concentrated, which can constrain the layout of drainage structures; other interfaces have dispersed elevation changes along the line, requiring different structural layout strategies. Step S2 needs to construct elevation gradient state values based on the elevation gradient values to express the elevation change trend along the interface direction.
[0087] For each interface, read the elevation gradient value recorded in step S1. Based on the positive and negative relationship of the elevation gradient, classify it into one of the three states.
[0088] When the elevation gradient value is greater than zero, it means that when moving along the interface line from the scree beach side to other restoration zones, the elevation increases with the distance on average. At this time, the elevation gradient state is recorded as "overall increase along the interface direction", and the value is marked with a positive one.
[0089] When the elevation gradient value is equal to zero, it means that the average elevation change along the interface line is zero. Although the local elevation may fluctuate, there is no single upward or downward trend overall. At this time, the elevation gradient state is recorded as "no overall trend change along the interface direction", and the value is marked as zero.
[0090] When the elevation gradient value is less than zero, it means that when moving along the interface line from the scree beach side to other restoration zones, the elevation decreases on average with increasing distance. In this case, the elevation gradient state is recorded as "overall decrease along the interface direction", and the value is marked with negative one.
[0091] Through this ternary state representation, each interface is classified into one of three types in terms of the directionality of its elevation distribution, which together with the aforementioned elevation difference state value constitutes a discretized description of the vertical relationship of the interface.
[0092] B5 interface mode feature group definition.
[0093] After completing the construction of slope type combination identifier, elevation difference state value and elevation gradient state value, step S2 needs to merge these three parts of information into a unified interface mode feature group.
[0094] For each interface, the interface pattern feature group consists of four ordered components. The first component is the slope type code representing the scree slope side. The second component is the slope type code representing the slope on the other restoration zone side. The third component is the elevation difference state value, represented by positive one, zero, or negative one to indicate three states: the other restoration zone side is generally above, generally at the same elevation, or generally below. The fourth component is the elevation gradient state value, also represented by positive one, zero, or negative one to indicate three states: generally rising along the interface line, generally without trend change, or generally decreasing.
[0095] These four components are arranged in a fixed order to form a feature sequence of length four. Each sequence fully expresses the combination of an interface in terms of both engineering attributes and elevation relationships on both sides. The set of all interface pattern feature groups constitutes a finite discrete space. In this space, if the pattern feature groups of two interfaces are completely identical, they can be considered to belong to the same interface pattern at the pattern level.
[0096] The B6 pattern represents the collection construction and interface pattern numbering.
[0097] After obtaining all the interface pattern feature groups, step S2 needs to extract different feature combinations from them to serve as representatives of the interface patterns, and assign a unique interface pattern number to each type of feature combination.
[0098] The specific method is as follows: In all pattern feature groups, each group is sequentially screened. Pattern feature groups with completely identical content are grouped into one category, and only one record from each category is retained as a representative of that category, forming a pattern representative set. Each record in the pattern representative set corresponds to an independent interface pattern, and different records differ in at least one component. The number of elements in the pattern representative set is denoted as the total number of patterns, and its value does not exceed the total number of interfaces.
[0099] After obtaining the set of pattern representatives, an interface pattern number is assigned to each pattern representative in a certain order. The pattern representatives can be numbered sequentially from the beginning until all pattern representatives have a unique number. The interface pattern number is a positive integer, ranging from one to the total number of patterns, and each number corresponds to exactly one record in the set of pattern representatives.
[0100] In this way, a strict one-to-one relationship is established between the interface mode number and the mode representative feature. Subsequently, only a certain number is needed to find the corresponding slope type combination identifier, elevation difference state value and elevation gradient state value.
[0101] The B7 interface number is generated based on pattern clustering and interface partitioning units.
[0102] After the pattern representative set and interface pattern number are generated, step S2 needs to classify each specific interface into a certain interface pattern to form a mapping relationship from interface number to pattern number, and at the same time, construct interface partition units based on this.
[0103] For each interface, its pattern feature group is read and compared with each record in the pattern representative set. When it is found that the four components of a pattern representative are completely identical to the four components of the interface, the interface is determined to belong to this pattern. Then, the interface number of this interface is added to the interface number set corresponding to the pattern number. By performing this process on all interfaces, each interface pattern number corresponds to an interface number set, which contains all interfaces with the same pattern features.
[0104] After completing the interface clustering, based on the original interface data records formed in step S1 and the interface pattern numbers obtained in step S2, an interface partitioning unit record is generated for each interface. The interface partitioning unit record contains the following: First, the interface mode number, which indicates the category of this interface in the mode space; Second, the interface number, which indicates which specific interface boundary line it refers to; Thirdly, the interface geometric objects, namely the set of interface polyline vertices and their geometric attributes recorded in step S1; Fourth, the slope type code is represented on the scree beach side and the slope type code is represented on the other side of the restoration zone; Fifth, the average elevation value on the scree beach side and the average elevation value on the other side of the other restoration zone; Sixth, the average elevation difference and elevation gradient values on both sides.
[0105] The interface partition unit record is structurally equivalent to adding an interface mode number field in front of the original interface data record. All other contents directly use the original calculation results in step S1 without changing the values, only adding mode belonging information.
[0106] After summarizing all interface partition unit records, an interface partition unit set is obtained. This set can be grouped by interface mode number to view all interfaces under a certain mode, or access all geometric and attribute information of a single interface by interface number as the key. This provides a complete data carrier for step S3 to retrieve the interface rule base by interface mode number and write it in batches into the interface repair scheme.
[0107] Through step S2, all interfaces between the scree beach zone and other zones have been transformed from a simple set of raw interface data into a set of interface partition units with pattern dimensions. Each interface is constructed with a pattern feature group based on the representative slope type code of one side of the scree beach and the other side of the other zone, the average elevation difference between the two sides, and the elevation gradient along the interface direction. A finite number of interface patterns are formed through the pattern representative set, with each pattern corresponding to a unique interface pattern number. All interfaces are categorized under different pattern numbers according to their pattern features. The pattern number, interface number, and the original geometric and elevation parameters of the interface are recorded uniformly within the interface partition unit. This establishes a rigorous, pattern-based data foundation for subsequent steps to retrieve repair schemes from the interface rule base based on the interface pattern number and write them into the interface partition unit.
[0108] In step S2, interface numbers with the same slope type combination and the same elevation relationship characteristics are aggregated into interface patterns, forming interface partition units with interface pattern numbers. At this point, all interfaces between the scree beach partition and other partitions have been patterned at the data level, but they are still at the stage of "classification" and "labeling". At the structural level, specific anchoring arrangements, drainage structures and vegetation configurations have not yet been implemented, and at the performance level, expected values for stability and drainage capacity have not been formed.
[0109] However, what is needed in engineering practice is not the abstract pattern itself, but a set of interface repair plans that can directly guide construction and be used for operational evaluation. This includes both the repair structure configuration for each interface and the expected performance in terms of stability and drainage capacity under this configuration. Step S3 is used to map the interface pattern and interface partition units obtained in step S2 to the repair schemes in the interface rule base, and to write the repair scheme information and expected performance indicators into each interface partition unit, thereby transforming the patterned result into a concrete and executable repair plan.
[0110] C1 constructs the interface rule base record relationship using the interface mode number.
[0111] In step S2, a limited number of interface patterns have been formed, and each interface pattern corresponds to an interface pattern number. Step S3 first sets a unique rule base record for each interface pattern number in the interface rule base.
[0112] Each rule base record uses the interface pattern number as its primary index and internally stores a complete set of interface repair scheme information matching that pattern. Specifically, a rule base record stores three levels of content simultaneously. The first level is a code used to identify the repair scheme, distinguishing different structural combinations. The second level consists of two pattern-level performance target indicators, one for stability and the other for drainage capacity. These two indicators are obtained by summarizing historical engineering calculation results or simulation analysis results according to pattern characteristics, with numerical values limited to the range of zero to one, used to express performance levels from completely failing to meet requirements to fully meeting requirements. The third level is the combination of repair structural parameters, internally storing quantitative parameters of anchoring components, reinforcement layers, drainage structures, vegetation layers, etc., in a pre-defined order, for subsequent direct guidance of interface structural design.
[0113] In this way, a one-to-one correspondence is established between the interface mode number and the rule base record. As long as a certain interface mode number is given, the corresponding repair solution and performance target can be accessed from the rule base.
[0114] C2 retrieves matching repair solution information based on the interface mode number.
[0115] After clarifying the correspondence between interface patterns and rule base records, a repair scheme retrieval is performed for each interface partition unit. Each interface partition unit already carries two types of identification information: interface pattern number and interface number.
[0116] During the retrieval process, the interface pattern number within the interface partition unit is used as the search condition to find rule base records in the interface rule base that match the pattern number field. The rule base is grouped by pattern number during the construction phase, and each pattern number corresponds to only one rule base record, thus ensuring the uniqueness of the retrieval results. After completing this matching operation, the repair scheme identifier, pattern layer stability target index, pattern layer drainage capacity target index, and repair construction parameter combination corresponding to the interface pattern number are obtained in memory or a data table.
[0117] C3 writes the repair scheme identifier and construction parameters into the interface partition unit.
[0118] After successfully retrieving the corresponding rule base record, the repair solution information is written to the interface partition unit.
[0119] The pattern number, interface number, and geometric shape, slope type, and elevation information inherited from step S1 are retained from the original interface partition unit record. Then, two items are added sequentially to the end of the record: one is the repair scheme identifier, which indicates which rule base scheme is adopted for this interface partition unit; the other is the repair construction parameter combination, which provides the specific design values for this interface partition unit in terms of anchoring, reinforcement, drainage, and vegetation.
[0120] Through this writing process, all interface partition units under the same mode achieve uniformity in terms of repair scheme identification and construction parameter combination, while interface partition units under different modes exhibit different scheme configurations. At this point, the interface partition unit has the conditions to be regarded as a prototype of the interface repair plan, but it does not yet include the expected performance indicators of stability and drainage capacity.
[0121] The calculation logic of the C4 stability expected performance index.
[0122] The interface repair plan needs to provide a theoretical performance in terms of stability after repair, for comparison with the results recorded in step S4. This expected performance is related to both the mode-level stability objective and the specific interface geometry.
[0123] The stability target index of the model layer is determined by the rule base compilation process and can be understood as the expected stability performance level when using the model repair scheme under typical geometric conditions. Among the specific interface geometric conditions, the quantity that has the most direct impact on stability is the interface elevation gradient. The elevation gradient has already been calculated in step S1, and the positive or negative sign indicates an upward or downward trend along the interface direction. Regardless of whether it is upward or downward, the faster the elevation changes, the more detrimental it is to structural stability. Therefore, the expected stability performance only needs to consider the absolute value of the elevation gradient.
[0124] In the calculation, the absolute value of the interface elevation gradient is first regarded as a geometric disadvantage factor. Then, using the model layer stability target index as the base value, a proportional relationship consisting of a constant and a geometric factor is constructed. The base value is divided by the sum of the constant and the geometric factor to obtain the expected stability performance value.
[0125] The corresponding calculation process for this textual expression is as follows: retrieve the model layer stability target index from the rule base record, retrieve the interface elevation gradient from the interface partition unit, calculate its square and take the square root to obtain the absolute value, add the absolute value with a constant to form a dimensionless amplification factor, use the model layer stability target index as the dividend and the amplification factor as the divisor to obtain the expected stability performance index.
[0126] When the absolute value of the elevation gradient of a certain interface is zero, the amplification factor is equal to one, and the expected stability performance is the same as the stability target of the model layer; when the absolute value of the elevation gradient increases, the amplification factor increases accordingly, and the expected stability performance decreases.
[0127] The calculation logic of the expected performance index of C5 drainage capacity.
[0128] The expected drainage capacity needs to reflect the theoretical drainage effect of the interface after the implementation of the repair plan, and is also calculated by combining the target index of drainage capacity of the model layer and the absolute value of the interface elevation gradient.
[0129] The target index for drainage capacity of the model layer describes the expected drainage performance level under standard elevation conditions, corresponding to the combination of interface model and repair structure. The absolute value of the interface elevation gradient is no longer considered a purely unfavorable factor in drainage problems, but rather a favorable factor driven by gravity. The more significant the elevation difference, the more sufficient the driving force for water flow along the interface direction, which, under the premise of a reasonable drainage structure, is conducive to the discharge of water from the interface region.
[0130] In the calculation, the absolute value of the interface elevation gradient is first treated as a geometric advantage factor. Then, using the model layer drainage capacity target index as the base value, a multiplicative relationship consisting of a constant and the geometric advantage factor is constructed. The base value is multiplied by the sum of the constant and the geometric advantage factor to obtain the expected drainage capacity performance value. The model layer drainage capacity target index is read from the rule base record, and the interface elevation gradient is read from the interface partition unit. The square is calculated and the square root is taken to obtain the absolute value. The constant is added to this absolute value to obtain a dimensionless enhancement factor. The model layer drainage capacity target index is multiplied by the enhancement factor to obtain the expected drainage capacity performance index.
[0131] When the absolute value of the elevation gradient is zero, the enhancement factor equals one, and the expected performance of drainage capacity is the same as the target drainage capacity of the model layer. When the absolute value of the elevation gradient increases, the enhancement factor increases, and the expected performance of drainage capacity increases accordingly, reflecting that the more obvious the elevation difference, the more sufficient the drainage conditions under the same structural configuration.
[0132] The formation of C6 interface repair plan unit and interface repair plan set.
[0133] After calculating the expected performance of stability and drainage capacity, these two performance indicators are written into each interface partition unit that has been fitted with a repair plan, and the unit is upgraded to an interface repair plan unit.
[0134] During processing, for each interface partition unit record, after the original pattern number, interface number, geometric information, slope type, elevation information, repair scheme identifier, and structural parameters, the expected performance values for stability and drainage capacity are added sequentially. In this way, each record simultaneously contains the pattern identifier, geometric conditions, structural configuration, and two performance expectations for stability and drainage capacity, which can be directly used as the basic unit for comparative evaluation of construction layout design and operation period.
[0135] All interface repair plan units are aggregated to form an interface repair plan set. Each record in the set corresponds to a specific interface. In terms of mode, they can be grouped according to interface mode number; in terms of space, they can be located to their actual location according to interface number. In step S4, when recording operations and adjusting plans, this interface repair plan set will be used as a benchmark to compare expected performance with actual performance. The rule base will be written back according to the interface mode number, thus closing the feedback loop of the entire repair and governance process.
[0136] Through the processing in step S3, the interface pattern number is no longer just a classification label, but becomes an index for retrieving repair schemes in the interface rule base; each interface partition unit not only obtains a specific repair scheme identifier and construction parameter combination, but also obtains the expected performance of stability and drainage capacity through the combination calculation of the pattern layer performance target and the interface elevation gradient, thereby forming an interface repair plan set that integrates structural information and performance information at the unit level, providing complete and calculable prerequisites for the operation record and scheme correction in step S4.
[0137] After completing the construction of original interface data, interface pattern division, and interface repair plan generation in mining slope areas, the expected performance of repair structures and stability and drainage capacity in each scree beach interface has been clearly defined. However, these expected values are only derived from the pattern objectives and geometric condition calculations in the design phase and do not reflect the actual response of the interface under the combined effects of rainfall, seepage, weathering, and vegetation growth during long-term operation. Once the mining slope enters the operational phase, the performance of each interface repair structure under actual working conditions will accumulate over a long period. Without quantitative recording and summarizing this operational information, and without comparing the operational results with the expected performance, it is impossible to determine which interface pattern designs are too conservative and which are insufficient, and even more difficult to form an iterative adjustment mechanism for repair schemes based on operational feedback in the interface rule base.
[0138] However, simply recording phenomena in a scattered manner on each interface cannot support pattern-level correction decisions. It is necessary to construct a complete feedback chain in step S4, from interface repair plan units to interface patterns and then to the interface rule base, to transform operational observations into dimensionless actual performance indicators, forming deviations at the unit level and average performance at the pattern level. Based on this, the pattern objectives and construction parameters are adjusted, and the interface rule base and interface repair plan set are updated simultaneously, so that the entire partition repair and governance method has self-correction capabilities for the operational period.
[0139] D1 Operation Recording Cycle and Actual Performance Indicator Construction In the interface repair plan set, each interface repair plan unit is assigned a set of sequentially arranged operation record batches, represented by integer numbers. The interval between each batch can correspond to annual inspection, pre-flood inspection, or post-flood inspection, as long as a uniform numbering method is used in all interface modes.
[0140] Within a specific batch of operational records, for each interface repair plan unit, quantities related to stability and quantities related to drainage conditions are observed. Stability-related quantities can be derived from safety factor calculations, deep displacement monitoring results, and comprehensive evaluation values of crack development. Drainage-related quantities can be derived from comprehensive evaluation values such as seepage pressure monitoring, drainage structure outlet flow rate, and wetting front location.
[0141] To enable direct comparison of these observations with the expected performance indicators within the zero-to-one interval in step S3, it is necessary to construct actual stability performance indicators and actual drainage capacity performance indicators. Specifically, within the same interface mode, the minimum and maximum values of stability observations for all interface repair plan units across all completed batches are statistically analyzed. The minimum value is considered the performance zero point, and the maximum value is considered the performance full value. Then, the stability observations for the current batch are converted into dimensionless stability performance indicators between zero and one using a linear proportional relationship. Similarly, in the drainage direction, the minimum and maximum values of drainage observations are statistically analyzed within the same interface mode, and the drainage observations for the current batch are converted into dimensionless drainage capacity performance indicators between zero and one using a linear proportional relationship.
[0142] Through the above processing, each interface repair plan unit has both a stability performance index and a drainage capacity performance index in each batch of operation records, and the value range of the two is consistent with the expected performance generated in step S3.
[0143] D2 Interface Repair Plan Unit Hierarchical Deviation Measurement.
[0144] In step S3, each interface repair plan unit has stored the expected performance indicators for stability and drainage capacity, both of which are in the range of zero to one. In step S4, after obtaining the actual performance indicators for a certain batch of operation records, the difference between the actual performance and the expected performance is calculated at the interface repair plan unit level to characterize the degree of deviation of a single interface in the operation of that batch.
[0145] Specifically, regarding stability, for a given interface repair plan unit and a given batch of operation records, the stability deviation value is obtained by subtracting the expected stability performance value of the unit from the actual stability performance value of the batch. A value greater than zero indicates that the actual stability performance in that batch is better than the expected performance; a value less than zero indicates that the actual stability performance is worse than the expected performance; and a value equal to zero indicates that the actual stability performance is consistent with the expected performance.
[0146] In the drainage direction, the actual drainage capacity performance index and the expected drainage capacity performance index are calculated using the same difference operation to obtain the drainage capacity deviation value. The meaning of the positive and negative signs and the zero value are completely consistent with the interpretation in the stability deviation.
[0147] Through this sub-step, each interface repair plan unit obtains two deviations for each batch of operation records, corresponding to stability and drainage direction, respectively, laying the data foundation for subsequent statistical summarization at the interface mode layer.
[0148] The average actual performance of the D3 interface mode hierarchy is constructed.
[0149] The adjustment of the interface repair plan needs to be based on the overall performance of the mode layer. Therefore, it is necessary to statistically aggregate the actual performance indicators of stability and drainage capacity at the mode layer.
[0150] For a given interface pattern, first determine the number of interface repair plan units belonging to that pattern, and then determine how many run record batches to use in the current evaluation round for statistical analysis. Next, sum the actual stability performance indicators of all interface repair plan units under that pattern across all participating run record batches. Divide the sum by the product of the number of units and the number of batches to obtain the average actual performance of that pattern in terms of stability. Since each actual performance indicator is between zero and one, the average value is also between zero and one.
[0151] In the drainage direction, following the exact same process, the actual performance indicators of drainage capacity are summed and divided by the product of the number of units and the number of batches to obtain the average actual performance of this model in the drainage capacity direction.
[0152] Through this sub-step, the actual performance information that was originally scattered across various interface repair plan units and various batches of operation records is compressed into two average values for each interface mode in terms of stability and drainage, forming an operational performance summary that can be directly compared with the mode's target indicators.
[0153] D4 mode target metrics are updated based on operational performance.
[0154] In step S3, each interface mode has recorded stability target indicators and drainage capacity target indicators in the interface rule base, and the values of both types of indicators are also limited to the range of zero to one. The average value of the actual stability performance and the average value of the actual drainage capacity performance are obtained for the same interface mode.
[0155] To ensure that the model's target indicators gradually converge to reflect real-world operating conditions after multiple runs, while maintaining a certain level of design safety, step S4 uses the arithmetic mean of the original model target indicators and the actual performance average as the new model target indicators in each update. Specifically: for stability, the original stability target indicator is added to the actual stability performance average, and the sum is divided by two; the resulting value is the new stability target indicator. For drainage, the original drainage capacity target indicator is added to the actual drainage capacity performance average, and the sum is also divided by two; the resulting value is the new drainage capacity target indicator.
[0156] Since both the original target value and the actual average value are located in the range of zero to one, the new target value will naturally also be located between zero and one, and between the original target value and the actual average value. When the original target value is higher than the actual average performance value, the new target value will shift towards the actual performance side, making the target setting more closely match the operating results; when the original target value is lower than the actual average performance value, the new target value will rise towards the actual performance side, making the target setting reflect the superior performance potential of the model.
[0157] D5 Repair Structure Parameter Combination Proportion Adjustment.
[0158] After the model's target indicators are updated, this change needs to be passed on to the corresponding model's repair construction parameter combination to ensure that the construction parameters are consistent with the new target indicators. Since the repair construction parameter combination contains multiple parameters, step S4 adopts a unified proportional adjustment method, defining adjustment coefficients in the stability direction and drainage direction respectively, and then amplifying or reducing the corresponding parameter group accordingly.
[0159] The stability-related structural parameter combination is a set of parameters extracted from the repair structural parameter combination that directly affect the interface's anti-sliding, anti-overturning, and overall bearing capacity. It includes at least the single length of the anchor or anchor cable, the depth of penetration into intact bedrock, the cross-sectional dimensions, the horizontal and vertical spacing, the design prestress value, the thickness of the concrete surface layer or lattice beam, the cross-sectional geometry, the material strength grade and reinforcement density, the thickness of the reinforced soil layer or reinforcement layer, the tensile strength of the reinforcement material, the number of layers and the spacing between layers, and the part of the soil cover thickness and vegetation configuration grade used for consolidating the gravel beach surface that directly corresponds to the root system's soil stabilization capacity. In the stability adjustment calculation, it is regarded as a whole parameter vector and participates in the stability adjustment coefficient by uniformly amplifying or reducing the scale.
[0160] The combination of drainage-related structural parameters is a set of parameters extracted from the combination of repair structural parameters that directly control the seepage path, drainage capacity, and interception and drainage organization. It includes at least the burial depth, hole diameter or pipe diameter, layout spacing, and porosity of filling materials for blind drains, culverts, or drainage holes; the bottom width, ditch depth, and longitudinal slope of slope interception ditches and drainage ditches; the height difference between cascades and the horizontal distance between cascades; the thickness, particle size distribution range, and corresponding permeability grade of crushed stone cushion and filter layer; and the configuration level of vegetation cover related to the control of rainwater interception and infiltration rate. In drainage adjustment calculations, it is also regarded as a whole parameter vector and participates in the drainage adjustment coefficient by uniformly scaling up or down.
[0161] In terms of stability, the stability adjustment coefficient is calculated first. The stability adjustment coefficient is constructed as follows: the original stability target index is subtracted from the average actual stability performance, and the difference is then added to a constant. The result is the stability adjustment coefficient. When the average actual performance is lower than the original target value, the difference is positive, and the adjustment coefficient is greater than one, corresponding to an increase in stability-related parameters in the next round. When the average actual performance is greater than the original target value, the difference is negative, and the adjustment coefficient is less than one but greater than zero, corresponding to a moderate reduction in the scale of some stable components while meeting safety requirements. Subsequently, each parameter in the stability-related structural parameter combination is multiplied by this adjustment coefficient, resulting in an overall amplification or reduction, thus obtaining a new stability-related structural parameter combination.
[0162] In the drainage direction, the drainage adjustment coefficient is constructed in the same way as in the stability direction. The original drainage capacity target index is subtracted from the average actual drainage capacity performance, and the difference is then added to a constant. The result is used as the drainage adjustment coefficient. When the average actual performance is lower than the original target value, the drainage adjustment coefficient is greater than one, corresponding to an increase in the size or density of the drainage structure. When the average actual performance is higher than the original target value, the drainage adjustment coefficient is less than one but greater than zero, corresponding to a moderate reduction in the drainage structure configuration while ensuring smooth drainage. Subsequently, each parameter in the combination of drainage-related structural parameters is multiplied by the drainage adjustment coefficient to obtain a new combination of drainage-related structural parameters.
[0163] By reasonably limiting the value range of the target indicators and the average value of actual performance during the rule base compilation stage, it is possible to control both adjustment coefficients to remain within a range of not less than zero and not exceeding two, thereby avoiding both parameter compression towards zero and parameter amplification to unreasonable levels. The new overall repair structural parameter combination consists of a new stability-related structural parameter combination and a new drainage-related structural parameter combination.
[0164] The D6 rule base records are updated synchronously with the interface repair plan.
[0165] After updating the pattern target indicators and the combination of repair construction parameters, this result needs to be reflected synchronously in two data carriers: one is the interface rule base, and the other is the interface repair plan set.
[0166] In the interface rule base, for each interface mode, the original stability target index is replaced with a new stability target index, the original drainage capacity target index is replaced with a new drainage capacity target index, and the original construction parameter combination is replaced with a new repair construction parameter combination. After the update, each record in the rule base reflects the target and construction configuration formed under the feedback of the latest round of operation.
[0167] In the interface repair plan set, for all interface repair plan units with the same mode number, the original construction parameter fields are first replaced with new repair construction parameter combinations to ensure that the unit-level construction information is consistent with the rule base. Then, based on the expected performance calculation relationship given in step S3, the expected stability performance index and the expected drainage capacity performance index are recalculated using the new mode target index and the original interface elevation gradient. That is, in the stability direction, the mode target index is divided by one and the absolute value of the elevation gradient is added, and in the drainage direction, the mode target index is multiplied by one and the absolute value of the elevation gradient is added, thus obtaining the expected performance consistent with the new rules.
[0168] Through this synchronous update process, the interface rule base and interface repair plan set remain consistent in terms of pattern objectives, construction parameters, and expected performance, providing a new benchmark for the next round of operation records and feedback.
[0169] Step S4, based on the interface repair plan set generated in Step S3, linearly normalizes the stability and drainage observations within the running record period to construct dimensionless stability performance indicators and drainage capacity performance indicators. At the interface repair plan unit level, the difference between actual performance and expected performance is calculated. At the interface mode level, the actual performance is arithmetically averaged to form the average actual performance of the two mode layers: stability and drainage capacity. Then, the mode layer target indicators are updated using the arithmetic mean of the original mode target indicators and the average actual performance. Stability adjustment coefficients and drainage adjustment coefficients are constructed based on the difference between the original target value and the average actual performance. The corresponding repair construction parameter combinations are then uniformly proportionally corrected. Finally, the updated mode targets and repair construction parameters are written back to the interface rule base and the interface repair plan set, and the expected performance is recalculated according to existing functional relationships, thus forming an iterative closed loop for the interface repair scheme based on running feedback.
[0170] Specifically, the above are merely preferred embodiments of this application and are not intended to limit this application.
[0171] In the description of this specification, references to terms such as "an embodiment," "example," "specific example," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.
[0172] The preferred embodiments of the present invention disclosed above are merely illustrative of the invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the invention to any specific implementation. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.
Claims
1. A method for zoned restoration and management of mine slope areas, characterized in that, Including the following steps: S1, identify the boundary between the scree beach zone and other zones, generate the original interface data based on the slope type and elevation relationship on both sides of the boundary, and assign an interface number to each boundary. S2. Based on the differences in slope type and elevation relationship reflected in the original interface data, the interface numbers with the same characteristics are clustered into interface patterns. The interface patterns are used to divide the interface partition units and inherit the original interface data. S3 uses the interface mode as the search condition, automatically selects the corresponding interface repair scheme from the interface rule base, writes the interface repair scheme into each interface partition unit to form an interface repair plan and records the expected performance. S4. Record the operation of the interface partition unit according to the interface repair plan, compare the recorded results with the expected performance of the interface mode in the interface repair plan, adjust the corresponding interface repair scheme for inconsistent interface modes, and update the interface rule base and interface repair plan in sync.
2. The method for zoned restoration and management of mine slope areas according to claim 1, characterized in that: In step S1, when identifying the boundary between the gravel beach zone and other zones, the contact lines between the gravel beach zone grid and the adjacent bare rock slope zone grid and backfill zone grid in the digital terrain model of the mine slope are extracted. Each contact line is determined as a boundary, and the vertex coordinate sequence of the boundary polyline, the slope type code on both sides, and the elevation value of the corresponding vertex are recorded along the boundary. At the same time, a unique interface number is generated for each boundary and written into the interface original data record.
3. The method for zoned restoration and management of mine slope areas according to claim 2, characterized in that: In step S1, to generate the original interface data, the following steps are also included: based on the elevation of the vertices on both sides of each boundary, calculate the average elevation of the scree beach side and the average elevation of the other partition side respectively, form the overall elevation difference between the two, and divide the overall elevation relationship of the boundary into three states: upstream side is above, both sides are at the same height, and upstream side is below, according to the elevation change trend along the boundary direction. At the same time, according to the elevation change trend along the boundary direction, divide the elevation gradient into three states: overall rising, overall horizontal, and overall falling, and store the two types of state values together in the original interface data.
4. The method for zoned restoration and management of mine slope areas according to claim 3, characterized in that: In step S2, when clustering interface numbers into interface patterns, an ordered feature group is formed by the slope type code of the scree beach side, the slope type code of the other partition side, the overall elevation relationship status value, and the elevation gradient status value in the original interface data corresponding to each boundary. Interface numbers with the same feature group are merged into the same interface pattern, and a unique interface pattern number is assigned to each different feature group. At the same time, the interface pattern number and the interface number are stored together in the interface partition unit to establish a one-to-one correspondence.
5. The method for zoned restoration and management of mine slope areas according to claim 4, characterized in that: In step S3, when constructing the interface rule base, a rule base record is set for each interface mode number. The rule base record includes at least the interface repair scheme identifier, mode layer stability target index, mode layer drainage capacity target index, and repair construction parameter combination that correspond one-to-one with the interface mode number. When executing step S3, the corresponding rule base record is retrieved from the interface rule base using the interface mode number as an index. The interface repair scheme identifier and repair construction parameter combination in the record are written into the interface partition unit with the same interface mode number to form the interface repair plan unit.
6. The method for zoned restoration and management of mine slope areas according to claim 5, characterized in that: In step S3, when recording the expected performance, for each interface repair plan unit, the stability target index and drainage capacity target index of the mode layer in the interface rule base are read and combined with the elevation gradient of the interface. The expected performance of stability is obtained by reducing the stability target index of the mode layer according to the monotonically decreasing ratio when the absolute value of the elevation gradient increases, and the expected performance of drainage capacity is obtained by amplifying the drainage capacity target index of the mode layer according to the monotonically increasing ratio when the absolute value of the elevation gradient increases. These are written into the interface repair plan unit together with the interface repair scheme.
7. The method for zoned restoration and management of mine slope areas according to claim 6, characterized in that: In step S4, when recording the operation of the interface partition unit, a batch number of the operation record is set for each interface repair plan unit in increments of integers. In each batch, stability observations and drainage observations are collected. Within the same interface mode, the minimum and maximum values of stability observations and drainage observations of all observation batches are statistically analyzed. The stability observations and drainage observations of the current batch are converted into actual stability performance indicators and actual drainage capacity performance indicators in a linear ratio where the minimum value corresponds to zero and the maximum value corresponds to one, and then stored in the operation record.
8. A method for zoned restoration and management of mine slope areas according to claim 7, characterized in that: In step S4, when comparing the recorded results with the expected performance in the interface repair plan, first at the interface repair plan unit level, the stability deviation is obtained by subtracting the corresponding expected stability performance from the actual stability performance index of each batch, and the drainage capacity deviation is obtained by subtracting the corresponding expected drainage capacity performance from the actual drainage capacity performance index of each batch. Then at the interface mode level, the arithmetic mean of the actual stability performance index and the actual drainage capacity performance index of all interface repair plan units and all batches participating in the statistics belonging to the same interface mode is calculated respectively to obtain the corresponding mode layer stability performance average and mode layer drainage capacity performance average.
9. A method for zoned restoration and management of mine slope areas according to claim 8, characterized in that: In step S4, when adjusting the interface repair scheme for inconsistent interface modes, the original mode layer stability target index and the average value of the actual stability performance of the mode layer are arithmetically averaged to obtain a new mode layer stability target index in the stability direction. In the drainage direction, the original mode layer drainage capacity target index and the average value of the actual drainage capacity performance of the mode layer are arithmetically averaged to obtain a new mode layer drainage capacity target index. Based on the difference between the original target index and the average value of the actual performance of the mode layer, stability adjustment coefficients and drainage adjustment coefficients are constructed. The stability-related parameter groups and drainage-related parameter groups in the repair construction parameter combination are enlarged or reduced by a uniform ratio to generate a new repair construction parameter combination.
10. A method for zoned restoration and management of mine slope areas according to claim 9, characterized in that: In step S4, when synchronously updating the interface rule base and interface repair plan, the mode layer stability target index and mode layer drainage capacity target index in the rule base record corresponding to each interface mode are replaced with new mode layer target indices. The repair construction parameter combination in the record is replaced with new repair construction parameter combination. The repair construction parameter field of all interface repair plan units with the same interface mode number is synchronously replaced. At the same time, according to the established expected performance calculation relationship in step S3, the expected stability performance and expected drainage capacity performance are recalculated with the new mode layer target index and interface elevation gradient, and the original expected performance fields are overwritten to form an updated interface repair plan set for use in the next round of operation records.
