June 2015 - Boost-users - lists.preview.boost.org

Printing local edge list in PBGL
by Alexander Frolov 23 Jun '15

23 Jun '15

Hi, I have a simple program using PBGL (boost 1.58) which creates an undirected graph and prints local edge list for the specified process. However, only for zero process the list (edges(g)) contains edge descriptors, while for non-zero processes the list is empty, which is strange, is it not? The program text is following: using namespace boost; using boost::graph::distributed::mpi_process_group; using boost::graph::parallel::process_group; std::size_t nVertices = 16; int main(int argc, char **argv) { boost::mpi::environment env(argc, argv); mpi_process_group pg; typedef adjacency_list<listS, distributedS<mpi_process_group, vecS>, undirectedS, // Vertex properties no_property, // Edge properties property<edge_weight_t, int> > Graph; Graph g(nVertices); if (process_id(pg) == 0) { std::cout << "MST Boost running..." << std::endl; std::cout << "\tnumber of mpi processes is " << num_processes(pg) << std::endl; std::cout << "\tnumber of vertices is " << nVertices << std::endl; std::cout << "\tnumber of edges is " << /*nEdges*/ nVertices << std::endl; std::cout << "Constructing graph..."; for (int i = 0; i < nVertices; i++) { uint64_t s = (i < nVertices/2) ? 0 : nVertices/2; //uint64_t s = 0; uint64_t d = i; uint64_t w = rand(); add_edge(vertex(s, g), vertex(d, g), w, g); } std::cout << "...completed" << std::endl; } synchronize(pg); typedef property_map<Graph, edge_weight_t>::type WeightMap; WeightMap weight_map = get(edge_weight, g); if (process_id(pg) == atoi(argv[1])){ std::cout << "printing vertices:\n"; Graph::vertex_iterator v, v_end; for (boost::tie(v,v_end) = vertices(g); v != v_end; v++) { std::cout << process_id(pg) << ": (" << local(*v) << "@" << owner(*v) << ")\n"; } std::cout << "end of vertex list.\n"; std::cout << "printing edges:\n"; for (typename Graph::edge_iterator ei = edges(g).first; ei != edges(g).second; ei++) { std::cout << process_id(pg) << ": (" << local(source(*ei, g)) << "@" << owner(source(*ei,g)) << "," << local(target(*ei, g)) << "@" << owner(target(*ei,g)) << "," << get(weight_map, *ei) << ")\n"; } std::cout << "end of edge list.\n"; } return 0; } The output for the process 0: mpirun -np 2 ./simple_test 0 MST Boost running... number of mpi processes is 2 number of vertices is 16 number of edges is 16 Constructing graph......completed printing vertices: 0: (0@0) 0: (1@0) 0: (2@0) 0: (3@0) 0: (4@0) 0: (5@0) 0: (6@0) 0: (7@0) end of vertex list. printing edges: 0: (0@0,0@0,1804289383) 0: (0@0,1@0,846930886) 0: (0@0,2@0,1681692777) 0: (0@0,3@0,1714636915) 0: (0@0,4@0,1957747793) 0: (0@0,5@0,424238335) 0: (0@0,6@0,719885386) 0: (0@0,7@0,1649760492) 0: (0@0,0@1,596516649) 0: (0@0,1@1,1189641421) 0: (0@0,2@1,1025202362) 0: (0@0,3@1,1350490027) 0: (0@0,4@1,783368690) 0: (0@0,5@1,1102520059) 0: (0@0,6@1,2044897763) 0: (0@0,7@1,1967513926) end of edge list. The output for the process 1: mpirun -np 2 ./simple_test 1 MST Boost running... number of mpi processes is 2 number of vertices is 16 number of edges is 16 Constructing graph......completed printing vertices: 1: (0@1) 1: (1@1) 1: (2@1) 1: (3@1) 1: (4@1) 1: (5@1) 1: (6@1) 1: (7@1) end of vertex list. printing edges: end of edge list. Is it ok? or there is a bug in the code? Appreciate any help. Thanks a lot. Best, Alex

1 0

Re: [Boost-users] [datetime] little problem with periods
by Georg.Kellerer＠lfu.bayern.de 23 Jun '15

23 Jun '15

Hi Boris, thanks for your help. In fact I didn't know that. Georg -----Ursprüngliche Nachricht----- Von: Boost-users [mailto:boost-users-bounces@lists.boost.org] Im Auftrag von Boris Schäling Gesendet: Dienstag, 23. Juni 2015 14:46 An: boost-users(a)lists.boost.org Betreff: Re: [Boost-users] [datetime] little problem with periods On Tue, 23 Jun 2015 13:42:03 +0200, <Georg.Kellerer(a)lfu.bayern.de> wrote: > Hello, > > i am using Boost V1.5.8 under vs 2010 with a german windows 7 64 bit. > When I tried to calculate a time period I always ran into the same > problem. The period is calculated one day too short. I wrote a little > program to illustrate my problem. It's important that you change the > value of the variable test to the current date. Is this a bug or do I > use the library in an incorrect way? The end of the period is not considered part of the period (see <http://theboostcpplibraries.com/boost.datetime-calendar#ex.datetime_08> or <http://dieboostcppbibliotheken.de/boost.datetime-kalenderdaten#ex.datetime_…> if you prefer German). HTH, Boris > [...] _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] [datetime] little problem with periods
by Georg.Kellerer＠lfu.bayern.de 23 Jun '15

23 Jun '15

Hello Michael, > Is date period a boost function or one of your own? No, its part of boost. Georg

1 0

[Serialization] Boost segfaults in archive/basic_xml_iarchive.hpp
by Mccall, Kurt E. (JSC-EG411) 22 Jun '15

22 Jun '15

If someone could help me diagnose this segmentation fault, I'd appreciate it greatly. It has stumped me for a couple of days. I'm deserializing a non-polymorphic derived class, and Boost crashes when it attempts to process the base class: Here is the pseudocode: struct Base { int id_; std::string long_name_; template<Archive> void serialize(Archive & ar, const unsigned int file_version) { ar & BOOST_SERIALIZATION_NVP(id_); ar & BOOST_SERIALIZATION_NVP(long_name_); // SEGFAULT OCCURS HERE } } struct Derived : public Base { template<Archive> void serialize(Archive & ar, const unsigned int file_version) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(Base); … } } I tried the methods described at http://stackoverflow.com/questions/3396330/where-to-put-boost-class-export-… for exporting the derived class using BOOST_CLASS_EXPORT, but none of them affected the segfault. I guess that it isn't really necessary to export non-polymorphic derived classes. Anyway, the code crashes in archive/basic_xml_iarchive.hpp in this code at line 92: // Anything not an attribute - see below - should be a name value // pair and be processed here typedef detail::common_iarchive<Archive> detail_common_iarchive; template<class T> void load_override( #ifndef BOOST_NO_FUNCTION_TEMPLATE_ORDERING const #endif boost::serialization::nvp< T > & t, int ){ this->This()->load_start(t.name()); this->detail_common_iarchive::load_override(t.value(), 0); // SEGFAULT OCCURS HERE this->This()->load_end(t.name()); } In GDB, "this" has a valid address ( 0x7fffffffdb30) as does "t" (0x7ffffff487b0). In GDB, executing t.name() yielded the correct name "long_name_", but when executing t.value(), the debugger complained about an invalid address: RuntimeError: Cannot access memory at address 0xffffffffffffffe8 That error message comes from GDB's Python utility for pretty-printing strings (the variable being deserialized is a std::string), which is invoked when I print t.value(), but regardless something is wrong in t.value(). Does any of this suggest what I might be doing wrong? Thanks for any help.

2 2

[Serialization] Non-default constructor and template class
by Mccall, Kurt E. (JSC-EG411) 22 Jun '15

22 Jun '15

I am attempting to serialize a template class without a default constructor, so I am overriding boost::serialization::save_construct_data(). I'm not sure of the correct syntax to declare that function. The line marked below fails to compile with a "too many template-parameter-lists" error. // Forward declaration of my class template<class Key, class Value, class Hasher> class HashMap; namespace boost { namespace serialization { template<class Archive> template<class Key, class Value, class Hasher> void save_construct_data(Archive &ar, const HashMap< Key, Value, Hasher > *t, const unsigned int file_version); // error here }} Thanks for any help, Kurt

4 4

[Variant]Maximum Limit of types in variant and fusion vector
by Elizabeta 21 Jun '15

21 Jun '15

Hi I want to use boost::variant with types more than 50. Until now I was using boost::variant with types up to 50 like this : #define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS #define BOOST_MPL_LIMIT_LIST_SIZE 50 #define BOOST_MPL_LIMIT_VECTOR_SIZE 50 #include <boost/variant.hpp> However , now if I change BOOST_MPL_LIMIT_LIST_SIZE and BOOST_MPL_LIMIT_VECTOR_SIZE to 100 it gives me compiler errors: Cannot open include file: 'boost/mpl/list/list100.hpp': No such file or directory So is 50 the maximum limit of types that can be put in the variant ? Also it seems that the maximum limit of types for vector fusion is 50, and can't increase that, and I want to have fusion vector for more than 50. Is this possible. Any suggestion -- View this message in context: http://boost.2283326.n4.nabble.com/Variant-Maximum-Limit-of-types-in-varian… Sent from the Boost - Users mailing list archive at Nabble.com.

4 5

bimap : Ordering
by Norman Goldstein 20 Jun '15

20 Jun '15

When iterating though a bimap with a left iterator, I notice that for the pairs having the same left member e.g. (L, R1) (L,R2), (L,R3), ... the pairs are not in increasing R, but in the insertion order of the pairs. Is this an artefact of the design, or an intention? The actual bimap I am using is typedef boost::bimap< boost::bimaps::multiset_of< unsigned int >, boost::bimaps::multiset_of< unsigned int >, boost::bimaps::set_of_relation<>, boost::bimaps::with_info< int > > BMAP; I set it up so that info stores the insertion order index. Thanks.

1 0

[Test] Small Enhancement Suggestion
by Merrill Cornish 19 Jun '15

19 Jun '15

I couldn't find the official way of suggesting an enhancement, but here goes: When a Boost Test currently runs in console mode, it logs the message lines "Running X test cases..." at the start and "*** Y failure detected in test suite 'My Test Suite' " at the end. That's all good. However, if <ahem> the test goes bad wrong and never reaches the end, there is no record in the log of which test did it. Suggestion: Change the initial log message to include the test suite name. For example, "Running X test cases from 'My Test Suite'" Merrill Cornish

2 1

Re: [Boost-users] [IPC Named Mutex]
by Lorenzo Trivelli 19 Jun '15

19 Jun '15

> >One thing you could try...in interprocess's win32_api.hpp, there is another implementation of get_last_bootup_time() which uses WMI instead of the event log (there were warnings in the source about WMI not supporting hibernation/clock changes correctly, so beware). If you define >BOOST_INTERPROCESS_BOOTSTAMP_IS_LASTBOOTUPTIME >it should use that other version...give that a try. (in visual studio Project Properties -> C/C++ -> Preprocessor -> Preprocessor Definitions: add a semi colon ';' then t Thanks Tom, I'll try to fallback to the "old" WMI version (which BTW worked in the 1.44 version I we used before) I'd also be glad to fix it by myself and so help boost developement, , but I do not completely understand the usage of the system boot time... If boost needs in some way a tmestamp to differentiate things, in my opinion there are plenty of them to use instead of the last boot time. Obviously it has been done for a reason, but I cannot understand why :-D Best regards Lorenzo

6 11

Linking Boost Log
by Florian Lindner 19 Jun '15

19 Jun '15

Hello, I try to compile/link a boost log example: http://www.boost.org/doc/libs/1_58_0/libs/log/example/doc/tutorial_file.cpp Using: g++ boostlog.cpp -lboost_log -lpthread with g++ 5.1.0 and boost 1.58 on arch linux. The trivial examples worked fine when I put #define BOOST_LOG_DYN_LINK 1 at the very first line. But with this example I get % g++ boostlog.cpp -lboost_log -lpthread /usr/bin/ld: /tmp/ccT2pz5x.o: undefined reference to symbol '_ZN5boost6detail12set_tss_dataEPKvNS_10shared_ptrINS0_20tss_cleanup_functionEEEPvb' /usr/lib/libboost_thread.so.1.58.0: error adding symbols: DSO missing from command line Probably a missing library but which one? I've not really found any linking documentation and I was guessing so far... Thanks, Florian

1 0