-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Alignments + weak quality scores capability in Service (#46)
* Draft adjustments to API * Adjustments to docs * Let's call the word + sentence ranges annotations * Editing confusing comment on size() * Fixing compilation for template adjustments for SentenceRanges * string_view template hacks This commit shifts AnnotatedBlob into a templated type and gets the troubled part to compile. All to manage absl::string_view and std::string_view. Objective: marian::bergamot stays C++ 11 to pluck and put in marian code, bergamot-translator somehow flexes C++17. Simplify development in one place. * Fixing the wiring: Gets source to build Runtime errors exist, but AnnotatedBlobs are consistent. * Bugfix: Matching old-state after factoring AnnotatedBlob in * Removing vocabs_ from Response. (For the umpteenth time). * Alignment API ready in marian::bergamot::Response * Wiring alignments upto TranslationResult * Adjustment to get alignments; bergamot-translator-app has alignments available * Accessing words instead of Ids This code sets up access of word string_views from annotations instead of printing Ids. However, we have segfault. This is likely due to targetRanges not being set, pending from #25. Could also be a rogue EOS token which we're filtering for in string_view annotations, but not so in alignments. * Switching to browsermt/marian-dev@jp/decode-string-view for targetTokenRanges * Target word byte range annotations available Issues corresponding to #25 should be resolved. There is still a segfault. Could be due to EOS. Pending investigation. * Bugfix: Tokens for alignments are now through. Was not EOS. * browsermt/marian-dev@master ByteRange changes work downstream and has been merged to master. Updating submodule to point to master. * Style and documentation enhancements: response.cpp * Style and documentation enhancements: TranslationResult.h * Descriptions for SentenceRanges templating * Switching to marian-dev@wasm-sync * AnnotatedBlob can be copy-ctord/copy-assigned * TranslationResult: Empty ctor + WASM Bindings Allows empty construction of TranslationResult. Using this empty constructor, WASM bindings are adjusted. Unsure of the results, maybe @abhi-agg can test. * Cosmetic: SentenceRangesT -> Annotation - SentenceRangesT is renamed to AnnotationT; - Further comments to explain heavily templated files. * Response: Cleaning up unused members and adding docs * Adding quality scores - attempt * Stub QualityScores This adjustment adds capability to get "scores", which should potentially indicate how confident (at least relative in a target-sentence) should be. This enables writing the code forward for TranslationResult, and an example quality-score people can be pointed at. - These are not between [0,1] yet. - In addition, guards to check out-of-bounds access have been placed so illegal accesses are caught early on during development. * Removing token debug statements * Reworking Annotation without templates mozilla#8 provides ByteRanges. - This ByteRange data-type is used in Annotation and converted to marian::string_view(=absl::string-view) on demand. - Since Annotation[using ByteRange] is not bound to anything else, it can be unit tested. A unit test is added (originally to test independently for integration after). - Annotation with ByteRange is now propogated across marian::bergamot and functionality matched to how it was previously working. This eliminates the string-view conversion and template code. * Nit: Removing std::endl flushes * Bring TranslationResult and Response closer Helps #53. In preparation , the data-export types for Quality and Alignment are pushed down to Response from TranslationResult and computed during construction. This brings TranslationResult closer to Response, paving way to avoid having two TranslationResults. histories_ only remain for marian-decoder replacement usage, which can be removed in a separate PR. * Clean up hacks originally added for a unit-test to compile * Moving Annotation functions to cpp and documenting header file * Shifting alignments, qualityScore testing capability into main-mts * Restore Unified API files to previous state * Adaptations to fix Response with Quality, Alignments to connect to old Unified API * Missing reset on TranslationResultBindings * Cleaning up Response documentation to reflect newer code * Minor adjustments to get build back after main sync * Marian seems to make available Catch somehow * Disable COMPILE_BERGAMOT_TESTS for WASM * Add COMPILE_BERGAMOT_TESTS as a CMakeDependent option * Use the COMPILE_TESTS flag instead to skip macos.yml * Trigger unit-tests on GitHub runners for Annotation * Reordering enable_testing() to before inclusion of test directory * doc constructs required to operate with alignments Documents with doxygen compatible documentation for Response, AnnotatedBlob, Annotation, ByteRange. Incorporates doxygen compatible documentation for * Updates ByteRange consistent with general C++ Also little documentation enhancements in the process. * Updating marian-dev@9337105 * Copy-paste documentation because lazy * Turn off autoformat and manually edit to fix style changes * AnnotatedBlob -> AnnotatedText; blob -> text * text.text in test app renamed * text of text -> blob of text in places of documentation
- Loading branch information
Jerin Philip
committed
Mar 31, 2021
1 parent
e0dca1b
commit bfb5e78
Showing
20 changed files
with
509 additions
and
222 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,7 @@ | ||
add_subdirectory(translator) | ||
add_subdirectory(translator) | ||
|
||
if(COMPILE_TESTS) | ||
# Catch currently comes from marian sources. | ||
add_subdirectory(tests) | ||
endif(COMPILE_TESTS) | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# Unit tests | ||
set(UNIT_TESTS | ||
annotation_tests | ||
) | ||
|
||
foreach(test ${UNIT_TESTS}) | ||
add_executable("run_${test}" run_tests.cpp "${test}.cpp") | ||
target_include_directories("run_${test}" PRIVATE ${CATCH_INCLUDE_DIR} "${CMAKE_SOURCE_DIR}/src") | ||
|
||
if(CUDA_FOUND) | ||
target_link_libraries("run_${test}" ${EXT_LIBS} marian ${EXT_LIBS} marian_cuda ${EXT_LIBS} Catch bergamot-translator) | ||
else(CUDA_FOUND) | ||
target_link_libraries("run_${test}" marian ${EXT_LIBS} Catch bergamot-translator) | ||
endif(CUDA_FOUND) | ||
|
||
if(msvc) | ||
# disable c4305: truncation from 'double' to '_ty' | ||
target_compile_options("run_${test}" public /wd4305) | ||
endif(msvc) | ||
|
||
add_test(NAME ${test} COMMAND "run_${test}") | ||
endforeach(test) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
#include "catch.hpp" | ||
#include "translator/sentence_ranges.h" | ||
#include <random> | ||
#include <vector> | ||
|
||
using namespace marian::bergamot; | ||
|
||
TEST_CASE("Test Annotation API with random sentences") { | ||
/// Objective here is to test insertion for sentences, and that whatever comes | ||
/// out adheres to the way it was inserted. Towards this, we keep externally | ||
/// which sentence went in where and try to use accessor methods on | ||
/// AnnotatedText to check if what we have as ground-truth by construction is | ||
/// consistent with what is returned. | ||
size_t sentences = 20; | ||
size_t maxWords = 40; | ||
|
||
std::mt19937 randomIntGen_; | ||
randomIntGen_.seed(42); | ||
|
||
AnnotatedText testAnnotation; | ||
std::vector<std::vector<ByteRange>> sentenceWords; | ||
std::vector<ByteRange> Words; | ||
|
||
for (size_t idx = 0; idx < sentences; idx++) { | ||
if (idx != 0) | ||
testAnnotation.text += "\n"; | ||
|
||
Words.clear(); | ||
size_t words = randomIntGen_() % maxWords + 1; | ||
Words.reserve(words); | ||
for (size_t idw = 0; idw < words; idw++) { | ||
size_t before = testAnnotation.text.size(); | ||
std::string word = std::to_string(idx) + "-" + std::to_string(idw); | ||
testAnnotation.text += word; | ||
if (idw != 0) | ||
testAnnotation.text += " "; | ||
Words.push_back((ByteRange){before, before + word.size() - 1}); | ||
} | ||
// std::cout << std::endl; | ||
|
||
sentenceWords.push_back(Words); | ||
} | ||
|
||
// std::cout << "Inserting words:" << std::endl; | ||
std::vector<std::vector<marian::string_view>> byteRanges; | ||
for (auto &sentence : sentenceWords) { | ||
std::vector<marian::string_view> wordByteRanges; | ||
for (auto &word : sentence) { | ||
marian::string_view wordView(&testAnnotation.text[word.begin], | ||
word.end - word.begin); | ||
wordByteRanges.push_back(wordView); | ||
// std::cout << std::string(wordView) << " "; | ||
} | ||
testAnnotation.addSentence(wordByteRanges); | ||
byteRanges.push_back(wordByteRanges); | ||
// std::cout << std::endl; | ||
} | ||
|
||
// std::cout << "From container: " << std::endl; | ||
for (int idx = 0; idx < sentenceWords.size(); idx++) { | ||
for (int idw = 0; idw < sentenceWords[idx].size(); idw++) { | ||
ByteRange expected = sentenceWords[idx][idw]; | ||
ByteRange obtained = testAnnotation.wordAsByteRange(idx, idw); | ||
// std::cout << std::string(testAnnotation.word(idx, idw)) << " "; | ||
CHECK(expected.begin == obtained.begin); | ||
CHECK(expected.end == obtained.end); | ||
|
||
std::string expected_string = std::string(byteRanges[idx][idw]); | ||
CHECK(expected_string == std::string(testAnnotation.word(idx, idw))); | ||
} | ||
// std::cout << std::endl; | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
#define CATCH_CONFIG_MAIN | ||
#include "catch.hpp" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.