use centroids for geo prior inference #40
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
note there are required changes to config.yml, check out config.yml.example
the current path, with centroids, requires no changes other than to mention in the config file that
use_coord_encoder= false. I did this because I didn't want to assume you'd be ok with switching the whole coord encoding scheme to this coord encoder class, Patrick. if you're ok with it, I can migrate the existing centroid based geo prior inference and geo encoding scheme to use the CoordEncoder class throughout the repo, but that seems like more work than I wanted to take on without at least talking with you first. basically, I was trying to add the possibility of the new coordinate encoding scheme in a way that would be flexible going forward (supporting hd encodings, other env covariates, etc) while making as little impact to the existing implementation as possible. however you think I should proceed, happy to follow your direction.