derek/DRAMSys
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixes - repository URL and repository updated

Browse Source 
github --> gitlab
dram.vp.system --> dram.sys
This commit is contained in:
Éder F. Zulian
2018-10-30 16:36:06 +01:00
parent 3655ceb4e4
commit 8bafb07d24
5 changed files with 25 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

62
README.md
View File

@@ -18,67 +18,37 @@ $ mkdir projects
$ cd projects
```
Configure git on your machine. Some basic configurations follow. Replace
**rhrkuser** with your own RHRK user when configuring your email.
Configure git on your machine. Some basic configurations follow.
```bash
$ git config --global user.name "FirstName OtherNames LastName"
$ git config --global user.email rhrkuser@rhrk.uni-kl.de
$ git config --global user.email user@email
$ git config --global credential.helper 'cache --timeout=3600'
$ git config --global color.ui auto
```
Login using your **git.rhrk** account. Fork the repository by clicking in
**Fork** in the upper-right corner of this page.
Now clone **your fork** of the official repository into a local folder on your
computer. Replace the occurrences of the word **user** with your own RHRK user
name. **Note that it appears twice in the line below**.
Now clone the repository into a local folder on your computer.
Replace the occurrences of the word **user** with your own user name.
```bash
$ git clone --recursive https://user@git.rhrk.uni-kl.de/user/dram.vp.system.git
$ git clone --recursive https://user@git.eit.uni-kl.de:ems/astdm/dram.sys.git
```
The *--recursive* flag tells git to initialize all submodules within the
repository. **DRAMPower** [2] and **tinyxml** are examples third party
repositories that were embedded within the source tree as submodules.
Now you can implement, test, commit and push features into your **fork** of
the official repository.
Now you can implement, test, commit and push features into a **branch**.
When you consider your work stable enough to be merged into the official
repository it is time to open a **pull request** using the web interface of
git.rhrk.uni-kl.de.
When you consider your work stable enough to be merged into the master branch
it is time to open a **merge request** using the web interface.
Your changes will be reviewed and finally integrated to the official
repository.
Your changes will be reviewed and finally integrated to the master branch.
After cloning go to the project directory.
```bash
$ cd dram.vp.system
```
When working with a fork, the official repository must be added as a remote for
your fork. Replace the word **user** with your own RHRK user name.
```bash
$ git remote add upstream https://user@git.rhrk.uni-kl.de/EIT-Wehn/dram.vp.system.git
```
In general, from time to time you should update your fork in order to keep it
synchronized with the official repository. It is important to keep track of
the evolution of the official repository and avoid a huge divergence.
To get the latest changes from the official repository merged into your fork
you can use the commands that follow:
```bash
$ git fetch upstream
$ git checkout master
$ git merge upstream/master
$ git push origin HEAD
$ git submodule update --init --recursive
$ cd dram.sys
```
### Dependencies
@@ -167,7 +137,7 @@ $ qtcreator &
Use the menu bar and open the DRAMSys project.
**File -> Open Project -> dram.vp.system/DRAMSys/DRAMSys.pro**
**File -> Open Project -> dram.sys/DRAMSys/DRAMSys.pro**
When you open the project for the first time a configuration window pops-up.
Then click in **Configure Project** and after that **Build** the project.
@@ -312,7 +282,7 @@ has to be changed like [this](https://trac.macports.org/attachment/ticket/44288/
- Install package [xerces](http://xerces.apache.org/mirrors.cgi) if your system does not have.
- Type following command inside your dram.vp.system folder:
- Type following command inside your dram.sys folder:
```bash
$ mkdir build
@@ -981,7 +951,7 @@ Users can profit of running multiple simulations automatically with
[DRAMSylva](DRAMSys/library/resources/scripts/DRAMSylva/DRAMSylva.sh).
Every time you run the script you get a new folder with the name containing
the execution time: dram.vp.system\_YYYY\_MM\_DD-HH.MM.SS.
the execution time: dram.sys\_YYYY\_MM\_DD-HH.MM.SS.
Example on how to run the script:
@@ -993,7 +963,7 @@ $ bash DRAMSylva.sh
To see the generated plots and CSV files:
```bash
$ nautilus dram.vp.system_YYYY_MM_DD-HH.MM.SS/build/simulator
$ nautilus dram.sys_YYYY_MM_DD-HH.MM.SS/build/simulator
```
In that folder you will find plots as PDF files and CSV files with the output
@@ -1007,7 +977,7 @@ data used to generate the plots. The CSV files are:
Use the command below to find all generated CSV files:
```bash
$ ls -l dram.vp.system_YYYY_MM_DD-HH.MM.SS/build/simulator/*.csv
$ ls -l dram.sys_YYYY_MM_DD-HH.MM.SS/build/simulator/*.csv
```
The generated CSV files can be open in a spreadsheet program for further
@@ -1541,7 +1511,7 @@ Copy this configuration file to the building directory of DRAMSys where the
executable **DRAMSys_gem5** is located:
```
dram.vp.system/build-DRAMSys-Desktop_Qt_5_7_0_clang_64bit-Debug/gem5
dram.sys/build-DRAMSys-Desktop_Qt_5_7_0_clang_64bit-Debug/gem5
```
Also the traffic generatior configuration file (conf/tgen.cfg) must be stored