search

cfedermann / mt-serverland

Open Server Architecture for Machine Translation
http://www.dfki.de/~cfedermann
11 stars 6 forks source link

Failed translations should be tagged as such #7

Closed sabinehunsicker closed 11 years ago

sabinehunsicker commented 14 years ago

Failed translations, i.e. when the worker does not return a target text or an empty one, should be tagged as such (red/bold font,...). In those case it would also be useful to get any error messages the worker or broker server might return (worker offline/busy, invalid source text/characters,...).

cfedermann commented 14 years ago

Current "tag" is the empty results page, we're still in beta stage ;)

Different colors for different status codes seem to be a good idea, finding out and returning the actual "cause" of an error will be more tricky. We could maybe start by also returning a STDOUT logfile?

cfedermann commented 11 years ago

Create additional 123456.STDOUT|STDERR files inside messages folder?

~Or extend protobuf messages to include such data?~ We could use repeated KeyValuePair packet_data = 6; which allows to add key-value information to TranslationRequestMessage objects.

cfedermann commented 11 years ago

Commit 01975e4 adds support for STDOUT, STDERR export to message files for Moses and Accurat workers.

Both are available from packet_data, using keys STDOUT and STDERR.

This closes the issue.