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

Outputs which are all NaN/null should not be part of database #704

Open
matthiaskoenig opened this issue Feb 1, 2021 · 0 comments
Open

Outputs which are all NaN/null should not be part of database #704

matthiaskoenig opened this issue Feb 1, 2021 · 0 comments
Assignees
@janekg89
Labels
backend backend issues

Comments

@matthiaskoenig
Copy link
Owner

Often all values Nan in output_type output. Such data should not be uploaded in data base.
E.g. omeprazole/Cederberg1992 clearance
image

NaN in array and timecourse are allowed.
@matthiaskoenig matthiaskoenig added the backend backend issues label Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@janekg89 janekg89

Labels
backend backend issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matthiaskoenig @janekg89