DPCS-team / DPCS

Data Powered Crash Solver
7 stars 17 forks source link

Research/ticket 52/Cleaning the database #19

Closed inexxt closed 8 years ago

inexxt commented 8 years ago

There is a problem of having outdated solutions in the database. How do we prevent that? In other words: we get the information about packages versions installed on client's machine - how do we check, if the solution is still applicable? If it haven't worked, how do we save that info? Deleting solutions doesn't seem like the optimal path, since there will still be users using old software, but maybe it will be the thing that has to be done, because there's no easy way to differentiate between cases in our algorithm, or simply our resources won't be able to handle that much of a historical data. Think of the possible paths we can possibly choose in the future - memory-expensive system lifelong logs, computationally-expensive deep learning algorithms, set of heuristics, NLP algorithms (shared knowledge) etc. write about 0.5 pages summing up your ideas and present it during the meeting.

inexxt commented 8 years ago

No longer needed (as we talked during the meeting).