Output File Formats

From DESUMA Wiki
Output File Formats
Jump to: navigation, search
Line 1: Line 1:
 
The description of each element is found in italics with { } directly underneath it.<br />
 
The description of each element is found in italics with { } directly underneath it.<br />
  
=== Diagnoser<br /> ===
+
== Diagnoser<br /> ==
  
  
Line 49: Line 49:
  
  
=== Diagnoser FSM ===
+
== Diagnoser FSM ==
  
  
Line 64: Line 64:
 
{Diagnoser State ID 1}
 
{Diagnoser State ID 1}
  
Certain:
+
CertThe description of each element is found in italics with { } directly underneath it.
 +
Individual FSM
 +
 
 +
The default for each event (transition) is controllable and observable (c and o). If an event is uncontrollable and unobservable, you may specify so after the new state with 'uc' and 'uo'. If the event is either uncontrollable but observable or unobservable but controllable, you may simply state the variable ('uc' or 'uo') that describes the negative characteristic. Please note that you may ignore 'uc' and 'uo' completely if you choose to create the unobservable events file manually by writing this text file. If you choose to use the routine write_uo, you have to state the event properties in the machine.fsm files. Also, the program called "add_prop" adds the uc and uo properties to all events in the FSM file based on the events.uo and events.uc inputs.
 +
 
 +
4                                                                                                                                                                            {# of states}
 +
 
 +
VC          1/0                            4                                                                                                                                  {State}    {Marked/Unmarked}  {# of Transitions}
 +
 
 +
SC1        VSC                                                                                                                                                                                          {Event}    {New State}
 +
 
 +
CV          VC
 +
 
 +
.....          ......
 +
 
 +
Optionally, additional events not appearing in transitions can be added to a machine. To do this, after the last state and transition, add a new line beginning with the key word EVENTS. After this line, additional events can be listed in the format for an event list. i.e. to add uncontrollable and unobservable event 'a' to an FSM, add the following at he end of the file.
 +
 
 +
EVENTS
 +
 
 +
a uc uo
 +
Stochastic Information for an FSM
 +
 
 +
The machine.stoc file can be created using the create_sfsm routine. You need to have the machine you want to add probabilities to already created.
 +
 
 +
{FROM STATE name} {TO STATE name} {EVENT name} {Probability}
 +
 
 +
S1                              S2                        a                      0.5
 +
 
 +
S1                              S2                        b                      0.5
 +
 
 +
S2                              S4                        e                      0.7
 +
 
 +
.....                            ......                      ......                    ......
 +
 
 +
In the above g.ft, we have partitioned {Stuck Closed 1, Stuck Closed 2} as failure type 1 and {Stuck Open 1, Stuck Open 2} as failure type 2.
 +
Sensor Data Map (compose)
 +
 
 +
The sensor data map contains the state of each sensor for every state of the system. For large systems part of the map creation process can be automated using sensmap. The sensor data map contains one line for each state and corresponding sensor values.
 +
 
 +
C9, V1, P4, F2, B2, L1  PNP, NF                                                                                                                          {State}                          {Sensor values at this state}
 +
 
 +
C9, V3, P3, F2, B2, L1  PPP, F
 +
 
 +
.... ....                            .... ....
 +
Global Sensor Map for the System (sensmap)
 +
 
 +
Sensmap is a utility to help automate the creation of sensor data maps for use with the compose routine. For each state in the global sensor map, sensmap searches for states in the system with that state as a substring. It then assigns the corresponding sensor values to that FSM state. The states in the global sensor map must have components ordered the same way as in sync.fsm.
 +
 
 +
10                                                                                                                                                                      {# of pairs of mapping}
 +
 
 +
P1                            PNP, NF                                                                                                                      {State Components}  {Sensor1, Sensor2} {Assigns all states containing string p1 to have sensor values PNP,NF}
 +
 
 +
P4                            PNP, NF                                                                                                                      {State Components}  {Sensor1, Sensor2} {Assigns all states containing string P4 to have sensor values PNP, NF}
 +
 
 +
.... ....                        .... ....
 +
Events Map for the System (I-Diagnosability)
 +
 
 +
Events.ift contains information about the indicator events and the failure partition each indicator event detects.
 +
 
 +
6                                                                                                                                                                  {# of pairs mapping}
 +
 
 +
CV                    1                                                                                                                              {indicator event}  {Failure Type}
 +
 
 +
OV                    2
 +
 
 +
... ...                ... ...
 +
Failure Partition for Building Diagnoser
 +
 
 +
The g.ft data file can be created from the sync.uo. From the sync.uo, we append the failure type for each unobservable event.
 +
 
 +
SC1                          1                                                                                                                    {Unobservable Event}  {Failure Type}
 +
 
 +
SC2                          1
 +
 
 +
SO1                          2
 +
 
 +
... ...                        ... ...
 +
 
 +
In the above g.ft, we have partitioned {Stuck Closed 1, Stuck Closed 2} as failure type 1 and {Stuck Open 1, Stuck Open 2} as failure type 2.ain:
  
 
{Failure types that are certain}
 
{Failure types that are certain}
Line 87: Line 165:
  
  
=== Fi-indeterminate cycles ===
+
== Fi-indeterminate cycles ==
  
  
Line 114: Line 192:
  
  
===Fi-indeterminate Cycles for Multiple Failure Diagnoser and (Fi,li)-indeterminate Cycles ===
+
== Fi-indeterminate Cycles for Multiple Failure Diagnoser and (Fi,li)-indeterminate Cycles ==
  
  

Revision as of 18:11, July 29, 2013

The description of each element is found in italics with { } directly underneath it.

Contents

Diagnoser

Total Diagnoser States = 33 Id = 1

{Diagnoser State ID = 1}

V1, P3, C1 F4

{FSM State}

V1, P3, C1 F1F4

{FSM State}

Total pairs = 2

{# Pairs in diagnoser state}

Certain: F4

{Failure (and indicator) types that are certain}

Uncertain: F1

{Failure (and indicator) types that are uncertain}

OV, PP, F -> 10

{Event transition and next diagnoser state}

OV, PP NF -> 8

{Event transition and next diagnoser state}

PP, NF -> PP, F -> 4

{Event transition and next diagnoser state}

Id = 2

... ...

... ...


Diagnoser FSM

The diagnoser FSM is written in the standard standard fsm format. Simplified Diagnoser The simplified diagnoser has the following changes from the regular diagnoser format: Each diagnoser state has the following format: ID number, followed by a Certain attribute field, followed by an Uncertain attribute field, followed by the next events and states. The list of state, label pairs that are present in the regular diagnoser format, as well as the total pairs field, is removed. Normal states are indicated by an empty Certain field and an empty Uncertain field. When the state label pairs include a normal sate along with other failed states, a N label appears in the Uncertain field. Total Diagnoser States = 33 Id = 1

{Diagnoser State ID 1}

CertThe description of each element is found in italics with { } directly underneath it. Individual FSM

The default for each event (transition) is controllable and observable (c and o). If an event is uncontrollable and unobservable, you may specify so after the new state with 'uc' and 'uo'. If the event is either uncontrollable but observable or unobservable but controllable, you may simply state the variable ('uc' or 'uo') that describes the negative characteristic. Please note that you may ignore 'uc' and 'uo' completely if you choose to create the unobservable events file manually by writing this text file. If you choose to use the routine write_uo, you have to state the event properties in the machine.fsm files. Also, the program called "add_prop" adds the uc and uo properties to all events in the FSM file based on the events.uo and events.uc inputs.

4 {# of states}

VC 1/0 4 {State} {Marked/Unmarked} {# of Transitions}

SC1 VSC {Event} {New State}

CV VC

..... ......

Optionally, additional events not appearing in transitions can be added to a machine. To do this, after the last state and transition, add a new line beginning with the key word EVENTS. After this line, additional events can be listed in the format for an event list. i.e. to add uncontrollable and unobservable event 'a' to an FSM, add the following at he end of the file.

EVENTS

a uc uo Stochastic Information for an FSM

The machine.stoc file can be created using the create_sfsm routine. You need to have the machine you want to add probabilities to already created.

{FROM STATE name} {TO STATE name} {EVENT name} {Probability}

S1 S2 a 0.5

S1 S2 b 0.5

S2 S4 e 0.7

..... ...... ...... ......

In the above g.ft, we have partitioned {Stuck Closed 1, Stuck Closed 2} as failure type 1 and {Stuck Open 1, Stuck Open 2} as failure type 2. Sensor Data Map (compose)

The sensor data map contains the state of each sensor for every state of the system. For large systems part of the map creation process can be automated using sensmap. The sensor data map contains one line for each state and corresponding sensor values.

C9, V1, P4, F2, B2, L1 PNP, NF {State} {Sensor values at this state}

C9, V3, P3, F2, B2, L1 PPP, F

.... .... .... .... Global Sensor Map for the System (sensmap)

Sensmap is a utility to help automate the creation of sensor data maps for use with the compose routine. For each state in the global sensor map, sensmap searches for states in the system with that state as a substring. It then assigns the corresponding sensor values to that FSM state. The states in the global sensor map must have components ordered the same way as in sync.fsm.

10 {# of pairs of mapping}

P1 PNP, NF {State Components} {Sensor1, Sensor2} {Assigns all states containing string p1 to have sensor values PNP,NF}

P4 PNP, NF {State Components} {Sensor1, Sensor2} {Assigns all states containing string P4 to have sensor values PNP, NF}

.... .... .... .... Events Map for the System (I-Diagnosability)

Events.ift contains information about the indicator events and the failure partition each indicator event detects.

6 {# of pairs mapping}

CV 1 {indicator event} {Failure Type}

OV 2

... ... ... ... Failure Partition for Building Diagnoser

The g.ft data file can be created from the sync.uo. From the sync.uo, we append the failure type for each unobservable event.

SC1 1 {Unobservable Event} {Failure Type}

SC2 1

SO1 2

... ... ... ...

In the above g.ft, we have partitioned {Stuck Closed 1, Stuck Closed 2} as failure type 1 and {Stuck Open 1, Stuck Open 2} as failure type 2.ain:

{Failure types that are certain}

OV, PP, F ->10

{Event transition and next diagnoser state}

OV, PP, NF -> 8

{Event transition and next diagnoser state}

PP, NF -> PP, F -> 4

{Event transition and next diagnoser state}

Id = 3

... ...

... ...


Fi-indeterminate cycles

The simplified diagnoser has the following changes from the regular diagnoser format: The first line of the dcycle output is the first Fi-indeterminate cycle. The Ids of the diagnoser state followed by the transitions to the next state are linked together with a '->'. The uncertain failure types in the cycle and the FSM states which compose each diagnoser state are then listed.

4 d -> 2 n -> 3 g -> 4

{1st D state} {Failure event} {2nd D State} {Failure Event} {3rd D state} {Failure event} {Failure event}

Uncertain: F1

{Uncertain failure types in cycle}

Diagnoser State 4 contains the following FSM states:

5

10

12

... ...

... ...


Fi-indeterminate Cycles for Multiple Failure Diagnoser and (Fi,li)-indeterminate Cycles

6 4 5 {1st D_state} {2nd D_state} {3rd D_state}

... ...

... ...

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
EECS @ UM
Tools