Add mapping-tester repetitions as separate script#226
Conversation
e7d25e5 to
56c6802
Compare
davidscn
left a comment
There was a problem hiding this comment.
There is currently no option to recover details about individual runs, once all repetitions are completed, right? Or do we store the json file?
There was a problem hiding this comment.
I think with this we should also provide a script to process the data statistically across various runs, no?
|
The script currently doesn't clean up intermediates. Running it for 5 repetitions results in: The various |
davidscn
left a comment
There was a problem hiding this comment.
Ah ok. I think then this essentially a python version of what I once implemented in bash. The nice thing about the bash script was actually that it served a central steering component around all the scripts in the mapping tester. However, you can still add the repetition script provided here, as one can still use the bash version as a central instance if deemed necessary
|
Will add this as a separate PR. Adding backends for both polars and pandas makes this a bit painful. |
9f96fc4 to
56c6802
Compare
56c6802 to
db0b01b
Compare
|
Rebased on develop after merging #225. I'll merge after the tests pass. |
Main changes of this PR
Based on #225
Replaces #195
This PR adds a separate python script
repeat.pyto the mapping tester to handle repetitions, which are useful for runtime measurements.It repeats for each repetition:
file-n.csvThen it merges all N
file-n.csvinto a singlefile.csv.The column
runindicates which repetition it was.Author's checklist
pre-commithook and usedpre-commit run --allto apply all available hooks.docs/README.md../changelog-entries/(create if necessary).precice/tutorials/aste-turbine.