UMDES Software Library File Formats

Input File Formats

The description of each element is found in red within { } 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 describe 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 event.uc inputs.
4
{# States}

VC
{State} 		1/0
{Marked/Unmarked} 		4
{# Transitions}
SC1
{Event} 		VSC
{New State}
CVVC
OVVO
SO1VSO

VO04
... ...
... ...
Optionally, additional eventsnot appearing in transitions can be added to a machine. To do this, after the last state and transition, add a new line begining with the key work 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 the 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}
S1S2a.5
S1S2b.5
S2S4e.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
{State} 		PNP,NF
{Sensor values at this state}
C9,V3,P3,F2,B2,L1PPP,F
C9,V3,P4,F2,B2,L1PNP,NF
C9,V4,P3,F2,B2,L1PPP,NF
... ...
... ...

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
{State components} 		PNP,NF
{Sensor1,Sensor2} 		{Assigns all states containing string P1 to have sensor values PNP,NF}
P4
{State components} 		PNP,NF
{Sensor1,Sensor2} 		{Assigns all states containing string P4 to have sensor values PNP,NF}
V2,P3
{State components} 		PNP,NF
{Sensor1,Sensor2} 		{Assigns all states containing string V2,P3 to have sensor values PPP,F}
... ...
... ...

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 of mapping}

CV
{Indicator event} 		1
{Failure type}
OV2
POFF3
PON4
... ...
... ...

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
{Unobservable event} 		1
{Failure type}
SC21
SO12
SO22
... ...
... ...
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.

Output File Formats

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 the diagnoser written in a standard fsm format.

Simplified Diagnoser

The simplified diagnoser has the following changes from the regular diagnoser format:
Total Diagnoser States = 33

Id = 1
{Diagnoser State ID 1}
Certain:
{Failure types that are certain}
Uncertain: N F1
{Failure 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
... ...
... ...

Fi-indeterminate cycles

The first line of the dcycle output is the first Fi-indeterminate cycle. The id's 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
{1st D State} 		d
{Failure event} 		->
2
{2nd D State} 		n
{Failure event} 		->
3
{3rd D State} 		g
{Failure event} 		->
4
{1st D State}
Uncertain: F1
{Uncertain failure types in cycle}
Diagnoser State 4 contains the following FSM states:
5
{FSM State}
10
{FSM State}
12
{FSM State}
... ...
... ...

Fi-Indeterminate Cycles for Multiple Failure Diagnoser and (Fi,Ii)-Indeterminate Cycles

6
{1st D_State} 		4
{2nd D_State} 		5
{3rd D_State}
... ...
... ...

Contact Information: Please e-mail questions to umdeslib-support@eecs.umich.edu. Although we are unable to provide full technical support, we will do our best to help.