search

GeomancerProject / geomancer-api

Geomancer API
6 stars 0 forks source link

Save failed Predict cache entries for later training #24

Open eightysteele opened 11 years ago

eightysteele commented 11 years ago

Title says it all.

tucotuco commented 11 years ago

I still like this idea. Here's what I propose to cache, Locality for Localities that do not produce georefs. Clauses for Clauses that do not produce georefs.

@eightysteele Additionally, is it feasible to change a cached prediction result if we discover in processing that it is incorrect?

Example: locality="South San Francisco"

prediction will return 'fs' for that, and that is not an unreasonable prediction. But it isn't correct. For the whole class of named places that begin with a heading (South Haven, North Shore, West Berlin, etc.), we need to check first on locs predicted as 'fs' to see if it works as an 'f'. If it does, we should change the prediction in the cache to avoid the overhead in the future. The processing 'fs' processing part of this issue is already logged in issue #58.