-
Notifications
You must be signed in to change notification settings - Fork 3
Improve Pathway Map
Major issues coming out of the discussion with Marjolijn and Julius [fixed, needs implementation]:
- Open circles for Tipping Points
- Optimize positioning of measures
- Allow for manual adjustment of positions of measures
- Shift vertical lines so that they are not on top of each other
- Shift horizontal lines if there are different tipping points
- Continue with colour horizontal parallel lines if measures are combined
- If measure replaced, or are not combined then only the colour of the last measure
- Option to show multiple scenarios in one plot
We managed to write code around all these issues and would like to see them implemented as part of the Pathways Generator Package.
Other potential additions to the package [still under development]:
- Allowing for interactive plots using plotly with additional meta-information
Other remaining issues are:
- Allow to do all above in the GUI
- Module to generate pathways from a list of measures
Start point of the trajectory is the current output for classic layout of the pathways
So, as an example of list of issues is now:
What is the issue: The circles for the begin point should be closed, the circles for the end point should be open. How addressed: Network objects are processed and converted into dictionaries to create lists for Begin and End markers.
Marjolijn: I prefer open at the beginning and vertical tipping points at the end. Also if we have different preferences, why not let the user decide?
Follow-up issues: Option to allow for different marker types ?
What is the issue: Originally the positioning of the measures is determined by the order in which they are listed in the sequence input file.
How addressed: Minimizing vertical distance between markers at same x-positions.
Follow-up issue: Advanced optimization rules. Allowing to indicate certain measures being positioned that should be positioned next to each other (or at opposite locations).
What is the issue: Allowing to manually adjust the position of one (or multiple) measures.
How it addressed: Option to specify a dictionary to swap two (or multiple) measure pairs or providing a complete new order. Follow-up issue: None
What is the issue: Create measure specific offset in x-direction to avoid that vertical lines (transitions to implement measures) overlap.
(See previous figures, already visible there.)
How it is addressed: Based on maximum offset in x-direction, each measure gets a unique offset around the 0-offset line
Follow-up issue: Make this continuous for all active measures. Currently the vertical lines are only based on the measure if the tipping point. Problem: Again overlapping vertical lines again means loosing insight where we came from.
What is the issue: Current version does not provide information on replacing measures. Information on specific pathways is lost because of overlaying.
How it was addressed: Input file for sequence was adjusted (adding a separate column indicating pathways numbers in which the specific combination is part of. Based on tipping point for different instances of same pathway check whether lines overlayed or not. Adding an equally spaced offset in y-direction based on the maximum number of unique instances of any measure in the set.
Future Issue: Making sure that the first measure implemented after current always has 0 offset. Right now the 0 offset is random (optimized). As a result, the alignment of ytick labels and the first marker is off.
What is the issue: The current pathways generator does not allow to provide any indication of whether a new measure replaces old measures or if it is combined.
How it was addressed: Adding a dictionary, in which it is specified for each measure whether or not it replaces any other measure(s). Plotting multiple horizontal lines unless the most recently added measure replaces one of the others.
What is the issue: In order to show shifts in tipping points from one scenario to another, an option should be to overlay two pathways maps to show the differences.
How it was addressed: Allowing to specify a base map and an overlay map with different properties for visualization
What is the issue: Allowing for interactive pathways map to highlight specific pathways and get additional meta-data on tipping points/pathways
How it was addressed: Using Plotly and doing some modifications in JavaScript to allow for customdata-targeted hover-behavior.
Potential future issue: Nice to combine with scorecard to highlight certain pathways and their performance.