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
Definitely agree on this one, especially for very time critical/emergency systems. I've had to do similar manually from the task level before - polling for 'done' files after a certain time so that the suite could finish up once a reasonable number of ensemble members were done.
Upvote this! I ran into a use case where we only wanted to send a critical message when more than X members of an ensemble failed. For now, have scrapped together a workaround whereby each failed member gets the status of the family to check whether the threshold has been reached, and if so, outputs a critical message. Then, the if any of the family members outputs the message, a task is triggered to send an email. It'd be so much nicer to have this construct. Perhaps notation could be something like FAMILY:fail-more-than(X); FAMILY:succeed-more-than(Y)?
In addition to
FAMILY:fail-all
andFAMILY:fail-any
(and same forsucceed
,start
, etc.) we should have triggers like "FAMILY:fail-50%-or-more'#2333 (comment)
We'll need to think hard about a clear and flexible notation here.
The text was updated successfully, but these errors were encountered: