反属性推理 check_ltlspec -p “G((smoke=detected)->! X(window.switch=open))“

smoke step设置为4

X出不来是因为有smoke一直在detected不变的情况,也不是,只要smoke

NuSMV > check_ltlspec -p "G((smoke=detected)->X(window.switch=open))"
-- specification  G (smoke = detected ->  X window.switch = open)  is false
-- as demonstrated by the following execution sequence
Trace Description: LTL Counterexample
Trace Type: Counterexample
  -> State: 1.1 <-
    window.switch = close
    weather.rain = not_raining
    weather.rainState = not_raining
    rain_count = 1
    smoke = detected
    smokeState = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 1.2 <-
    window.switch = open
    rain_count = 0
    smokeState = detected
    smoke_count = 0
    delaywindow = 5
  -> State: 1.3 <-
    weather.rain = raining
    rain_count = 1
    runinwindow.timer = 5
  -> State: 1.4 <-
    window.switch = close
    weather.rainState = raining
    rain_count = 0
    smoke = clear
    smoke_count = 1
    runinwindow.timer = 4
  -- Loop starts here
  -> State: 1.5 <-
    weather.rain = not_raining
    rain_count = 1
    smokeState = clear
    smoke_count = 0
    runinwindow.timer = 3
  -> State: 1.6 <-
    weather.rainState = not_raining
    rain_count = 0
    runinwindow.timer = 2
  -> State: 1.7 <-
    smoke = detected
    smoke_count = 1
    runinwindow.timer = 1
  -> State: 1.8 <-
    window.switch = open
    smokeState = detected
    smoke_count = 0
    runinwindow.timer = 0
  -> State: 1.9 <-
    weather.rain = raining
    rain_count = 1
    smoke = clear
    smoke_count = 1
    runinwindow.timer = 5
  -> State: 1.10 <-
    window.switch = close
    weather.rainState = raining
    rain_count = 0
    smokeState = clear
    smoke_count = 0
    runinwindow.timer = 4
  -> State: 1.11 <-
    weather.rain = not_raining
    rain_count = 1
    runinwindow.timer = 3
NuSMV > check_ltlspec -p "G((smoke=detected)->F(window.switch=open))"
-- specification  G (smoke = detected ->  F window.switch = open)  is false
-- as demonstrated by the following execution sequence
Trace Description: LTL Counterexample
Trace Type: Counterexample
  -> State: 2.1 <-
    window.switch = open
    weather.rain = raining
    weather.rainState = not_raining
    rain_count = 1
    smoke = clear
    smokeState = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 2.2 <-
    window.switch = close
    weather.rainState = raining
    rain_count = 0
    smoke_count = 0
  -> State: 2.3 <-
    weather.rain = not_raining
    rain_count = 1
    smoke = detected
    smoke_count = 1
  -> State: 2.4 <-
    window.switch = open
    weather.rainState = not_raining
    rain_count = 0
    smokeState = detected
    smoke_count = 0
    delaywindow = 5
  -> State: 2.5 <-
    weather.rain = raining
    rain_count = 1
    runinwindow.timer = 5
  -> State: 2.6 <-
    window.switch = close
    weather.rainState = raining
    rain_count = 0
    runinwindow.timer = 4
  -> State: 2.7 <-
    weather.rain = not_raining
    rain_count = 1
    smoke = clear
    smoke_count = 1
    runinwindow.timer = 3
  -> State: 2.8 <-
    weather.rainState = not_raining
    rain_count = 0
    smokeState = clear
    smoke_count = 0
    runinwindow.timer = 2
  -> State: 2.9 <-
    runinwindow.timer = 1
  -- Loop starts here
  -> State: 2.10 <-
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 2.11 <-

smoke_fix1,直接跳过一步固定自然属性

冲突状态仍存在

