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.

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

EBAS reading: add tests for correct values for the most used EBAS variables #605

Closed
jgriesfeller opened this issue Mar 24, 2022 · 8 comments
Assignees
Labels

Comments

@jgriesfeller
Copy link
Member

The current EBAS reading tests do not test actual variable values.
I think we should also make sure that the read values of the most used variables make sense.
Variables:

  • concso4
  • concso2
  • concpm10
  • concpm25
  • conco3
  • concoa
  • concss
  • concoc
@lewisblake
Copy link
Member

Some guidance for criteria for "makes sense" would be appreciated here. In my initial testing, I've found concpm10 concentrations with negative values (all -0.1), but can't seem to find an obvious way to determine if these are fill values or suspect data.

lewisblake added a commit that referenced this issue Jul 19, 2022
@lewisblake
Copy link
Member

It is also worth noting that the ReasEbas filter itself does not check for negative values in the data.

@avaldebe
Copy link
Collaborator

@jgriesfeller

It is also worth noting that the ReasEbas filter itself does not check for negative values in the data.

Do you k now if this is a bug or a feature?

@lewisblake
Copy link
Member

I think it's a feature. It's listed:

TODO
----
- Check for negative values vs. detection limit
- ...

I looked to see if this was just outdated and had been implemented but this TODO not removed, but I did not see anything which appears like it has been implemented. I think we should implement removing of negative values before testing for it :)

@avaldebe
Copy link
Collaborator

Is there an specific issue for the negative values?
If not, maybe you could open one and address it on your test coverage PR?

@lewisblake
Copy link
Member

I do not see an issue, so I will open one and address it.

Copy link

This issue is stale because it has been open for 365 days with no activity. This issue will be closed in 14 days if no action is taken.

@github-actions github-actions bot added the stale label Jan 14, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants