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

Raw Estimates Errorbars for TPInstrument #460

Open
pcwysoc opened this issue Jul 10, 2024 · 1 comment
Open

Raw Estimates Errorbars for TPInstrument #460

pcwysoc opened this issue Jul 10, 2024 · 1 comment
Assignees
@sserita @pcwysoc
Labels
discussion Request for further conversation to figure out action steps low priority Developers should be aware of this issue, but it need not be addressed imminently
Milestone
0.9.13

Comments

@pcwysoc
Copy link

pcwysoc commented Jul 10, 2024 •
edited
Loading

Error bars for raw estimates using a TPInstrument are asymmetric. While unsatisfying, this makes sense due to the asymmetry in TPInstrument. However, we should continue tracking this. Hopefully, it will be resolved by removing the TPInstrument class and replacing it with the ComposedInstrument class.
@pcwysoc pcwysoc mentioned this issue Jul 10, 2024
Open
16 tasks
@pcwysoc pcwysoc changed the title First instrument element errorbars calculate incorrectly in report generation for Raw Estimates @coreyostrove @pcwysoc - Not an issue, but should be revisited (the TP instrument parameterization means that the confidence intervals will be asymmetric) Raw Estimates Errorbars for TPInstrument Jul 10, 2024
@pcwysoc pcwysoc added discussion Request for further conversation to figure out action steps low priority Developers should be aware of this issue, but it need not be addressed imminently labels Jul 10, 2024
@pcwysoc pcwysoc added this to the 0.9.13 milestone Jul 10, 2024
@pcwysoc
Copy link
Author

pcwysoc commented Jul 10, 2024

@sserita Feel free to elaborate. I can't remember exactly what you told me a couple weeks ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sserita sserita

@pcwysoc pcwysoc

Labels
discussion Request for further conversation to figure out action steps low priority Developers should be aware of this issue, but it need not be addressed imminently
Projects
None yet
Milestone
0.9.13
Development

No branches or pull requests
2 participants
@sserita @pcwysoc