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.

Sign up for GitHub

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

Jump to bottom

Expected at least one HPO term per patient, but received none for patient Reuter2020 #56

Closed
pnrobinson opened this issue Sep 22, 2023 · 1 comment · Fixed by #128
Closed

Expected at least one HPO term per patient, but received none for patient Reuter2020 #56

pnrobinson opened this issue Sep 22, 2023 · 1 comment · Fixed by #128
Assignees
@lnrekerle
Labels
bug Something isn't working
Milestone
Manuscript

Comments

@pnrobinson
Copy link
Member

Instead of this error message:

Expected at least one HPO term per patient, but received none for patient VanDongen2019_P2
Expected at least one HPO term per patient, but received none for patient VanDongen2019_P12
Expected at least one HPO term per patient, but received none for patient Reuter2020

It would be better to state:

23 phenopackets removed from analysis because no HPO terms were found: VanDongen2019_P2, VanDongen2019_P12, Reuter2020...
@ielis ielis added the bug Something isn't working label Oct 16, 2023
@ielis ielis added this to the Manuscript milestone Nov 16, 2023
@ielis
Copy link
Member

ielis commented Dec 19, 2023

Related to #120

@lnrekerle lnrekerle self-assigned this Dec 19, 2023
This was referenced Jan 9, 2024
Closed
Merged
@ielis ielis linked a pull request Jan 16, 2024 that will close this issue
Formalize handling and reporting of input errors #128
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lnrekerle lnrekerle

Labels
bug Something isn't working
Projects
None yet
Milestone
Manuscript
3 participants
@pnrobinson @ielis @lnrekerle