NuSMV > check_ltlspec -p "G((smoke=detected)->!X(window.switch=open))"
-- specification  G (smoke = detected -> !( X window.switch = open))  is false
-- as demonstrated by the following execution sequence
Trace Description: LTL Counterexample
Trace Type: Counterexample
  -> State: 1.1 <-
    window.switch = close
    weather.rain = not_raining
    weather.rainState = not_raining
    rain_count = 1
    smoke = detected
    smokeState = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
    flag1 = TRUE
    flag2 = FALSE
    step = 1
  -> State: 1.2 <-
    window.switch = open
    rain_count = 0
    smokeState = detected
    smoke_count = 0
    delaywindow = 5
    step = 2
  -> State: 1.3 <-
    weather.rain = raining
    rain_count = 1
    runinwindow.timer = 5
    step = 3
  -> State: 1.4 <-
    window.switch = close
    weather.rainState = raining
    rain_count = 0
    runinwindow.timer = 4
    step = 4
  -> State: 1.5 <-
    weather.rain = not_raining
    rain_count = 1
    runinwindow.timer = 3
    step = 0
  -> State: 1.6 <-
    weather.rainState = not_raining
    rain_count = 0
    runinwindow.timer = 2
  -> State: 1.7 <-
    runinwindow.timer = 1
  -- Loop starts here
  -> State: 1.8 <-
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 1.9 <-

smoke_fix2

INVAR
!(flag1 = TRUE & flag2 = FALSE) 也不行

NuSMV > check_ltlspec -p "G((smoke=detected)->!X(window.switch=open))"
-- specification  G (smoke = detected -> !( X window.switch = open))  is false
-- as demonstrated by the following execution sequence
Trace Description: LTL Counterexample
Trace Type: Counterexample
  -> State: 1.1 <-
    window.switch = close
    weather.rain = not_raining
    weather.rainState = not_raining
    rain_count = 1
    smoke = detected
    smokeState = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
    flag1 = FALSE
    flag2 = FALSE
    step = 1
  -> State: 1.2 <-
    window.switch = open
    rain_count = 0
    smokeState = detected
    smoke_count = 0
    delaywindow = 5
    step = 2
  -> State: 1.3 <-
    weather.rain = raining
    rain_count = 1
    runinwindow.timer = 5
    step = 3
  -> State: 1.4 <-
    window.switch = close
    weather.rainState = raining
    rain_count = 0
    runinwindow.timer = 4
    step = 4
  -> State: 1.5 <-
    weather.rain = not_raining
    rain_count = 1
    runinwindow.timer = 3
    step = 0
  -> State: 1.6 <-
    weather.rainState = not_raining
    rain_count = 0
    runinwindow.timer = 2
  -> State: 1.7 <-
    runinwindow.timer = 1
  -- Loop starts here
  -> State: 1.8 <-
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 1.9 <-

smoke_fix3(未实行) 改action

smoke_fix3

INVAR
!(flag1 = TRUE & flag2 = FALSE)
INVAR
!(flag1 = FALSE & flag2 = FALSE)

  -> State: 1.1 <-
    window.switch = close
    weather.rain = not_raining
    weather.rainState = not_raining
    rain_count = 1
    smoke = detected
    smokeState = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
    flag1 = FALSE
    flag2 = TRUE
    step = 1
  -> State: 1.2 <-
    window.switch = open
    rain_count = 0
    smokeState = detected
    smoke_count = 0
    delaywindow = 5
    step = 2
  -> State: 1.3 <-
    weather.rain = raining
    rain_count = 1
    runinwindow.timer = 5
    step = 3
  -> State: 1.4 <-
    weather.rainState = raining
    rain_count = 0
    runinwindow.timer = 4
    step = 4
  -> State: 1.5 <-
    weather.rain = not_raining
    rain_count = 1
    smoke = clear
    smoke_count = 1
    runinwindow.timer = 3
    step = 0
  -> State: 1.6 <-
    weather.rainState = not_raining
    rain_count = 0
    smokeState = clear
    smoke_count = 0
    runinwindow.timer = 2
  -> State: 1.7 <-
    runinwindow.timer = 1
  -- Loop starts here
  -> State: 1.8 <-
    window.switch = close
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 1.9 <-

smoke_2 step为6

close 不设置延迟,open可以设置延迟,先不设置延迟,相当于延迟的值为无限,只是打开窗户,如果无限时间都满足,那么短暂时间也满足。如果不满足就考虑延迟

-- specification  G (smoke = detected ->  X window.switch = open)  is false
-- as demonstrated by the following execution sequence
Trace Description: LTL Counterexample
Trace Type: Counterexample
  -> State: 1.1 <-
    window.switch = close
    weather.rain = not_raining
    weather.rainState = not_raining
    rain_count = 1
    smoke = detected
    smokeState = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 1.2 <-
    window.switch = open
    rain_count = 0
    smokeState = detected
    smoke_count = 0
    delaywindow = 5
  -> State: 1.3 <-
    weather.rain = raining
    rain_count = 1
    smoke = clear
    smoke_count = 1
    runinwindow.timer = 5
  -> State: 1.4 <-
    window.switch = close
    weather.rainState = raining
    rain_count = 0
    smokeState = clear
    smoke_count = 0
    runinwindow.timer = 4
  -> State: 1.5 <-
    smoke = detected
    smoke_count = 1
    runinwindow.timer = 3
  -> State: 1.6 <-
    weather.rain = not_raining
    rain_count = 1
    smokeState = detected
    smoke_count = 0
    runinwindow.timer = 2
  -> State: 1.7 <-
    weather.rainState = not_raining
    rain_count = 0
    smoke = clear
    smoke_count = 1
    runinwindow.timer = 1
  -- Loop starts here
  -> State: 1.8 <-
    smokeState = clear
    smoke_count = 0
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 1.9 <-

smoke_2_fix1

(weather.rainState != weather.rain)) &(weather.rain = raining) & (smoke = detected): open;

NuSMV > check_ltlspec -p "G((smoke=detected)->!X(window.switch=open))"
-- specification  G (smoke = detected -> !( X window.switch = open))  is false
-- as demonstrated by the following execution sequence
Trace Description: LTL Counterexample
Trace Type: Counterexample
  -> State: 1.1 <-
    window.switch = close
    weather.rain = not_raining
    weather.rainState = not_raining
    rain_count = 1
    smoke = detected
    smokeState = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
    flag1 = TRUE
    flag2 = FALSE
    flag3 = TRUE
    flag4 = TRUE
    flag5 = FALSE
    flag6 = FALSE
    step = 1
    step_uperlimit = 6
  -> State: 1.2 <-
    window.switch = open
    rain_count = 0
    smokeState = detected
    smoke_count = 0
    delaywindow = 5
    step = 2
  -> State: 1.3 <-
    weather.rain = raining
    rain_count = 1
    smoke = clear
    smoke_count = 1
    runinwindow.timer = 5
    step = 3
  -> State: 1.4 <-
    window.switch = close
    weather.rainState = raining
    rain_count = 0
    smokeState = clear
    smoke_count = 0
    runinwindow.timer = 4
    step = 4
  -> State: 1.5 <-
    smoke = detected
    smoke_count = 1
    runinwindow.timer = 3
    step = 5
  -> State: 1.6 <-
    weather.rain = not_raining
    rain_count = 1
    smokeState = detected
    smoke_count = 0
    runinwindow.timer = 2
    step = 6
  -> State: 1.7 <-
    weather.rainState = not_raining
    rain_count = 0
    runinwindow.timer = 1
    step = 0
  -- Loop starts here
  -> State: 1.8 <-
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 1.9 <-

smoke_2_fix2 冲突状态仍存在

!(flag1 = TRUE & flag2 = FALSE & flag3 = TRUE & flag4 = TRUE & flag5 = FALSE & flag6 = FALSE)

smoke_2_fix3 同上

!( flag1 = TRUE & flag2 = FALSE & flag3 = TRUE & flag4 = FALSE & flag5 = FALSE & flag6 = FALSE)

smoke_2_fix4

INVAR
!( flag1 = TRUE & flag2 = FALSE & flag3 = TRUE & flag4 = FALSE & flag5 = TRUE & flag6 = FALSE)

分析反例后
(weather.rain = raining)&(smokeState != smoke)&(smoke = detected) : open;
与 smokeState != smoke & smoke = detected & (weather.rain = not_raining): open;合并

因为无限都能满足,那么出于人性化可以设置为延时,这里无限满足不了

NuSMV > check_ltlspec -p "G((smoke=detected)->!X(window.switch=open))"
-- specification  G (smoke = detected -> !( X window.switch = open))  is false
-- as demonstrated by the following execution sequence
Trace Description: LTL Counterexample
Trace Type: Counterexample
  -> State: 1.1 <-
    window.switch = close
    weather.rain = not_raining
    weather.rainState = not_raining
    rain_count = 1
    smoke = detected
    smokeState = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
    flag1 = TRUE
    flag2 = FALSE
    flag3 = FALSE
    flag4 = TRUE
    flag5 = FALSE
    flag6 = TRUE
    step = 1
    step_uperlimit = 6
  -> State: 1.2 <-
    window.switch = open
    rain_count = 0
    smokeState = detected
    smoke_count = 0
    delaywindow = 5
    step = 2
  -> State: 1.3 <-
    weather.rain = raining
    rain_count = 1
    smoke = clear
    smoke_count = 1
    runinwindow.timer = 5
    step = 3
  -> State: 1.4 <-
    window.switch = close
    weather.rainState = raining
    rain_count = 0
    smokeState = clear
    smoke_count = 0
    runinwindow.timer = 4
    step = 4
  -> State: 1.5 <-
    smoke = detected
    smoke_count = 1
    runinwindow.timer = 3
    step = 5
  -> State: 1.6 <-
    window.switch = open
    weather.rain = not_raining
    rain_count = 1
    smokeState = detected
    smoke_count = 0
    runinwindow.timer = 2
    step = 6
  -> State: 1.7 <-
    weather.rainState = not_raining
    rain_count = 0
    runinwindow.timer = 1
    step = 0
  -- Loop starts here
  -> State: 1.8 <-
    window.switch = close
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 1.9 <-

smoke_3 delay也要跟着改,这里新增规则和原延时重合,不需要新增延时

step为8
特点runin=1在冲突的前一状态
7、8:不好好设置延时会导致规则执行完仍未消除smoke,smoke->规则执行结束的close。一直smoke

  -> State: 1.1 <-
    window.switch = close
    weather.rain = raining
    weather.rainState = not_raining
    rain_count = 1
    smoke = detected
    smokeState = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
  -> State: 1.2 <-
    window.switch = open
    weather.rainState = raining
    rain_count = 0
    smokeState = detected
    smoke_count = 0
    delaywindow = 5
  -> State: 1.3 <-
    weather.rain = not_raining
    rain_count = 1
    runinwindow.timer = 5
  -> State: 1.4 <-
    weather.rainState = not_raining
    rain_count = 0
    runinwindow.timer = 4
  -> State: 1.5 <-
    runinwindow.timer = 3
  -> State: 1.6 <-
    runinwindow.timer = 2
  -> State: 1.7 <-
    runinwindow.timer = 1
  -> State: 1.8 <-
    window.switch = close
    smoke = clear
    smoke_count = 1
    runinwindow.timer = 0
    delaywindow = 0
  -- Loop starts here
  -> State: 1.9 <-
    smokeState = clear
    smoke_count = 0
  -> State: 1.10 <-

smoke_4

属于无trigger,ruin不好弄的情况
抽象原规则,新规则,延时(无延迟0,固定时长和非固定),而且基于规则定期trigger和无法until的特性
抽象原规则不能解决就加延时,然后新规则,延时

    runinwindow.timer=1 & window.switch=open: close;
    smokeState != smoke & smoke = detected: {0,5};

将延时换为smokeState != smoke & smoke = clear & window.switch=open: close;

-> State: 1.1 <-
smoke = detected
smoke_last = clear
smoke_count = 1
window.switch = close
window.switch_last = close
weather.rain = not_raining
weather.rain_last = raining
weather.rain_count = 1
delay_window.switch_open_0 = 0
runin_window.switch_open_0.timer = 0
-> State: 1.2 <-
smoke_last = detected
smoke_count = 0
window.switch = open
weather.rain_last = not_raining
weather.rain_count = 0
delay_window.switch_open_0 = 5
-> State: 1.3 <-
smoke = clear
smoke_count = 1
window.switch_last = open
runin_window.switch_open_0.timer = 5
-> State: 1.4 <-
smoke_last = clear
smoke_count = 0
weather.rain = raining
weather.rain_count = 1
runin_window.switch_open_0.timer = 4
-> State: 1.5 <-
smoke = detected
smoke_count = 1
window.switch = close
weather.rain_last = raining
weather.rain_count = 0
runin_window.switch_open_0.timer = 3
-> State: 1.6 <-
smoke_last = detected
smoke_count = 0
window.switch_last = close
runin_window.switch_open_0.timer = 2
-> State: 1.7 <-
smoke = clear
smoke_count = 1
runin_window.switch_open_0.timer = 1
-> State: 1.8 <-
smoke_last = clear
smoke_count = 0
delay_window.switch_open_0 = 0
runin_window.switch_open_0.timer = 0
-> State: 1.9 <-
smoke = detected
smoke_count = 1
weather.rain = not_raining
weather.rain_count = 1

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
C语言是一种广泛使用的编程语言,它具有高效、灵活、可移植性强等特点,被广泛应用于操作系统、嵌入式系统、数据库、编译器等领域的开发。C语言的基本语法包括变量、数据类型、运算符、控制结构(如if语句、循环语句等)、函数、指针等。在编写C程序时,需要注意变量的声明和定义、指针的使用、内存的分配与释放等问题。C语言中常用的数据结构包括: 1. 数组:一种存储同类型数据的结构,可以进行索引访问和修改。 2. 链表:一种存储不同类型数据的结构,每个节点包含数据和指向下一个节点的指针。 3. 栈:一种后进先出(LIFO)的数据结构,可以通过压入(push)和弹出(pop)操作进行数据的存储和取出。 4. 队列:一种先进先出(FIFO)的数据结构,可以通过入队(enqueue)和出队(dequeue)操作进行数据的存储和取出。 5. 树:一种存储具有父子关系的数据结构,可以通过中序遍历、前序遍历和后序遍历等方式进行数据的访问和修改。 6. 图:一种存储具有节点和边关系的数据结构,可以通过广度优先搜索、深度优先搜索等方式进行数据的访问和修改。 这些数据结构在C语言中都有相应的实现方式,可以应用于各种不同的场景。C语言中的各种数据结构都有其优缺点,下面列举一些常见的数据结构的优缺点: 数组: 优点:访问和修改元素的速度非常快,适用于需要频繁读取和修改数据的场合。 缺点:数组的长度是固定的,不适合存储大小不固定的动态数据,另外数组在内存中是连续分配的,当数组较大时可能会导致内存碎片化。 链表: 优点:可以方便地插入和删除元素,适用于需要频繁插入和删除数据的场合。 缺点:访问和修改元素的速度相对较慢,因为需要遍历链表找到指定的节点。 栈: 优点:后进先出(LIFO)的特性使得栈在处理递归和括号匹配等问题时非常方便。 缺点:栈的空间有限,当数据量较大时可能会导致栈溢出。 队列: 优点:先进先出(FIFO)的特性使得

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

q1uTruth

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值