Jason Rigby

@jsciame I also had this issue. I think I've found a solution, which I've raised as PR #280. If you get a chance, could you take a look at the...

Hi @SinhUIT thanks for your question. I haven't included the training code I used in the repo just because the training setup can depend a lot on your system configuration...

@poorlymac you had a question earlier in issue #5 that I didn't get around to replying properly (sorry!). Perhaps you could take a look at my reply above in this...

@hblandford there are two things to consider here: 1. There will always be some inputs that are not correctly parsed simply because this is a probabilistic model and doesn't follow...

@diogorjs from a theoretical perspective, there is no reason why this model would not work (or course it will need retraining). The purpose of this model is simple to assign...

@Aretle first of all, please accept my apologies for not noticing this (badly needed) PR. I have been swamped with notifications from my day job and this never caught my...

My personal feeling is that we can increment the major version number and not try to maintain backward compatibility. TF 1.x is old and ensuring backwards compatibility, especially when there...

As with issue #5 I think this will come down to tuning the address generation code used during training. The reason your approach of adding L to lookups.py didn't work...

Your English is completely fine, don't worry! This model is trained only on Australian address data, so it will not work at all for Vietnamese addresses, and probably it will...

Oh dear, you are right. The TF version range in setup.py is bad! At the time of development, it would have been 1.12 because I always set the version to...