-
Notifications
You must be signed in to change notification settings - Fork 8
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
Bug related to integers/floats and/or cohort input parameter #280
Comments
@karafecho I believe this issue was triggered by changes to address the issue #247 as well which changed the response from cohort endpoint to return number of patients rather than number of observations as previously implemented. So the counts returned here are for number of observations for selected cohort rather than aggregating across years. Should we make it clear the returned count are for number of observations? The confusion here is that the cohort returns number of patients while these features and features associations endpoints return number of observations for the select cohort, which was discussed a bit in that issue #247. It seems to me these endpoints are all returning correct results and we just need to update documentation to make the returned results clearer to the users. What do you think? |
@hyi : Thanks for the investigative work. I think your conclusion is correct; however, I did some systematic testing at both the asthma and pcd prod endpoints, just to take a closer look, as the patient vs observation issue is a bit confusing. Plus, I wanted to consider how this might affect the multivariate functionality. I've attached two files with tabular example results. (Note that I didn't save all the CURLs.) I noticed a few things:
Asthma
422 Error, not a valid feature - study_period must not be defined in YAML PCD
COHORT:1 (all)
Returns terms/conditions, zero results - tested several variations - study_period not valid feature at multivariate endpoints? All in all, I think you are correct that all endpoints are behaving properly and by design. However, we probably need to:
Does the above seem correct? |
One additional comment/task: we do need to update the documentation. I can do this, but please advise on your preferred approach for doing so. Thanks! |
@hyi : Brenna continues to report issues with the multivariate endpoint, so I did a bit of systematic testing. Perhaps we can discuss?
|
BTW, and this may be important information, all of the cohorts were preserved, despite the fact that you recreated the database. Perhaps something went wrong with that? |
@karafecho database is only recreated for PCD instances due to changes to all features yaml file. For other instances, only valuesets yaml file is updated with correct min and max ranges for year, so there are no database changes. |
Closing issue, as this issue was resolved ... |
Brenna (intern) is exploring the multivariate technique. She has successfully used the lesson plan that I created to independently run all available ICEES+ functionalities and generate a multivariate table. However, she uncovered a bug that I reproduced and explored a bit. The issue appears to be related to the change we made in the treatment of integers vs floats and/or a failure to recognize the cohort input parameter at certain endpoints. Here's an example:
+-------------+--------+
| cohort_id | size |
+=============+========+
| COHORT:26 | 15901 |
Excerpt:
Excerpt:
The text was updated successfully, but these errors were encountered: