You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Acceleration is a big part of preCICE configuration files, but we currently have no visualization for it.
The question is how can we effectively visualize acceleration without adding too much clutter.
Problem I noticed for parallel schemes is that all exchanged data is accelerated (both directions), which makes a central node to represent the acceleration very confusing.
A simple option could be to add the information as a mouse-over to exchange tags and choose a different head/tail.
I think that 80% of the interesting part is which acceleration method we are using. For this, I would expect a box inside the coupling scheme with the name of the acceleration.
That box could then optionally include the XLM tags as text. This would allow someone to access these details when helping someone tune a case, without visually bloating too much the figure. Something like:
Could even just include a dump of the respective XML config, if that is easier to implement.
A simple option could be to add the information as a mouse-over to exchange tags and choose a different head/tail.
Please keep the CLI full-featured. Mouse-over elements would be nice for someone working on their computer, but it would make it difficult to interact with others.
Acceleration is a big part of preCICE configuration files, but we currently have no visualization for it.
The question is how can we effectively visualize acceleration without adding too much clutter.
Problem I noticed for parallel schemes is that all exchanged data is accelerated (both directions), which makes a central node to represent the acceleration very confusing.
A simple option could be to add the information as a mouse-over to exchange tags and choose a different head/tail.
More context
https://precice.org/configuration-acceleration.html
The text was updated successfully, but these errors were encountered: