designengrlab/fmdtools

DEPRECATED: System modelling and fault-injection-based resilience assessment in Python

fmdtools's Issues

Add in ability to run joint-fault scenarios at different times

• propagate needs a method that simulates arbitrary sets of fault modes (((fxn1, fault1), time1),((fxn2, fault2), time2), etc)

graph.set_pos() makes it difficult to iteratively change the model structure

current behavior: set_pos always generates new node positions randomly
desired behavior: ability to re-use node positions from a previous version of the model

Need a smarter way of creating sample approach(es) using operational modes

• Model should incorporate function mode information (where mode is discrete changes in state) to automatically determine the phases of operation
• Fxnblock/Component classes should let one associate failure modes with operational modes in addition to/rather than phases
• Need more infrastructure for modes--visualizations of modes over time (e.g. overlaid on behavior graphs) and just the modes of the system at large

mdlhist doesn't form histories of states placed in dictionaries

State return should copy states instead of reference them, when possible

Empty model graphs don't return figures

modify line 170 to return figures/axes when desired?

pip installation does not install netgraph

Need to make sure that netgraph gets installed, otherwise resultdisp modules don't import

Formalize static/dynamic behavior order

Function execution order should differentiate dynamic behaviors (which should run at the end of each time-step according to specified run order) from static behaviors (which can still run/propagate in an un-directed sense)

Ideally this should result in a time-step running as follows:
1.) Run dynamic behaviors in specified order
2.) Run static behaviors (if any) in specified order, and then execute remaining blocks until it converges (current behavior)

Functions should be given helper methods for this which are called at different times. Ideally allows one to use the current behavior() and condfaults() interfaces while making the default dynbehavior() and statbehavior() (or whatever makes sense)

Suggestion.

I notice you have user modelling in your approach.

Have you considered using tool such as cogulator in parallel to capture the analysis if users and then perhaps parse cogulator files into your human component representation?

Need to be able to specify run order

Need to be able to specify run order of modules for dynamic models.

Recommend changing mdl.timelyfxns and activefxns in propagate to an ordered dict (or similar).

new netgraph major release

Hi,

I saw on the github dashboard that you are using my package netgraph.

This is a heads up that I just released a new major version. I tried to maintain backwards compatibility as much as possible but I did break it in a few cases. Especially if your code uses either the Graph or InteractiveGraph classes, expect a few changes. Also, I have removed some InteractiveGraph derived variants for the time being, as they seem to be used very little but are a pain to maintain. If that affects you, please let me know, so we can work something out.

Hopefully, you will find that the improvements that I have made are worth any pains that might arise from upgrading. ;-)

Best,
Paul

PS: Feel free to close the issue any time.