#85 closed defect (worksforme)
more user-friendly MD5 mismatch handling
Reported by: | Juergen Reuter | Owned by: | kilian |
---|---|---|---|
Priority: | P2 | Milestone: | |
Component: | core | Version: | 2.0.0alpha |
Severity: | major | Keywords: | MD5 checksum handling |
Cc: |
Description (last modified by )
when MD5 checksums do not agree but the user nevertheless runs the process
the cross sections comes out to be zero (numerically, i.e. 10-16 fb. If such a thing happens there should not only be a warning, but the WHIZARD should stop evaluating.
Change History (3)
comment:1 Changed 15 years ago by
Description: | modified (diff) |
---|---|
Milestone: | v2.0-beta → v2.0-final |
comment:2 Changed 15 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
as I cannot reproduce this right now, I close the ticket for now. We might reopen it later.
Note: See
TracTickets for help on using
tickets.
Hm. Right now I cannot reproduce this case! Since this is a typical test case for the beta testing phase I move this ticket to the final release milestone.