-
Notifications
You must be signed in to change notification settings - Fork 303
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
Left truncation adjustment for KM plot #4324
Conversation
@dippindots really nice work! For study view:
Results/Comparison View View:
|
@dippindots Excellent work! This is amazing. My only comment is that we should probably adjust this warning: "Kaplan-Meier estimates do not account for the lead time bias introduced by the inclusion criteria for the GENIE BPC Project." as we can adjust for some curves at this point. Some of these warnings also come from the data files themselves, so we need to figure out a way to correctly display these warnings. In the space where the left truncation adjustment is described, it would be convenient/ consistent to have a warning that the curve is not corrected. In both the smaller plots on the summary page and in the comparison view. Alternatively, we could change the warning to something more general such as: "Not all Kaplan-Meier estimates account for the lead time bias introduced by the inclusion criteria for the GENIE BPC Project." |
@dippindots for this tooltip: It might be good to:
In the left truncation tooltip: On the comparison page:
Does that make sense? Thanks! |
4b660e5
to
d4659fb
Compare
readonly survivalPlotData = remoteData<SurvivalType[]>({ | ||
await: () => [ | ||
this.survivalData, | ||
this.selectedPatientKeys, | ||
this.survivalPlots, | ||
this.survivalEntryMonths, | ||
], | ||
invoke: async () => { | ||
return this.survivalPlots.result.map(obj => { |
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 can see that this isn't new but it's a little wrong that we are mutating survivalPlots here, tacking on the survival data. it's suprising to me that typescript allows this. in other words, that the survivalPlot object will accept survivalDataWithoutLeftTruncation as a property. better to just make consumers look it up using plot id?
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 fixed it by not changing the property in place, is this looks good? 313fbab
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 don't think this is great either. it doesn't really make sense to collapse these two types in this way. maybe just key the survivalPlotData by id and then look it up when we need it?
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.
changed to a search by id approach in commit : dbdd28d
Please using links:
to test this feature.
What is in this pr: