[parsec-users] Input and output file format for Fluidanimate

Christian A Bienia cbienia at CS.Princeton.EDU
Tue Dec 23 16:04:57 EST 2008

Hi Nirav,

The input and output files of fluidanimate are composed of a header containing general information, followed by an array of particles. It's a very simple file format that was created ad hoc for the benchmark program. Please look at the source code to understand its exact structure, it's the only documentation of the format at that point. The input file contains the exact position of the fluid (represented by the particles) at the beginning of the simulation, the output file is the fluid at the end of the simulation.

The README file that comes with the program is not up to date. We specified a total of 6 input files which are labeled from `test' to `native'. You can find more about these input sets and their meaning in the general documentation for PARSEC.

To run the benchmark it's easiest to use the parsecmgmt utility that you can find in the `bin/' directory of the benchmark distribution. The tool will print the exact command line which it uses to the console if you run a benchmark with it.


----- Ursprüngliche Mail -----
Von: "Nirav Shah" <nirav4ever4u at gmail.com>
An: "PARSEC Users" <parsec-users at lists.cs.princeton.edu>
Gesendet: Dienstag, 23. Dezember 2008 21:13:43 GMT +01:00 Amsterdam/Berlin/Bern/Rom/Stockholm/Wien
Betreff: [parsec-users] Input and output file format for Fluidanimate


Can anybody please explain what is required input format for fluidanimate? For test input, a file in tarball named in_5k.fluid is given. What is .fluid format? The output file is also generated with same extension. 

Also, manual says that there are two possible inputs for this package one with 5K size and other with 32M size. I presume 5K sized input is test_input.tar. I have got a small clip of a game sizing around 146M. But, no documentation about how to give this file as input to fluidanimate. 

It would be really helpful if someone can please explain how to run this benchmark with various inputs? What is required format and filenames for the input? How to interpret output? 

Nirav Shah. 

parsec-users mailing list
parsec-users at lists.cs.princeton.edu

More information about the parsec-users mailing list