|
1 | 1 |
|
2 | 2 | ### Table of Contents |
3 | 3 |
|
4 | | -1. [Installation](#example) |
5 | | -2. [Project Motivation](#example2) |
6 | | -3. [File Descriptions](#third-example) |
7 | | -4. [Results](#example) |
8 | | -5. [Licensing, Authors, and Acknowledgements](#example2) |
| 4 | +1. [Installation](#installation) |
| 5 | +2. [Project Motivation](#motivation) |
| 6 | +3. [File Descriptions](#files) |
| 7 | +4. [Results](#results) |
| 8 | +5. [Licensing, Authors, and Acknowledgements](#licensing) |
9 | 9 |
|
10 | | -## Installation |
| 10 | +## Installation <a name="installation"></a> |
11 | 11 |
|
12 | 12 | Extra libraries that are not installed with the Anaconda distribution, as well as what what version of python you are using should be noted. |
13 | 13 |
|
14 | | -## Project Motivation |
| 14 | +## Project Motivation<a name="motivation"></a> |
15 | 15 |
|
16 | 16 | Discuss what your project is about, and what interested you in pursuing the project. |
17 | 17 |
|
18 | | -## File Descriptions |
| 18 | +## File Descriptions <a name="files"></a> |
19 | 19 |
|
20 | 20 | Guide others through the files in your repository. You may not talk about every file here, but you should let them know where they can find the work they might find most interesting. |
21 | 21 |
|
22 | | -## How To Interact With Your Project |
| 22 | +## Results<a name="results"></a> |
23 | 23 |
|
24 | 24 | When your project isn't meant to be interactive or used for other projects, you should instead talk about the technical details of your project. What were your results? What did you do to improve them? What methods did you try? What worked? What didn't work? |
25 | 25 |
|
26 | | -## Licensing, Authors, Acknowledgements |
| 26 | +## Licensing, Authors, Acknowledgements<a name="licensing"></a> |
27 | 27 |
|
28 | 28 | You always want to give credit where necessary. Acknowledge other contributors, helpful peers, data providers, etc. |
29 | 29 |
|
0 commit comments