Hm, that's new.
I guess this is connected with moses switching recently to memory pools and no one bothered to check whether the query tool still works after that.

You could check out branch "wipoNew" which still has a Moses 2.1 version, the tool should work there.

W dniu 09.03.2016 o 19:09, Lane Schwartz pisze:
Right. So I added that, and now I get a crash. Here's the backtrace:

    Program received signal SIGABRT, Aborted.
    0x00007ffff5f985e9 in raise () from /lib64/libc.so.6
    Missing separate debuginfos, use: debuginfo-install
    bzip2-libs-1.0.6-12.el7.x86_64 glibc-2.17-78.el7.x86_64
    libgcc-4.8.3-9.el7.x86_64 libstdc++-4.8.3-9.el7.x86_64
    libxml2-2.9.1-5.el7_1.2.x86_64
    xmlrpc-c-1.32.5-1905.svn2451.el7.x86_64
    xmlrpc-c-c++-1.32.5-1905.svn2451.el7.x86_64
    xz-libs-5.1.2-12alpha.el7.x86_64 zlib-1.2.7-13.el7.x86_64
    (gdb) bt
    #0  0x00007ffff5f985e9 in raise () from /lib64/libc.so.6
    #1  0x00007ffff5f99cf8 in abort () from /lib64/libc.so.6
    #2  0x00007ffff5fd8dd7 in __libc_message () from /lib64/libc.so.6
    #3  0x00007ffff5fe01bd in _int_free () from /lib64/libc.so.6
    #4  0x000000000041e763 in std::__valarray_release_memory
    (__p=0x1039600) at /usr/include/c++/4.8.2/bits/valarray_array.h:66
    #5  0x0000000000420c7b in std::valarray<float>::~valarray
    (this=0x1039558, __in_chrg=<optimized out>) at
    /usr/include/c++/4.8.2/valarray:703
    #6  0x000000000041ff1b in Moses::FVector::~FVector
    (this=0x1039528, __in_chrg=<optimized out>) at
    moses/FeatureVector.h:127
    #7  0x0000000000436078 in
    Moses::ScoreComponentCollection::~ScoreComponentCollection
    (this=0x1039528, __in_chrg=<optimized out>) at
    ./moses/ScoreComponentCollection.h:87
    #8  0x000000000055f865 in Moses::TargetPhrase::~TargetPhrase
    (this=0x10394c0, __in_chrg=<optimized out>) at
    moses/TargetPhrase.cpp:151
    #9  0x00000000004c0db7 in std::_Destroy<Moses::TargetPhrase>
    (__pointer=0x10394c0) at
    /usr/include/c++/4.8.2/bits/stl_construct.h:93
    #10 0x00000000004bfdde in
    std::_Destroy_aux<false>::__destroy<Moses::TargetPhrase*>
    (__first=0x10394c0, __last=0x10395f0) at
    /usr/include/c++/4.8.2/bits/stl_construct.h:103
    #11 0x00000000004bebbb in std::_Destroy<Moses::TargetPhrase*>
    (__first=0x10394c0, __last=0x10395f0) at
    /usr/include/c++/4.8.2/bits/stl_construct.h:126
    #12 0x00000000004bdc4b in std::_Destroy<Moses::TargetPhrase*,
    Moses::TargetPhrase> (__first=0x10394c0, __last=0x10395f0) at
    /usr/include/c++/4.8.2/bits/stl_construct.h:151
    #13 0x000000000052028a in std::vector<Moses::TargetPhrase,
    std::allocator<Moses::TargetPhrase> >::_M_insert_aux
    (this=0x1039080, __position=warning: can't find linker symbol for
    virtual table for `Moses::TargetPhrase' value
    ..., __x=...) at /usr/include/c++/4.8.2/bits/vector.tcc:384
    #14 0x000000000051d873 in std::vector<Moses::TargetPhrase,
    std::allocator<Moses::TargetPhrase> >::push_back (this=0x1039080,
    __x=...) at /usr/include/c++/4.8.2/bits/stl_vector.h:913
    #15 0x000000000083341e in Moses::PhraseDecoder::DecodeCollection
    (this=0xfd5130, tpv=..., encodedBitStream=..., sourcePhrase=...,
    topLevel=true, eval=false)
        at moses/TranslationModel/CompactPT/PhraseDecoder.cpp:279
    #16 0x0000000000833087 in
    Moses::PhraseDecoder::CreateTargetPhraseCollection (this=0xfd5130,
    sourcePhrase=..., topLevel=true, eval=false) at
    moses/TranslationModel/CompactPT/PhraseDecoder.cpp:237
    #17 0x00000000004bbb1f in
    Moses::PhraseDictionaryCompact::GetTargetPhraseCollectionRaw
    (this=0x7fffffffda50, sourcePhrase=...) at
    moses/TranslationModel/CompactPT/PhraseDictionaryCompact.cpp:148
    #18 0x000000000040ef67 in main (argc=6, argv=0x7fffffffe298) at
    misc/queryPhraseTableMin.cpp:64


On Wed, Mar 9, 2016 at 1:02 PM, Marcin Junczys-Dowmunt <junc...@amu.edu.pl <mailto:junc...@amu.edu.pl>> wrote:

    Your phrase table has 11 scores, you need to add  "-n 11"

    W dniu 09.03.2016 o 19:01, Lane Schwartz pisze:

        $ ./bin/queryPhraseTableMin -t
        newstest2013.filtered.3/phrase-table.0-0.1.1.minphr <<< "une"
        terminate called after throwing an instance of 'util::Exception'
          what(): moses/ScoreComponentCollection.cpp:252 in void
        Moses::ScoreComponentCollection::Assign(const
        Moses::FeatureFunction*, const std::vector<float>&) threw
        util::Exception.
        Feature function PhraseDictionaryCompact0 specified 4 dense
        scores or weights. Actually has 11
        Aborted (core dumped)


    Am I calling this correctly? Something's not right.

    On Wed, Mar 9, 2016 at 12:56 PM, Marcin Junczys-Dowmunt
    <junc...@amu.edu.pl <mailto:junc...@amu.edu.pl>> wrote:

        There is queryPhraseTableMin that reads phrases from stdin
        and returns all entries in the compact phrase table. Just do
        a script that generates all substrings from a sentence and
        pass it to that program.

        W dniu 09.03.2016 o 18:53, Lane Schwartz pisze:
        Ah, excellent! Can this info be gotten via one of the
        standalone query programs? I've never used those, but I'm
        guessing that's what they're for?

        I have a phrase-table.0-0.1.1.gz that looks like this:

            a , au contraire , ||| , however , ||| 6.70231e-06
            1.67288e-09 0.0150266 0.00200436 2.718 1 1 1 1 1 1 |||
            1-0 2-1 3-1 4-2 ||| 17936 8 1 ||| |||
            a , au contraire , ||| , instead , ||| 0.000785703
            5.71013e-05 0.0150266 0.022757 2.718 1 1 1 1 1 1 ||| 1-0
            2-1 3-1 4-2 ||| 153 8 1 ||| |||

        And I have a phrase-table.0-0.1.1.minphr.

        What would be the recommended mechanism for getting phrases
        for a particular sentence using a query program?

        Thanks,

        Lane



        On Wed, Mar 9, 2016 at 12:42 PM, Marcin Junczys-Dowmunt
        <junc...@amu.edu.pl <mailto:junc...@amu.edu.pl>> wrote:

            With verbose 3 it's actually there, just before it
            starts outputting the search graph, take another look.
            There is a list sorted by source sentence spans.

            W dniu 09.03.2016 o 18:39, Lane Schwartz pisze:
            I don't suppose anyone knows of a relatively easy way
            to print the list of translation options for each
            sentence?

            verbose=2 tells how many translation options there are,
            but not what they are
            verbose=3 prints the search graph as it's being
            constructed, but still not what I'm looking for

            Thanks,
            Lane



            _______________________________________________
            Moses-support mailing list
            Moses-support@mit.edu <mailto:Moses-support@mit.edu>
            http://mailman.mit.edu/mailman/listinfo/moses-support




-- When a place gets crowded enough to require ID's, social
        collapse is not
        far away.  It is time to go elsewhere.  The best thing about
        space travel
        is that it made it possible to go elsewhere.
                        -- R.A. Heinlein, "Time Enough For Love"




-- When a place gets crowded enough to require ID's, social collapse
    is not
    far away.  It is time to go elsewhere.  The best thing about
    space travel
    is that it made it possible to go elsewhere.
                    -- R.A. Heinlein, "Time Enough For Love"




--
When a place gets crowded enough to require ID's, social collapse is not
far away.  It is time to go elsewhere.  The best thing about space travel
is that it made it possible to go elsewhere.
                -- R.A. Heinlein, "Time Enough For Love"

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to