Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Limit Surface Integral Bounding Error #1216

Closed
10 tasks done
alfoa opened this issue Apr 16, 2020 · 1 comment · Fixed by #1217
Closed
10 tasks done

[TASK] Limit Surface Integral Bounding Error #1216

alfoa opened this issue Apr 16, 2020 · 1 comment · Fixed by #1217
Assignees
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment

Comments

@alfoa
Copy link
Collaborator

alfoa commented Apr 16, 2020


Issue Description

Is your feature request related to a problem? Please describe.

The Limit Surface integral should allow (optionally) to request for the estimation of the bounding error (maximum error in Probability)

Describe the solution you'd like
N/A

Describe alternatives you've considered
N/A


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@alfoa alfoa added priority_minor task This tag should be used for any new capability, improvement or enanchment labels Apr 16, 2020
@alfoa alfoa self-assigned this Apr 16, 2020
alfoa added a commit that referenced this issue Apr 16, 2020
@wangcj05
Copy link
Collaborator

Checklist is satisfied, and issue can be closed.

wangcj05 pushed a commit that referenced this issue Apr 23, 2020
* limit surface error bound

* Closes #1216

* added new requirement

* considering the number of points, the error bound can be at maximum accurate to 1e-3

* fixed perturbation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants