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.

Sign up for GitHub

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

Jump to bottom

Improve the evaluate()-method #13

Open
3 tasks
1313e opened this issue Mar 7, 2019 · 0 comments
Open
3 tasks

Improve the evaluate()-method #13

1313e opened this issue Mar 7, 2019 · 0 comments
Assignees
@1313e
Labels
maintenance Optimization/improvement/extension

Comments

@1313e
Copy link
Owner

1313e commented Mar 7, 2019

Rewrite/improve the evaluate()-method to make it very clear what part of the results belongs to what data_idx, as they are currently returned in the order PRISM handles them (which has no logic for the user at all).

  • Split results up into the individual emulator iterations at which the sample was last evaluated;
  • Every result must show to which data point (data_idx) it belongs to;
  • Allow for a subset of data_idx to be given?
@1313e 1313e added maintenance Optimization/improvement/extension todo This will be worked on in the future labels Mar 7, 2019
@1313e 1313e added this to the v1.1.2 milestone Mar 7, 2019
@1313e 1313e self-assigned this Mar 7, 2019
@1313e 1313e modified the milestones: v1.1.2, v1.1.3 Jun 12, 2019
@1313e 1313e removed this from the v1.1.3 milestone Jun 19, 2019
@1313e 1313e removed the todo This will be worked on in the future label Oct 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@1313e 1313e

Labels
maintenance Optimization/improvement/extension
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@1313e