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] uniform discrete distribution #1249

Closed
10 tasks done
mandd opened this issue Jun 8, 2020 · 1 comment · Fixed by #1250
Closed
10 tasks done

[TASK] uniform discrete distribution #1249

mandd opened this issue Jun 8, 2020 · 1 comment · Fixed by #1250
Assignees
Labels
priority_critical task This tag should be used for any new capability, improvement or enanchment

Comments

@mandd
Copy link
Collaborator

mandd commented Jun 8, 2020


Issue Description

Is your feature request related to a problem? Please describe.
A uniform discrete distribution is needed.
This new distribution requires two different types of sampling, with or without replacement.

Describe the solution you'd like
Create additional distribution class based on the categorical distribution

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.


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?
@mandd mandd added priority_minor task This tag should be used for any new capability, improvement or enanchment labels Jun 8, 2020
@alfoa
Copy link
Collaborator

alfoa commented Jun 11, 2020

Closure checklist passed... and Closure approve via #1250

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_critical 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