[Rivet] YODA excptions

[Chris Pollard]

Hi David,

Just to be sure I understand you: YODA should always raise these
exceptions; it's a question of whether Rivet catches them gracefully,
correct?

I am not sure all users want Rivet to continue running when at least one
analysis crashes, but I can see why some might. Maybe a --continue-run flag
or similar is more appropriate for those that don't want to stop the run
when there is at least one analysis "still standing"?

Chris

On Tue, Jan 19, 2016 at 10:35 AM, David Grellscheid <
david.grellscheid at durham.ac.uk> wrote:

> Hi all,
>
> can we discuss the new YODA stance of always raising exceptions?
>
> Within the lowest level of YODA, I have no problem with that, it's the
> right thing to do. The question is at what level you need to swallow these.
> One rogue point in one dodgy Rivet analysis can kill a whole run right now.
>
> I think that
>
> 1) no YODA exceptions should be able to propagate outside of Rivet. Rivet
> needs to deal with them and "do the right thing" whatever that may be.
>
> 2) Rivet needs to isolate crashing analyses and allows the remaining run
> to proceed
>
> Any comments?
>
>   David
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> https://www.hepforge.org/lists/listinfo/rivet
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20160119/96971ccc/attachment.html>