Open slacmshankar opened 5 years ago
Is it possible that this has been fixed?
Yes; I do believe this is fixed. I'd left this open to add some documentation. Will do so...
Regards, Murali
From: Andraz Pozar notifications@github.com Sent: Monday, December 30, 2019 7:07 PM To: slacmshankar/epicsarchiverap epicsarchiverap@noreply.github.com Cc: Shankar, Murali mshankar@slac.stanford.edu; Assign assign@noreply.github.com Subject: Re: [slacmshankar/epicsarchiverap] Maximize status (in addition to severity) for postprocessors (#74)
Is it possible that this has been fixed?
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://github.com/slacmshankar/epicsarchiverap/issues/74?email_source=notifications&email_token=AATZLMUN6I7IULYFLIGYJL3Q3KZPZA5CNFSM4GQAEC3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH3UTOY#issuecomment-569854395, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AATZLMVFKICTESMCYRVBRNTQ3KZPZANCNFSM4GQAEC3A.
Currently, the postprocessors implement a "maximize severity" across the samples in the bin. Per Andraz, it would be beneficial to apply the same to status as well. That is, we also maximize the status across the samples in the bin and set the status of the computed sample to the max(status) of all the samples in the bin.