I've seen examples where the "not" operator has no effect on the monitoring result. For example, consider the ros_stl_monitor.launch example launch file, which uses the spec.stl specification. If I change the existing specification
c.value = always (a.value <= 2)
by adding a not after always, like so
c.value = always not (a.value <= 2)
I get the same resulting robustness value output.
I've seen examples where the "not" operator has no effect on the monitoring result. For example, consider the ros_stl_monitor.launch example launch file, which uses the spec.stl specification. If I change the existing specification
c.value = always (a.value <= 2)
by adding a not after always, like soc.value = always not (a.value <= 2)
I get the same resulting robustness value output.