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
In simulations with implicit coupling, the second participant writes a CSV file logging the number of iterations in every coupling time window: https://precice.org/running-output-files.html
We should be checking for regressions in such files, or at least include those in the reference data and reports.
The text was updated successfully, but these errors were encountered:
So the idea would be to add an option to the yaml to let the users decide to check for that?
I guess we can also make it a bit more abstract and just let the user specify a set list of files that should be the same in terms of binary or textual representation?
I like the suggestion for the more general solution (specify some files to check, either binary or numerical representation). Since we would need to define metrics for the CSV files (rather complicated), let's just check the hashes.
In simulations with implicit coupling, the second participant writes a CSV file logging the number of iterations in every coupling time window: https://precice.org/running-output-files.html
We should be checking for regressions in such files, or at least include those in the reference data and reports.
The text was updated successfully, but these errors were encountered: