Christopher @cjquijano, Ben @BenLewis,
very valid suggestions! I can definitely see the value of making the Simulation <-> Run “relationship” more powerful. I created a feature request for it, will keep you updated.
Regarding the Simulation Run concept in general: On desktop systems, the traditional way of “running” a simulation is that specific simulation settings are executed and when I’m changing those settings afterwards, the UI indicates that the simulation results are “outdated”. So the “Simulation run” concept was introduced on SimScale due to the fact that with a cloud based solution, you can kick off many different simulations in general. So to keep track of all the different settings and the results that have been generated with it, this immutable “Settings Snapshot” concept was introduced.
Now in user interviews and user experience tests, I’ve seen different usage types of the run concept. Some use it primarily for “debugging” a simulation, so the difference from run to run within a simulation is only some parameter tweaking to get an accurate solution. Others use it to actually run a parameter study, say 5 different inlet velocities of a flow sim. I’ve rarely seen someone changing the mesh from run to run.
For what do you use primarily the runs on SimScale? Understanding better the strengths and drawbacks of it and for what it’s used would help to develop it into the right direction!
Thanks in advance for the feedback!