1. Untar the xerces-c-3.1.1.tar.gz.
Install the xerces parser in the /opt directory. 
To do this go to unpacked directory: cd xerces-c-3.1.1
Run:
./configure --prefix=/usr
Now Run:
make
Finally Run:
make install
This will install xerces parser in your machine.


2. It contains a script file (maketotalconfig.sh) that builds and runs TejasPowerPack or GPUTejasPowerPack or both.

Run the script file: ./maketotalconfig.sh with any of the three parameters: GPUTejas, Tejas, all. GPUTejas parameter will generate config file
for GPUTejas Simulator only. Tejas parameter will generate config file for Tejas Simulator only. All paramter will generate config file for both
the simulators.

   
3. Both the simulators need <DynamicEnergy> and <LeakageEnergy> in nJ (10^(-9))for each of the components present in a processor/SM.
<DynamicEnergy> = dynamic energy per access.
<LeakageEnergy> = leakage energy per cycle.
These energy values are provided by mcpat and orion.

4. For direct usage, the default config_tpp.xml and config_gtpp.xml are provided inside respective folders Tejaspowerpack and GPUTejasPowerPack.
All the power values in these config files are generated at 22nm. 

5. The 22nm technology at which the power values are generated is referred to as <baseline_technology> in the Tejas and GPUTejas config file.
There is a tag <technology> just before <baseline_technology>. This <technology> tag tells us the technology at which you want Tejas/GPUTejas to work. 
		If (<baseline_technology> = <technology>)
			use the same power values present in the config_tpp/config_gtpp.xml
		else
			use the conversion Table.

Conversion Table:
Technology Nodes			Power
65->45nm				0.626x
45->32nm				0.626x
32->22nm 				0.648x
22->14nm				0.664x
14->10nm				0.671x

6. In case, you don't want to use the conversion table and generate your own power values, you need to specify the technology
at the <baseline_technology> tag. (This is the tag that is being read by the Tejas Power Pack/GPUTejas Power Pack wrappers).

7. If you want to get further simulator specific information, head on to the Readme in respective simulator folders.

8. In case you don't want to build and run the softwares from this location, there is a makeconfig.sh provided inside
respective folders' UpdateConfig directory. This makeconfig.sh will build the particular software in whose directory it is located.

9. To provide your own parameters to GPUTejas config file, there is a expectedconfig.cfg file located in /GPUTejasPowerPack/UpdateConfig.
You can modify your parameters there. It will be automatically updated in the config file that will be subsequently used by the power pack
to generate the energy numbers for the gputejas config file.
