You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many users have expressed surprise when they discover that CohortDiagnostics computes characterization for time windows that were not explicitly specified. This issue arises because certain time windows are required, as indicated in the code section: RunDiagnostics.R#L409-L419.
Originally (and continues to be), CohortDiagnostics was intended for phenotype development and evaluation, and the FeatureExtraction covariate settings were not exposed. Over time, likely due to demand for using CohortDiagnostics as a characterization tool, these settings were made public. However, a design decision to enforce certain time windows was implemented. As a result, users are often surprised by seeing outputs for time windows they did not specify.
It would be beneficial to either improve the documentation to clearly state this behavior or reconsider the design to allow more flexibility in specifying time windows.
The text was updated successfully, but these errors were encountered:
Many users have expressed surprise when they discover that CohortDiagnostics computes characterization for time windows that were not explicitly specified. This issue arises because certain time windows are required, as indicated in the code section: RunDiagnostics.R#L409-L419.
CohortDiagnostics/R/RunDiagnostics.R
Lines 409 to 419 in 03c40ab
For example, even when the default covariate settings are modified, these required time windows are still computed:
Originally (and continues to be), CohortDiagnostics was intended for phenotype development and evaluation, and the FeatureExtraction covariate settings were not exposed. Over time, likely due to demand for using CohortDiagnostics as a characterization tool, these settings were made public. However, a design decision to enforce certain time windows was implemented. As a result, users are often surprised by seeing outputs for time windows they did not specify.
It would be beneficial to either improve the documentation to clearly state this behavior or reconsider the design to allow more flexibility in specifying time windows.
The text was updated successfully, but these errors were encountered: