fix: localize region alarm rules and update tutorials

Author: nquyencubas523-cloud

docs/en/tutorials/04-pipeline-orchestration/images/img_42.png

@@ -139,7 +139,7 @@ relationship, so the guide starts from a known minimum business chain.
 | Model | Installed `PedestrianDetection` atomic model |
 | Rules | Track people, keep the pedestrian class, decide whether a target enters the main area |
 | Output | Region-intrusion event with the person target and snapshot |
-| Positive sample | A clearly visible person enters the area and satisfies the duration |
+| Positive sample | A clearly visible person enters the area and satisfies the minimum stay duration |
 | Negative sample | A person passes only outside the area |
 | Acceptance | Positive has a box and event; negative has no intrusion event; the task still works after restart |
 
@@ -181,10 +181,12 @@ Complete these six numbered steps:
    Keep the pedestrian label and start with the current Min Pedestrian Size of `60`.
 
 5. **Region Alarm**
-   Select the main area as input. This node evaluates whether pedestrians enter the area drawn during
-   scenario task assignment.
+   Select **Exception Alarm** for **Output Purpose**, **Target Region Stay** for **Region Rule Type**,
+   **Primary Region** for **Decision Region**, and **Target is inside the region** for
+   **Stay Start Condition**. This node evaluates whether pedestrians enter the area drawn during scenario
+   task assignment and produces a candidate alarm after the minimum stay duration is satisfied.
 
-   ![Using the main area in Region Alarm](images/img_42.webp)
+   ![Selecting Exception Alarm, Target Region Stay, and Primary Region in Region Alarm](images/img_42.png)
 
 6. **Event Report**
    Select a triggered event with target tracking. Video clips increase storage and transfer load, so enable
@@ -211,7 +213,7 @@ Under **Parameter Settings**, start from an explainable baseline:
 | --- | ---: | --- |
 | Pedestrian Detection Method | Bottom | Use the person's foot position for a ground-plane area |
 | Min Pedestrian Size | 60 | Remove very small pedestrian targets |
-| Detection Time | 0 seconds | Prove the chain first; increase later to suppress brief entry |
+| Minimum Stay Duration | 0 seconds | Prove the chain first; increase later to suppress brief entry |
 | Alarm Interval (sec) | 3 | Convenient for a short test; increase for the production response process |
 | Alarm Count | 1 | Verify a single trigger first |
 | Stationary Target Deduplication | Off | Observe raw behavior before deciding whether to enable it |
@@ -271,7 +273,7 @@ Final pass criteria:
 
 1. Confirm that Category Filter does not remove every target.
 2. Confirm that the target enters the area using the selected box position.
-3. Restore detection duration and alarm suppression to a testable baseline.
+3. Restore minimum stay duration and alarm suppression to a testable baseline.
 4. Confirm that Event Report exists after the rules and is configured for a triggered event.
 5. Check Event Center filters and storage space.
 

docs/en/tutorials/04-pipeline-orchestration/images/img_42.webp

@@ -138,7 +138,7 @@ next:
 | 模型 | 已安装的 `PedestrianDetection` 行人检测原子模型 |
 | 规则 | 追踪行人、保留行人类别、判断是否进入主区域 |
 | 输出 | 带行人目标的区域入侵事件和抓拍图 |
-| 正样本 | 人员清晰进入区域并满足检测持续时间 |
+| 正样本 | 人员清晰进入区域并满足最短停留时间 |
 | 负样本 | 人员只在区域外经过 |
 | 验收方法 | 正样本有框且有事件；负样本不产生区域入侵事件；重启任务后仍可运行 |
 
@@ -179,9 +179,11 @@ next:
    保留行人标签，最小行人尺寸从当前默认 `60` 开始。过小目标漏报或噪声问题出现后再调。
 
 5. **区域告警判断**
-   输入区域类型选择主区域。该节点依据场景任务分配页绘制的区域判断行人是否进入。
+   输出目的选择 **异常告警**，区域规则类型选择 **目标区域停留**，判断区域选择
+   **主区域**，停留开始条件选择 **目标位于区域内**。该节点依据场景任务分配页绘制的
+   区域判断行人是否进入，并按最短停留时间产生候选告警。
 
-   ![区域告警判断节点使用主区域](images/img_42.webp)
+   ![区域告警判断节点选择异常告警、目标区域停留和主区域](images/img_42.png)
 
 6. **事件上报**
    选择带目标跟踪的触发类事件。是否附带视频片段会影响存储和传输，应按项目要求设置；
@@ -208,7 +210,7 @@ next:
 | --- | ---: | --- |
 | pedestrian 检测方式 | 底部 | 以行人脚部位置判断是否进入地面区域 |
 | 最小行人尺寸 | 60 | 过滤过小行人目标 |
-| 检测时间 | 0 秒 | 首轮先验证链路；需要抑制瞬时进入时再增加 |
+| 最短停留时间 | 0 秒 | 首轮先验证链路；需要抑制瞬时进入时再增加 |
 | 告警时间间隔（秒） | 3 | 便于短视频验证；生产环境按处置流程增大 |
 | 告警次数 | 1 | 首轮只验证一次触发 |
 | 静止目标去重 | 关闭 | 先观察原始行为，再决定是否启用 |
@@ -267,7 +269,7 @@ next:
 
 1. 确认类别过滤没有删除全部目标。
 2. 确认目标实际进入检测区域，且检测方式选择的位置正确。
-3. 将检测时间和告警抑制恢复为可验证基线。
+3. 将最短停留时间和告警抑制恢复为可验证基线。
 4. 检查事件上报节点存在、位于规则之后，并已配置触发类事件。
 5. 检查事件中心筛选条件和存储空间。
 

docs/en/tutorials/04-pipeline-orchestration/pipeline-orchestration.md

@@ -3,9 +3,25 @@ import {
   AREA_RULE_UI_TYPES,
   applyAreaRuleUiType,
   buildAreaRuleSummary,
+  getAreaRuleFieldText,
+  getAreaRuleOptionLabel,
   inferAreaRuleUiType,
   mergeParamsPreservingUnknown
 } from '../src/views/gam/countManagement/arrangeDetail/flow/areaRuleCompatibility.js'
+import zhCN from '../src/i18n/locales/zh-CN.js'
+import enUS from '../src/i18n/locales/en-US.js'
+
+const createTranslator = (messages) => (key, params = {}) => {
+  const value = key.split('.').reduce((current, segment) => current?.[segment], messages)
+  assert.equal(typeof value, 'string', `missing translation: ${key}`)
+  return Object.entries(params).reduce(
+    (text, [name, replacement]) => text.replaceAll(`{${name}}`, String(replacement)),
+    value
+  )
+}
+
+const zhT = createTranslator(zhCN)
+const enT = createTranslator(enUS)
 
 const legacy = [
   { key: 'areaAlarmType', value: '6' },
@@ -14,7 +30,7 @@ const legacy = [
 ]
 assert.equal(inferAreaRuleUiType(legacy), AREA_RULE_UI_TYPES.LEGACY_TARGET_LIMIT)
 assert.match(
-  buildAreaRuleSummary(legacy, AREA_RULE_UI_TYPES.LEGACY_TARGET_LIMIT),
+  buildAreaRuleSummary(legacy, AREA_RULE_UI_TYPES.LEGACY_TARGET_LIMIT, zhT),
   /有效目标数 < 2/
 )
 
@@ -31,7 +47,8 @@ compareCases.forEach(([compare, symbol]) => {
       { key: 'param.areaLimitTargetCount', value: '3' },
       { key: 'param.areaLimitTargetType', value: compare }
     ],
-    AREA_RULE_UI_TYPES.TARGET_LIMIT
+    AREA_RULE_UI_TYPES.TARGET_LIMIT,
+    zhT
   )
   assert.match(summary, new RegExp(`有效目标数 ${symbol} 3`))
 })
@@ -66,4 +83,50 @@ const unknown = [{ key: 'areaAlarmType', value: '99' }]
 assert.equal(inferAreaRuleUiType(unknown), AREA_RULE_UI_TYPES.UNKNOWN)
 assert.deepEqual(applyAreaRuleUiType(unknown, AREA_RULE_UI_TYPES.UNKNOWN), unknown)
 
+assert.equal(
+  getAreaRuleFieldText('inputAreaType', enT).name,
+  'Decision Region'
+)
+assert.equal(
+  getAreaRuleOptionLabel('param.areaLimitTargetType', '0', '', enT),
+  'Less than'
+)
+
+const englishSummaryCases = [
+  [
+    AREA_RULE_UI_TYPES.TARGET_LIMIT,
+    [
+      { key: 'param.areaLimitTargetCount', value: '3' },
+      { key: 'param.areaLimitTargetType', value: '0' }
+    ]
+  ],
+  [AREA_RULE_UI_TYPES.AREA_COUNT, []],
+  [AREA_RULE_UI_TYPES.PASS_FLOW, []],
+  [AREA_RULE_UI_TYPES.TRIPWIRE, [{ key: 'param.trippingWireType', value: '1' }]],
+  [
+    AREA_RULE_UI_TYPES.DIRECTION,
+    [
+      { key: 'param.retroDirect', value: '0' },
+      { key: 'param.retroDistance', value: '0.05' }
+    ]
+  ],
+  [
+    AREA_RULE_UI_TYPES.DURATION,
+    [
+      { key: 'durationBreakAreaType', value: '0' },
+      { key: 'param.areaDuration', value: '10' },
+      { key: 'param.areaDurationTimeType', value: '1000' }
+    ]
+  ],
+  [AREA_RULE_UI_TYPES.PRESENCE, []],
+  [AREA_RULE_UI_TYPES.LEGACY_TARGET_LIMIT, legacy],
+  [AREA_RULE_UI_TYPES.UNKNOWN, unknown]
+]
+
+englishSummaryCases.forEach(([type, params]) => {
+  const summary = buildAreaRuleSummary(params, type, enT)
+  assert.ok(summary.length > 0, `empty English summary for ${type}`)
+  assert.doesNotMatch(summary, /\p{Script=Han}/u, `Chinese leaked into ${type}: ${summary}`)
+})
+
 console.log('area rule compatibility checks passed')

docs/tutorials/04-pipeline-orchestration/images/img_42.png

