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
- clarify naming convenction, for `member_num` use either `member_id`,
`member_ids`, or `member_count`
- revise the member selection algorithm, instead of checking random it
uses this deterministic approach
At each step, every ensemble member is evaluated to determine how many
of the remaining members satisfy the given tolerances when compared to
it. The ensemble member that results in the highest number of other
members passing the tolerances is selected. This process is repeated
until either all members are successfully validated using the current
tolerances, or a maximum number of attempts is reached. In the latter
case, the tolerance factor is increased, and the process continues.
---------
Co-authored-by: Annika Lauber <annika.lauber@c2sm.ethz.ch>
-`stats_ref.csv`: contains the post-processed output from the unperturbed reference run
194
-
-`stats_{member_num}.csv`: contain the post-processed output from the perturbed reference runs (only needed temporarily to generate the tolerance file)
194
+
-`stats_{member_id}.csv`: contain the post-processed output from the perturbed reference runs (only needed temporarily to generate the tolerance file)
195
195
-`exp_name_tolerance.csv`: contains tolerance ranges computed from the stats-files
196
196
197
197
These can then be used to compare against the output of a test binary (usually a
0 commit comments