Hi MaMiCo development team,
just as a feature request / suggestion, an idea came to my mind:
I think, for debugging and development of new scenarios / couplings / features / applications - it might be very helpful to have a simple MaMiCo GUI?
Primary purpose of the GUI would be live visualization of MaMiCo data structures, i.e. coupling cell grid with indices and content data. This could simply be shown as a 2D matrix, where the index in the 3rd dimension is chosen by a slider and the cell attribute (such as density / velocity component) could be chosen from a drop-down menu. There should be buttons such as start simulation, stop simulation and run X coupling cycles, and the data in the coupling cell data window should be updated while the simulation is running.
As a second step, the GUI could also show all values and settings from XML configuration, and perhaps even allow to modify them while the simulation is running / before another time step is executed (this may require restarting of some services, but that feature will be needed for dynamic load balancing anyway).
The more data the GUI can display, the more useful it is going to be. For example, one might want to show the total number of particles, the average velocity of entire CFD domain, bounday condition setup, local MPI ranks, number of local MD instances ... But all of that can be added later. I think the GUI should simply always run on the CFD solver rank, so that it implicity uses MaMiCo' MPI commmunication features to collect MD data and shows the result of that communication.
Might be very helpful for debugging and development? What do you think?
Best, Piet
Hi MaMiCo development team,
just as a feature request / suggestion, an idea came to my mind:
I think, for debugging and development of new scenarios / couplings / features / applications - it might be very helpful to have a simple MaMiCo GUI?
Primary purpose of the GUI would be live visualization of MaMiCo data structures, i.e. coupling cell grid with indices and content data. This could simply be shown as a 2D matrix, where the index in the 3rd dimension is chosen by a slider and the cell attribute (such as density / velocity component) could be chosen from a drop-down menu. There should be buttons such as
start simulation,stop simulationandrun X coupling cycles, and the data in the coupling cell data window should be updated while the simulation is running.As a second step, the GUI could also show all values and settings from XML configuration, and perhaps even allow to modify them while the simulation is running / before another time step is executed (this may require restarting of some services, but that feature will be needed for dynamic load balancing anyway).
The more data the GUI can display, the more useful it is going to be. For example, one might want to show the total number of particles, the average velocity of entire CFD domain, bounday condition setup, local MPI ranks, number of local MD instances ... But all of that can be added later. I think the GUI should simply always run on the CFD solver rank, so that it implicity uses MaMiCo' MPI commmunication features to collect MD data and shows the result of that communication.
Might be very helpful for debugging and development? What do you think?
Best, Piet