-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fix readjustment of number of slices bug in RSA #679
Conversation
Does the switch to YAXArray break the ability to plot results? |
There are also changes to |
ext/AvizExt/viz/viz.jl
Outdated
@@ -1,7 +1,7 @@ | |||
using Makie, DataFrames | |||
|
|||
using ADRIA: ResultSet, metrics.metric_label, analysis.col_normalize, model_spec | |||
using NamedDims, AxisKeys | |||
using NamedDims, AxisKeys, YAXArrays, DimensionalData |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the import of DimensionalData simply to have the At
method?
If so, I'd prefer it be imported via YAXArrays:
import YAXArrays.DD: At
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I just took this from the YAXArray docs and forgot to remove, I've removed it now
src/analysis/sensitivity.jl
Outdated
YAXArrays, | ||
DimensionalData |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As with previous comment - if this is for At
, import it directly.
Thanks Rose, clearly I'm going blind. |
ext/AvizExt/viz/sensitivity.jl
Outdated
@@ -175,7 +175,7 @@ Makie figure | |||
function ADRIA.viz.rsa!( | |||
g::Union{GridLayout,GridPosition}, | |||
rs::ResultSet, | |||
si::NamedDimsArray, | |||
si::YAXArrays.Dataset, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not import Dataset
directly so prefacing it with YAXArrays
is not necessary?
Or is there a different Dataset
type that is causing a conflict?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've replaced with Dataset
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor comments for consideration
… storage size, but then S i readjusted according to the factor type
…or factors which are not categorical
Add `factors` as input to specify which factors to output
Not max between number of categories and default S
… otherwise set as default
…rwise use defauilt
Each entry has bins as first column, sensitivities as second
Also remove original Dict() storage for sensitivities
Values to be stored in YAXArrays with shared dimensions where relevant (variables other than unordered categorical type) Keys of NamedTuple are variable names
2ff9c61
to
3324de3
Compare
…taset` references with `Dataset`
I think I've addressed your comments, If you're happy with this I'll do another PR with similar changes for |
Busy with something else at the moment, would you mind attaching a figure here to demonstrate its working please? |
The peak is telling you that there is high variability in that factor space. In other words, the outcome assessed is highly sensitive to that region of factor space, which corresponds with no intervention. |
Makes sense |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes readjustment of number of slices bug in RSA (partially addresses #615) and changes output of RSA to
YAXArrays.Dataset
type.