/**
 * Author: Anthony Sulistio
 * Date: March 2006
 */


Welcome to the Example of how to use GridSim auction extension.
To compile the example source code:
    In Unix/Linux: javac -classpath $GRIDSIM/jars/gridsim.jar:. ExampleAuction.java
    In Windows:    javac -classpath %GRIDSIM%\jars\gridsim.jar;. ExampleAuction.java

where $GRIDSIM or %GRIDSIM% is the location of the gridsimtoolkit package.


To run the class file:
    In Unix/Linux: java -classpath $GRIDSIM/jars/gridsim.jar:. ExampleAuction > file.txt
    In Windows:    java -classpath %GRIDSIM%\jars\gridsim.jar;. ExampleAuction > file.txt


The above command means run the program and output the results into a file
named "file.txt" rather than into screen or standard output.
To prevent from overwriting an existing file, I renamed "file.txt" into
"output.txt"
NOTE: When you open "output.txt" file, it tells you that grid user entities
      sending Gridlets to a selected grid resource.


When running the example file, it will produce the following files:

    sim_trace -> created by the SimJava2 package (lower-level) to trace every
        events (performed by SimJava and GridSim) during the simulation.
        We don't need to worry about this file. Not to important for our
        example.

    sim_report -> created by the SimJava2 package (lower-level) of GridSim.
        This is a simulation report that contains general information about
        running this experiment. We don't need to worry about this file.
        Not to important for our example.

    *.csv -> created by NetUser.java and gridsim.net.RIPRouter.java
        to record every incoming activities.
        The format of this file is:
            simulation_time, ...

        where ... means other descriptive information.

NOTE: sim_trace, sim_report and all *.csv files will be overwritten if running
      a new experiment.