-
Notifications
You must be signed in to change notification settings - Fork 11
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
Date of trained MT engine #28
Comments
I'll mark this as an enhancement for a future version. |
Thanks Tommi It actually happens quite often as you once told me not to add new or updated TMs to the trained MT engine but to "start over" again, so I'm continually updating my trained MT engines already |
Hello Tommi
I'm sure you will get round to looking at recent posts
I've noticed that when I train an MT engine with a specific TM for a specific client, the date of the trained MT engine is the date of the original untrained MT engine on which is was based
i.e. My French untrained MT engine has the date 2020-02-26
If I use this MT engine to produce a new trained MT engine for a client, say "Company1", the date of this new MT engine is still 2020-02-26
The confusion then starts as after each job, I have to remember, when I have a spare moment, to delete the old MT engine for the client and to produce a new one with my updated TM
but if I use the same naming convention, I get Company1 2020-02-26 again so to speak
And after a few weeks, I can never remember which MT engines are up to date and which need to be deleted and a new one produced
Any chance of giving them an up-to-date date automatically?
Thanks
The text was updated successfully, but these errors were encountered: