Charm++ parallel programming system

[Balaji S <balaji.ceg.13 AT gmail.com>]

Thanks for the clarification on tools, and what about the tool log2proj? It gives some matrix like data as output? Clarification please

On Mon, Feb 27, 2012 at 10:36 PM, Mokos, Ryan <mokos AT illinois.edu> wrote:

Hi Balaji,

loadlog converts bgTrace files from binary to ASCII format so you can see what events they contain.  buildlog lets you create bgTrace binary files by calling the log API functions directly, rather than emulating an actual program.

Please note that these are both older tools.  If you want to view bgTrace files in ASCII format, I would suggest that you use the LogAnalyzer tool that comes with BigNetSim.  It can be found in the BigNetSim/trunk/tools/LogAnalyzer directory.  LogAnalyzer has a number of options for analyzing traces.  #2 is the one you would use for binary -> ASCII conversion.

If you want to create your own bgTrace files without an emulation run, use the text2log tool in charm/examples/bigsim/tools/text2log.  It's more powerful, easier to use than learning the log API, and it performs a number of checks to ensure that the trace files you create are valid.

Ryan

---

From: ppl-bounces AT cs.uiuc.edu [ppl-bounces AT cs.uiuc.edu] on behalf of Balaji S [balaji.ceg.13 AT gmail.com]
Sent: Sunday, February 26, 2012 7:27 AM
To: charm AT cs.uiuc.edu
Subject: [ppl] [charm] Trace files

Hi ,
        What are the use of tools, Loadlog and Buildlog in charm/examples/bigsim/tools.
Are they used to convert the bgtrace* files to ASCII text log files?

--
With Regards,
    Balaji.S

-- 
With Regards,
    Balaji.S