New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a diagram about ASPECT's architecture #1667
Comments
@bangerth I think @jdannberg has done something like this in her tutorial slides "Modularity". Can someone review and modify as per above? |
This is not a bad graph, but there are about a dozen plugin systems that are responsible for the "Model setup" part. Some of them also require feedback from the simulator. |
Julianne does have a more complicated version of this but I think there is a middle ground of something that gives the user a general overview as well as enough detail about the “parts”
Best,
-Lorraine
*****************************
Lorraine Hwang, Ph.D.
Associate Director, CIG
530.752.3656
… On May 16, 2017, at 6:58 AM, Wolfgang Bangerth ***@***.***> wrote:
This is not a bad graph, but there are about a dozen plugin systems that are responsible for the "Model setup" part. Some of them also require feedback from the simulator.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#1667 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AESQX22rLhH72KIpPPYIqSbRKdieeGW4ks5r6auLgaJpZM4Nak_U>.
|
If I have a fifteen minute break today, I may just come up with a way to create the graph from ASPECT internals. Each plugin system should be able to tell about itself what we need for this graph. |
This is a screen shot from @jdannberg tutorial presentation 'aspect_tutorial_slides.pdf'. |
@jdannberg -- how did you make this graph? Do you still have the sources? I'd like to put something like this into the manual. |
This can now be closed. |
@ljhwang asked whether there is a diagram that explains the structure of the ASPECT. There isn't, but it should not actually be very difficult to generate one.
In essence, we have the following structure:
Simulator
classSimulator
class, calledSimulatorAccess
. So there would be an arrow fromSimulator
toSimulatorAccess
.Simulator
, so there should be an arrow from each of these interfaces to theSimulator
.SimulatorAccess
, so there may be an arrow from the latter to the former.@ljhwang -- I guess this is too abstract to draw a graph? Or is it good enough?
The text was updated successfully, but these errors were encountered: