troeger / fuzzed Goto Github PK

The client JavaScript code breaks if

• topEvent or intermediateEvent have a property [0, 0]
• any event has more than one parent
• topEvent has other ID than 0

This should be covered by the importer sanity checks.

For instance, it is not obvious, what "Time" (timestamp?) and "Failures" (number of failures within the executed simulation rounds) means for the simulation result.
Suggestion for further tooltips: "Rounds": "Number of rounds simulated to obtain approximated reliability value" "Reliability": "Probability of the top event NOT occurring before the mission time" "MTTF" : "Mean Time To Failure" (maybe this one is obvious)

Based on a longer discussion in the team and with the potential users, here are the requirements:

• Graphs can be shared by multiple people, but only one of them can lock the graph for editing.
• Everybody else sees a regularly updated read-only version of the graph in the editor.
• This demands some UI extension for user sharing management.
• The updates are sent from the web server to the JS code vis WebSockets, in the moment were it receives the frontend API calls from the editing user.
• The update messages are formulated in a way that most JS code can be re-used (command pattern implementation.)

This should be an extension of the meanwhile existing static graph sharing UI.

If a model contains a PAND gate some simulation rounds are bound to never fail, which leads to "infinity" as failure time in some cases, and the mean is only well-defined over numbers not containing "infinity".

The MTTF should be something like NaN if a PAND gate is present.

When naming a basic event with a name including an underscore _, the resulting LaTeX document won't compile, and the pdf export does not return any file.

Dynamic gates should be converted to undeveloped events. Existing child edges from the dynamic gate should be removed, while leaving the subtree intact.

This can become part of the config backend engine.

Most obvious case is making the browser window smaller

The SVG thumbnail ids need to match the kind identifier used in the notations file in order to work with the nose.js implementation. So far the id string must be set manually while creating the SVG. Automize it by using Django template magic instead, and let the id be set automatically.

The analysis window should contain a slider for the decision of "Speed" <-> "Precision", which maps to a decomposition number between 1 and 10 (inclusive).
The chosen value must be stored as part of the graph state to configure the slider on the next run. The default value without any state in the graph is 2.

Right now just Repeated BasicEvents are supported. Make this generic for all events.

The simulated model should be persisted for further reference.

... and check the new version for it's multi selection capability, which could make some current hacks needless.

Very wide graphs become a problem for the PDF export.

Users may have some pseudo project with read-only example graphs.

For node / edge / group properties, the JS client code currently generates / expects the value wrapped in a separate dictionary with only one key. There is no visible advantage of that approach, and it demands some nasty workarounds in the fronted Tastypie code.
The proposal is to just send / receive JSON values as property value.

although mouse cursor provides a visual hint suggesting that column width can be increased, dragging the mouse only moves the entire result window (drag events are not delegated to the table?)

Currently, the doc page saving crashed when the text contains a unicode character.

• Introduce alert categories/identifier
• Do only allow a certain number of alerts of the same categorie/identifier to be displayed at a time

What happens if a shared graph has transfer in gates ? We should at least show a warning during the sharing that the 'imported' graphs must be shared too. In addition, the according access tests for the sharee must become part of the test suite.

It's no functional issue but just about visualizing the drag&drop-process.

We agreed to use a solution were the front-end internally translates grid coordinates to pixel coordinates for drawing. A custom zoom function would then just influence this re-calculation.
A first quick measurement shows that re-drawing the canvas after each zoom operation would be a reasonable solution for the viewport update.
Care must be taken regarding node sizes, mirror texts and selectability of items.

During faulttree simulation, a PNML file for the petri net is generated, saved and re-loaded.
Avoid this step to make simulation faster.

Instead of raising an issue for each configuration with an undeveloped event, please deliver a global issue telling that a number of configurations was ignored due to an undeveloped event in them. This would avoid a lot of unneccessary empty result values.

When multiple FDEP gates are attached to Basic Events, it is not clear which belong to which, since line crossings are not visualized. In the attached picture, the left hand side FDEP is not connected to the left hand side Basic Event, but this is not visualized.

This is currently broken due to the open source conversion of the project.

This is a cool project. The world should know it.

The connection rules are already defined by @laena, so it is basically about adding the shapes and tweaking the notations file.

Most of the nowadays identity providers switch from OpenId to OAuth2. Most notably:

• Facebook, Twitter, Google, Yahoo, Microsoft, Amazon
• See http://en.wikipedia.org/wiki/OAuth#List_of_OAuth_service_providers for a more detailed list
• However, need to change the frontend and backend authentication libraries.
• Porting existing password-less accounts is a serious problem with this idea.

if cursor is paced at the beginning/end of a text area (e.g. inside sticky note, properties menu ) the canvas will be moved to the left/right if the left/right arrow key was clicked

Most obvious case is making the browser window smaller

There should be the possibility to load the editor with a special token in the URL. By this, we would be able to utilize browsershots.org for editor loading tests.

Halos are iconic buttons, that are positioned around the node, they are belonging to.
Possible halo button are:

• Create a new node with an already set up edge to the halo's node
• Create a new node in the same node group (see #255)
• Delete the halo's node
• …