From 87c0e881d23570c919691b5704ee1e52ddba81c7 Mon Sep 17 00:00:00 2001 From: Katherine Mantel Date: Fri, 8 Nov 2024 06:28:21 +0000 Subject: [PATCH] Scheduler: fix false add_condition replace warning Do not set _user_specified_conds in __init__, because it will be set by add_condition_set in graph_scheduler.Scheduler.__init__. This second call would result in the condition replacement warning for any conditions passed in. --- psyneulink/core/scheduling/scheduler.py | 2 -- 1 file changed, 2 deletions(-) diff --git a/psyneulink/core/scheduling/scheduler.py b/psyneulink/core/scheduling/scheduler.py index 5413d257668..de1a59c4c0f 100644 --- a/psyneulink/core/scheduling/scheduler.py +++ b/psyneulink/core/scheduling/scheduler.py @@ -56,8 +56,6 @@ def __init__( # TODO: consider integrating something like this into graph-scheduler? self._user_specified_conds = graph_scheduler.ConditionSet() - if conditions is not None: - self._user_specified_conds.add_condition_set(copy.copy(conditions)) self._user_specified_termination_conds = copy.copy(termination_conds) if termination_conds is not None else {} super().__init__(