leaving out options from engine constructor (as shown in example) results in compilation error

[Tristan Slominski]

code version at latest commit: dd438c266a5fff24a38c7a1edce05973531c7da1

In documentation here:  http://docs.graphlab.org/using_graphlab_distributed_graph_vertex_program.html

In section "Running the Vertex Program" the following example code indicates that last parameter graphlab_options& can be skipped:

graphlab::omni_engine<pagerank_program> engine(dc, graph, "sync");

engine.signal_all();

engine.start();

However, following that pattern resulted in:

/path/to/mypagerank.cpp:143:74: error: no matching function for call to ‘graphlab::omni_engine<pagerank_program>::omni_engine(graphlab::distributed_control&, graph_type&, std::string&)’

/path/to/mypagerank.cpp:143:74: note: candidates are:

Only, after providing a dummy option, does compilation succeed:

 

graphlab::command_line_options clopts("blah blah.");

graphlab::omni_engine<pagerank_program> engine(dc, graph, "sync", clopts);

engine.signal_all();

engine.start();

This was surprising and definitely increased "time to first pagerank hello world" :)

[Joseph Gonzalez]

Thank you for notifying us!  We forgot to add a default argument to the omni_engine constructor.  I have corrected the code and updated the release archives.   

Thanks,

Joey