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

Expand summary data in RM Weighted Mean visualisation #367

Open
sbodorkos opened this issue Oct 23, 2019 · 1 comment
Open

Expand summary data in RM Weighted Mean visualisation #367

sbodorkos opened this issue Oct 23, 2019 · 1 comment
Assignees

Comments

@sbodorkos
Copy link

I thought I'd start a bit of a list of enhancements to our RM visualisations, as we haven't done anything with there for a while, and some additional info would help make life easier for 1.3.0 users. Some of the decision we need to make about Unknowns depend on parameters calculated on the set of RM analyses, and visibility of the relevant summary data is currently poor (unless you know exactly where to look in Manage Expressions).

I think the set of numeric Reference Ages for the RM would be a useful addition (even though the primary/relevant daughter-parent age is marked on the Wtd Mean plot). The 207Pb/206Pb age can be different to the daughter-parent age, and it would be nice to be able to see it all on one screen.

RM summary results: We really need to be able to see the results of R-flagged BiWt summary results, ideally in the same area of the screen as currently shows the Wtd Mean summary. At a minimum, we would need:

  • BiWt_204OvCts_From207Pb[0] and [2]
  • BiWt_204OvCts_From207Pb[0] and [2]
  • BiWt_4cor_207Pb206Pb_Age[0] and [2]

I am less worried about analogous data for the ...PrimaryCalibConstDelta... parameters, but perhaps we should ultimately leave space for those as well.

The above BiWt parameters, in conjunction with the RefRad ages for the RM, are the data we would want to assess when making a decision on the appropriate 204CountCorrection setting for the Unknowns.

I also think we need to start using tabs in places where visualisations are "naturally" separated, in places where we are currently using radio-buttons inappropriately, or (in Unknowns) where the tree-structure is overloaded (and because we are also eventually going to need space to show summary results for Unknowns too). More on that later.

@bowring
Copy link
Member

bowring commented Jun 20, 2020

@sbodorkos - time to revisit this as well in one of our calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants