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
When executing a batch run across two cases that draw from the same measure set but use different (but overlapping) subsets of the larger set, the batch runs of ecm_prep.py will develop a shared set of prepared measure data for run.py to draw from in each case, and will avoid preparing the same measure twice across cases that share it, as intended.
However, then each case's execution of run.py pulls in the full set of prepared measures, rather than the appropriate subset of measures that the case applies to.
The text was updated successfully, but these errors were encountered:
jtlangevin
changed the title
Batch runs appear to conflate scenarios that have the same prep settings but apply to different measure subsets
Batch runs appear to merge together measure data in scenarios that have the same prep settings but apply to different measure subsets
Jan 17, 2025
jtlangevin
changed the title
Batch runs appear to merge together measure data in scenarios that have the same prep settings but apply to different measure subsets
Batch runs appear to mix together active measures in scenarios that have the same prep settings but apply to different measure subsets
Jan 17, 2025
When executing a batch run across two cases that draw from the same measure set but use different (but overlapping) subsets of the larger set, the batch runs of
ecm_prep.py
will develop a shared set of prepared measure data forrun.py
to draw from in each case, and will avoid preparing the same measure twice across cases that share it, as intended.However, then each case's execution of
run.py
pulls in the full set of prepared measures, rather than the appropriate subset of measures that the case applies to.The text was updated successfully, but these errors were encountered: