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

Review Csv-Driver products #235

Open
3 of 6 tasks
SpencerFleming opened this issue Jul 18, 2019 · 1 comment
Open
3 of 6 tasks

Review Csv-Driver products #235

SpencerFleming opened this issue Jul 18, 2019 · 1 comment
Labels
Task Marks issue as a SCRUM task

Comments

@SpencerFleming
Copy link
Contributor

SpencerFleming commented Jul 18, 2019

Before I say this epic is complete I want to make sure there are no glaring mistakes, and I also need to put some time into bug testing and stress testing the code.

Quality Control goals:

  • No unused lines of code
  • Formatting is satisfactory
  • Notes have been taken on where refactoring of this along with LidarDriver may be useful
  • All functions and classes that aren't unit testable are exhaustively listed somewhere
  • CSVs are proven to be accurate (I may look into how GSuite may be able to help with this)
  • Program runs at least as fast as geotiff-driver, and uses at most the same amount of memory.
@SpencerFleming SpencerFleming self-assigned this Jul 18, 2019
@SpencerFleming SpencerFleming added the Task Marks issue as a SCRUM task label Jul 18, 2019
@SpencerFleming
Copy link
Contributor Author

Functions in LidarDriver aren't unit tested. One of them just calls a function that is, and the other is a variant of fit_data that I'm still working on.

@SpencerFleming SpencerFleming removed their assignment Dec 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Marks issue as a SCRUM task
Projects
None yet
Development

No branches or pull requests

1 participant