- edited description
Create flow diagram of how the system components work together
I would find it useful to have a diagram that shows how the system components work together. For example:
Populating the database
- Modality sends DICOM objects to OpenREM's store SCP
- The store SCP (Conquest in my case) applies the rules in dicom.ini to each object
- Data from the object is extracted by the appropriate python script or the object is deleted if the extraction rules don't apply
- Calculation of skin dose map occurs if appropriate / possible
- The object is deleted from OpenREM's store
There could be other diagrams for other elements of the system.
Read the docs has Graphviz built-in that can help with this. See http://build-me-the-docs-please.readthedocs.io/en/latest/Using_Sphinx/UsingGraphicsAndDiagramsInSphinx.html
Test doc page to see with in progress: http://docs.openrem.org/en/docsdiagrams/testgraphviz.html
Comments (43)
-
reporter -
reporter User guides and examples:
-
reporter Added a new diagram of the system components. References issue
#448→ <<cset 28016cf53acd>>
-
reporter Adjusted data extraction diagram to make style match the other one. Also added tooltips. References issue
#448→ <<cset cf876bd08130>>
-
reporter Adjusting style of second diagram. References issue
#448→ <<cset 6cf6d569b8b1>>
-
- edited description
-
reporter The tooltips on the second diagram are incorrect - they are duplicates of the tips from the first diagram. It may be that we can only have one diagram per webpage.
See http://docs.openrem.org/en/docsdiagrams/testgraphviz.html
@edmcdonagh, do you have any corrections / omissions / additions to what is there so far?
-
reporter There's a list of flowchart shapes here: http://www.conceptdraw.com/How-To-Guide/picture/Designelements-Flowchart.png
I'll adjust the shapes used for each node in the diagrams to better match what is shown in the link above, using the available default shapes (http://www.graphviz.org/doc/info/shapes.html)
-
reporter Updating shapes; removing commas. References issue
#448→ <<cset 739d3daa03e5>>
-
reporter Trying to sort out size issue. References issue
#448→ <<cset ff024cb1defb>>
-
reporter Trying to sort out size issue. References issue
#448→ <<cset 950a2d771ecd>>
-
reporter Trying to sort out size issue. References issue
#448→ <<cset cfb39cd2a9aa>>
-
reporter Trying to sort out size issue and some shapes. References issue
#448→ <<cset 8c9108d27068>>
-
reporter Trying to sort out size issue and some shapes. References issue
#448→ <<cset 934c8cb3028d>>
-
reporter Trying to sort out size issue and some shapes. References issue
#448→ <<cset b60dfa02609a>>
-
reporter Moved Conquest into the server cluster; relabelled the cluster as "Server" to be consistent with other diagram. References issue
#448.→ <<cset 4e47c4198918>>
-
reporter This site is useful to play with the diagram language: http://www.webgraphviz.com/
-
Is there a system behind the shape choices?
-
reporter -
reporter @edmcdonagh, it would be good to use a proper database symbol for PostgreSQL, but "shape=cylinder" doesn't work on the existing read the docs install. The cylinder shape is now available (http://www.graphviz.org/mantisbt/view.php?id=1867). Is there a way of updating the version of graphviz that read the docs is using so that the cylinder works?
-
reporter Combined the two diagrams into one. References issue
#448→ <<cset 08af94562b0d>>
-
Seeing if demanding a later version of sphinx will get a later version of graphviz. Refs
#448→ <<cset d8ecd2991952>>
-
Didn't work, reverting sphinx version requirement. Even the Sphinx v1.5 docs are produced using Sphinx 1.3.5! Refs
#448→ <<cset a074100b5c3a>>
-
No, I don't see a way of doing this @dplatten. Sorry. Maybe a stack-overflow question?
-
reporter OK - thanks for checking. I don't think it matters too much for the time being.
-
reporter Putting all server nodes in the same cluster to make layout more straightforward for me. References issue
#448.→ <<cset 9f2f51b1322a>>
-
Forgot to reference the issue in the commit: 8d820b4
-
Added alternatives information. Refs
#448→ <<cset 0c3cb8c5b1bf>>
-
Minor mod to wording. Refs
#448→ <<cset e28626427a58>>
-
reporter Updated the layout using two blank nodes and some additional ranking to force a specific horizontal order.
I found the information on forcing a horizontal order here: http://stackoverflow.com/questions/14123259/how-to-enforce-the-left-to-right-node-ordering-in-graphviz-rank-layout
References issue
#448.→ <<cset a755508368aa>>
-
reporter Made nodes a little smaller, and reduced font size. I'm not able to produce a good-looking chart that is much narrower than this at the moment. May re-visit this at the weekend. References issue
#448→ <<cset 3531fd952b50>>
-
reporter Reverted to larger text size. I'd like to let the user click on the diagram and it open full-size in a new window. References issue
#448→ <<cset e845c6d7160a>>
-
reporter - changed status to resolved
Updated name of diagram document. Updated link from index. Updated changes files. Fixes issue
#448→ <<cset feff2d69be99>>
-
Refs
#448Adds study time to the CT export module with correct formatting for time and date.
→ <<cset c4176fc34ed0>>
-
Hi David. Can we modify this to indicate ISIS for Windows and nginx+gunicorn for Linux?
-
reporter Updated system diagram in the documents to reflect new recommendations on web servers. Also amended database text. References issue
#448, issue#592and issue#596→ <<cset 33b5ea83d5ae>>
-
reporter Amended heading underline. References issue
#448→ <<cset e4b049d1cf90>>
-
reporter @edmcdonagh, would you create a documentation set for the issue448UpdateSystemDiagram branch so that I can check that the changes I've made haven't broken anything?
-
-
Thanks, by the way :)
-
reporter Removed link to installing Apache - this is referred to in the web server link anyway. References issue
#448, issue#592and issue#596→ <<cset 69357c5ea463>>
-
Merged in issue448UpdateSystemDiagram (pull request #171)
Issue448UpdateSystemDiagram
Approved-by: Ed McDonagh ed@mcdonagh.org.uk
→ <<cset f828c783af9e>>
-
- changed milestone to 0.8.0
- Log in to comment