@@ -1653,6 +1653,151 @@ export default {
     }
   },
   flow: {
+    areaRule: {
+      title: 'Region Rule Configuration',
+      purposeLabel: 'Output Purpose',
+      purposes: {
+        alarm: 'Exception Alarm',
+        statistics: 'Statistics Report',
+        compatibility: 'Compatibility Configuration'
+      },
+      typeLabel: 'Region Rule Type',
+      summaryLabel: 'Rule Description',
+      downstreamNote: 'Whether an alarm record is ultimately created still depends on rate limits, deduplication, and review rules in the downstream “Event Report” node.',
+      legacyNote: 'This is a legacy multi-node configuration. Editing preserves the original type 6 and parameter keys without automatic migration.',
+      types: {
+        targetLimit: 'Region Target Count Condition',
+        areaCount: 'Region Target Count Statistics',
+        passFlow: 'Entry/Exit Flow Statistics',
+        tripwire: 'Target Line Crossing',
+        direction: 'Vertical Direction Anomaly',
+        duration: 'Target Region Stay',
+        presence: 'Target Present in Region',
+        legacyTargetLimit: 'Region Target Count Condition (Legacy Multi-node)',
+        unknown: 'Unrecognized Legacy Region Rule'
+      },
+      fields: {
+        decisionRegion: {
+          name: 'Decision Region',
+          description: 'Choose the primary or associated region for rule evaluation.'
+        },
+        targetCountThreshold: {
+          name: 'Target Count Threshold',
+          description: 'Compared with the actual valid target count in the region.'
+        },
+        triggerCondition: {
+          name: 'Trigger Condition',
+          description: 'Choose the comparison between the actual target count and the threshold.'
+        },
+        conditionDuration: {
+          name: 'Condition Duration',
+          description: 'How long the count condition must remain true; 0 evaluates the current frame.'
+        },
+        durationUnit: {
+          name: 'Duration Unit',
+          description: 'Time unit used by the condition duration.'
+        },
+        reportingPeriod: {
+          name: 'Statistics Reporting Period',
+          description: 'Periodically produces region count or entry/exit flow statistics.'
+        },
+        reportingPeriodUnit: {
+          name: 'Reporting Period Unit',
+          description: 'Time unit used by the statistics reporting period.'
+        },
+        crossingDirection: {
+          name: 'Crossing Direction',
+          description: 'Matches when a target crosses in the direction marked on the tripwire.'
+        },
+        requiredLineCount: {
+          name: 'Required Tripwire Count',
+          description: 'Number of tripwires the same tracked target must cross.'
+        },
+        stayStartCondition: {
+          name: 'Stay Start Condition',
+          description: 'Choose whether the target only needs to be inside the region or must first be observed entering from outside.'
+        },
+        minimumStayDuration: {
+          name: 'Minimum Stay Duration',
+          description: 'How long the same tracked target must continuously remain in the region.'
+        },
+        stayDurationUnit: {
+          name: 'Stay Duration Unit',
+          description: 'Time unit used by the minimum stay duration.'
+        },
+        prohibitedDirection: {
+          name: 'Prohibited Movement Direction',
+          description: 'The current implementation evaluates vertical movement and requires stable target tracking.'
+        },
+        minimumAbnormalDisplacement: {
+          name: 'Minimum Abnormal Displacement',
+          description: 'A ratio of frame height; 0.05 means 5% of the frame height.'
+        },
+        legacyTargetCountThreshold: {
+          name: 'Target Count Threshold',
+          description: 'Target count threshold used by the legacy multi-node configuration.'
+        },
+        legacyTriggerCondition: {
+          name: 'Trigger Condition',
+          description: 'Count comparison used by the legacy multi-node configuration.'
+        },
+        legacyConditionDuration: {
+          name: 'Condition Duration',
+          description: 'Condition duration used by the legacy multi-node configuration.'
+        },
+        legacyDurationUnit: {
+          name: 'Duration Unit',
+          description: 'Time unit used by the legacy multi-node configuration.'
+        },
+        periodicDataChangeMarker: {
+          name: 'Periodic Data Change Marker',
+          description: 'Marks whether the target count changed in a periodic report; it does not bypass the reporting period.'
+        }
+      },
+      options: {
+        compare: {
+          lessThan: 'Less than',
+          greaterThan: 'Greater than',
+          notGreaterThan: 'Not greater than',
+          notLessThan: 'Not less than',
+          equalTo: 'Equal to'
+        },
+        unit: {
+          milliseconds: 'ms',
+          seconds: 's',
+          minutes: 'min',
+          hours: 'h'
+        },
+        tripwire: {
+          count1: 'Cross 1 tripwire',
+          count2: 'Cross 2 tripwires'
+        },
+        stayStart: {
+          inside: 'Target is inside the region',
+          entered: 'Target enters from outside the region',
+          insideFallback: 'inside the region'
+        },
+        direction: {
+          bottomToTop: 'from bottom to top of the frame',
+          topToBottom: 'from top to bottom of the frame',
+          specified: 'in the specified direction'
+        }
+      },
+      summary: {
+        currentFrame: 'evaluated on the current frame',
+        satisfiedFor: 'satisfied for {value} {unit}',
+        targetExpression: 'Valid target count {symbol} {count}',
+        targetExpressionFallback: 'The valid target count satisfies the selected threshold relation',
+        targetLimit: 'Compares the valid target count in the region with the target count threshold and supports <, >, ≤, ≥, and =. Current configuration: {expression}; a candidate alarm is produced when the condition is {duration}.',
+        areaCount: 'Periodically reports the current valid target count in the region, including zero. This is statistical data, not an exception alarm.',
+        passFlow: 'Periodically reports tripwire entries, exits, and cumulative flow. This rule requires stable target tracking.',
+        tripwire: 'A candidate alarm is produced when the same tracked target crosses the configured number ({count}) of tripwires in the marked direction.',
+        direction: 'A candidate alarm is produced when the same target moves {direction} by more than {distance}% of the frame height.',
+        duration: 'A candidate alarm is produced when the same target satisfies “{condition}” and the stay condition is {duration}.',
+        presence: 'A candidate alarm is produced when any valid upstream target is inside the decision region. Target classes are determined by the upstream model and category filter.',
+        unknown: 'This configuration contains a legacy rule value that the current interface cannot recognize. Use compatibility mode for read-only inspection to avoid overwriting it.'
+      }
+    },
     actionNames: {
       '目标检测算法': 'Target Detection',
       '目标分类算法': 'Target Classification',