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
Is your request related to a problem? Please describe.
Currently the benchmark statement is pretty useful to compare things "manually" but it is not meant to be handled programmatically.
For example if I want to study the impact of one variable on the average execution time using this statement, I will have to copy the content of the console into an external text editor and do a lot of string manipulation to transform it into something usable like a csv to display it as a chart in yet another program. Which is a bit sad because we have all the data available in gama and the tools to display it (or export to csv if I need more serious external tools) but everything ends up in the console.
Describe the improvement you'd like
My proposal is that we add a facet to the benchmark statement to store the duration of each repetition into a list, and maybe another one to turn on or off the writing into the console. This way we could let the user manipulate the results however they want and possibly calculate other metrics they are interested into like standard deviation.
Describe alternatives you've considered
Switch from a statement into an operator that will either return the string we currently have, or a list of duration, depending on the options we set. That would be preferable in my opinion but that would also break previous models using it and probably will take more time implementing
The text was updated successfully, but these errors were encountered:
Is your request related to a problem? Please describe.
Currently the
benchmark
statement is pretty useful to compare things "manually" but it is not meant to be handled programmatically.For example if I want to study the impact of one variable on the average execution time using this statement, I will have to copy the content of the console into an external text editor and do a lot of string manipulation to transform it into something usable like a csv to display it as a chart in yet another program. Which is a bit sad because we have all the data available in gama and the tools to display it (or export to csv if I need more serious external tools) but everything ends up in the console.
Describe the improvement you'd like
My proposal is that we add a facet to the
benchmark
statement to store the duration of each repetition into a list, and maybe another one to turn on or off the writing into the console. This way we could let the user manipulate the results however they want and possibly calculate other metrics they are interested into like standard deviation.Describe alternatives you've considered
Switch from a statement into an operator that will either return the string we currently have, or a list of duration, depending on the options we set. That would be preferable in my opinion but that would also break previous models using it and probably will take more time implementing
The text was updated successfully, but these errors were encountered: