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

Permit processing of 3D data when no EnvironmentLogger data is available #6

Open
jeffreydemieville opened this issue Jul 31, 2023 · 0 comments

Comments

@jeffreydemieville
Copy link
Member

Problem: outages of EnvironmentLogger result in no data being saved on the datastore for dates where 3D data was collected. Transformation of this data would still be necessary, but a predictive model based on EnvironmentLogger parameters could not be reliably used.

Course of action: for datasets that lack EnvironmentLogger data, allow the operator to ignore its absence and transform each measurement independently. This would be labor-intensive but would allow transformation of datasets that are not appropriate for the predictive model. The output transformation would need some flag indicating that it lacks EnvironmentLogger data, or would need to be handled manually through the next step of the pipelines.

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

No branches or pull requests

1 participant