Heat/Reheat controls for ForceGraph #36
Labels
Milestone
Comments
zwelz3
added
documentation
|
Unsure how this is related to #28, but there may be some overlap. |
zwelz3
changed the title
|
Yerp, #28 (and by extension #35) probably handles this with the We also clobbered a lot of jitter when various traits change, which should result in snappier updates. |
|
https://ipyforcegraph--35.org.readthedocs.build/en/35/_static/lab/index.html?path=Forces.ipynb (recommend opening this in a "private browsing" session so you don't get weird cache artifacts) |
|
(also note that notebook is very much a work-in-progress... running past the couple cells right after Warmup and Cooldown will blow away the linked configuration) |
Closed
dfreeman06
pushed a commit
that referenced
this issue
Feb 21, 2023
dfreeman06
pushed a commit
that referenced
this issue
Feb 21, 2023
nrbgt
added a commit
to nrbgt/ipyforcegraph
that referenced
this issue
Feb 22, 2023
nrbgt
added a commit
that referenced
this issue
Feb 23, 2023
dfreeman06
pushed a commit
that referenced
this issue
Feb 24, 2023
nrbgt
added a commit
that referenced
this issue
Feb 24, 2023
* gh-36 adding manual reheating control * gh-36 added reheat ui to the other force behaviors * Gh 36 rereheating (#55) * rework envs for performance in CI, Binder, RTD (#53) * hoist action messages to type, add totality check * more badge * fix links * add reheat robot test * skip more osx tests * skip more osx tests --------- Co-authored-by: Dane Freeman <dane.freeman@gtri.gatech.edu> Co-authored-by: Nicholas Bollweg <nicholas.bollweg@gtri.gatech.edu>
dfreeman06
added a commit
that referenced
this issue
Feb 24, 2023
* gh-33 initial dag behavior * gh-33 fix notebook names * gh-33 linting and other code quality check fixes * gh-33 simple DAG unit test * gh-33 fixing tests * gh-33 dag test * gh-36 adding manual reheating control * gh-36 added reheat ui to the other force behaviors * Gh 36 rereheating (#55) * rework envs for performance in CI, Binder, RTD (#53) * hoist action messages to type, add totality check * more badge * fix links * add reheat robot test * skip more osx tests * gh-33 refactoring dag to better fit as a 'force' * gh-33 fix dag api check test * gh-33 fixing dag robot test * skip more osx tests * Update dictionary.txt * gh-33 fixed notebook dag function naming. updated changelog. * gh-33 updating dag traitlet help --------- Co-authored-by: Dane Freeman <dane.freeman@gtri.gatech.edu> Co-authored-by: Nicholas Bollweg <nicholas.bollweg@gtri.gatech.edu>
|
Fixed by #65 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Elevator Pitch
The ability to control the simulation heat/reheat parameters when making changes to the source and/or behaviors. A method for ex. pausing the simulation when applying certain style changes (e.g. node color), and a recommended design patter (within docs?) for how to achieve this desired effect.
Motivation
We are developing apps using ipyforcegraph, and updating this such as node/edge visibility, color, and other styles (as part of the ipyforcegraph supported behaviors) causes the visualization to "reheat" the graph layout. Under certain conditions it would be valuable to allow users of ipyforcegraph to control the heat settings so that operations can be performed on the source and behaviors without causing the visualization to reheat. A recommended implementation from the dev team will help ensure that the most effective manner for controlling these options is used downstream.
Design Ideas
Possibly set the config on the ForceGraph class (simplified e.g.
fg.reheat = False) before modifying behaviors/source/etc.The text was updated successfully, but these errors were encountered: