<commit_before>sp17-i524
----------

Repository: https://github.com/cloudmesh/sp17-i524

Class submissions for Spring 2017 i524

1. You will be assigned a **homework id** (or HID in the rest of this document).
2. You will be assigned a **project id** (or PID in the rest of this document).
3. Fork this repository
4. Clone your forked repository
5. Add the upstream repository https://help.github.com/articles/configuring-a-remote-for-a-fork/  ::

   $ git remote add upstream https://github.com/cloudmesh/sp17-i524

6. Keep your fork up to date https://help.github.com/articles/syncing-a-fork/  ::

   $ git fetch upstream
   $ git merge upstream/master
   
7. Push your changes to your fork

   ::
   
     $ git push
     
8. Create a pull request

Before submitting, use the `check-paper.sh` and `check-project.sh`
script to check for some common submission errors.



Submissions
-----------

Setup your paper or project using the ``setup`` script.
For example, if my HID is `S17-EX-0000`::

  $ ./setup paper1 S17-EX-0000

This will setup a directory ``paper1/S17-EX-0000`` with all LaTeX
materials to work on.

Please make your changes to ``report.tex``.

Before submitting a pull request, you should run the
``check-paper.sh`` and ``check-project.sh`` scripts as needed::

  $ ./check-paper.sh paper#/HID


When ready to submit, create a pull request to
https://github.com/cloudmesh/sp17-i524 with the subject in the form
`paper# HID`. For example: `paper1 sp17-st000`

<commit_msg>chg:dev: fork link<commit_after>sp17-i524
----------

Repository: https://github.com/cloudmesh/sp17-i524

Class submissions for Spring 2017 i524

1. You will be assigned a **homework id** (or HID in the rest of this document).
2. You will be assigned a **project id** (or PID in the rest of this document).
3. Fork this repository: https://github.com/cloudmesh/sp17-i524#fork-destination-box
4. Clone your forked repository
5. Add the upstream repository https://help.github.com/articles/configuring-a-remote-for-a-fork/  ::

   $ git remote add upstream https://github.com/cloudmesh/sp17-i524

6. Keep your fork up to date https://help.github.com/articles/syncing-a-fork/  ::

   $ git fetch upstream
   $ git merge upstream/master
   
7. Push your changes to your fork::
   
     $ git push origin master
     
8. Create a pull request

Before submitting, use the `check-paper.sh` and `check-project.sh`
script to check for some common submission errors.



Submissions
-----------

Setup your paper or project using the ``setup`` script.
For example, if my HID is `S17-EX-0000`::

  $ ./setup paper1 S17-EX-0000

This will setup a directory ``paper1/S17-EX-0000`` with all LaTeX
materials to work on.

Please make your changes to ``report.tex``.

Before submitting a pull request, you should run the
``check-paper.sh`` and ``check-project.sh`` scripts as needed::

  $ ./check-paper.sh paper#/HID


When ready to submit, create a pull request to
https://github.com/cloudmesh/sp17-i524 with the subject in the form
`paper# HID`. For example: `paper1 sp17-st000`


{'fraction_non_alphanumeric': 0.11882160392798691, 'fraction_numerical': 0.04157119476268412, 'mean_word_length': 3.29817158931083, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 11, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1135171', 'n_tokens_mistral': 1054, 'n_tokens_neox': 938, 'n_words': 369}