Argument `--upgrade` (re)installs the package, even if the version number hasn't changed.
Argument `--upgrade` (re)installs the package, even if the version number hasn't changed.
...
@@ -14,11 +16,11 @@ Argument `--upgrade` (re)installs the package, even if the version number hasn't
...
@@ -14,11 +16,11 @@ Argument `--upgrade` (re)installs the package, even if the version number hasn't
**TODO:** Add instructions for how to obtain and prepare the involved data. See also `preprocessing/README.md`.
**TODO:** Add instructions for how to obtain and prepare the involved data. See also `preprocessing/README.md`.
1. Obtain and prepare data
1. Obtain and prepare data, see `preprocessing/README.md`.
1. Run `mu-moss --help` for arguments that can/must be configured. Afterwards, run `mu-moss` as desired.
1. Run `mu-moss --help` for arguments that can/must be configured. Afterwards, run `mu-moss` as desired, e.g. `mu-moss -u 1234 -n 300 "./ex1/*/main.cpp"`.
`mu-moss` connects to the Moss service, uploads submissions and downloads the generated report.
`mu-moss` connects to the Moss service, uploads submissions and downloads the generated report. This may take a while, and will probably not work for large `-n` values (3000 worked for me, 10,000 didn't).
* Replace `<python3>/Lib/site-packages/mossum/mossum.py` with `MODIFIED-mossum.py`
* http://networkx.github.io/
*`pip install networkx`
## Tidying up files and directories
## Tidying up files and directories
*`cx-dump_bonus-exercise-1_2020-04-17.zip` contains the latest submission from each user
*`cx-dump_bonus-exercise-1_2020-04-17.zip` contains the latest submission from each user
* Execute next commands on the level of the user directories, e.g. in `./bonus_exercise_1`, so that, e.g. `./bonus_exercise_1/<user>` are the individual user directories
* Execute commands on the level of the user directories, e.g. in `./bonus_exercise_1`, so that, e.g. `./bonus_exercise_1/<user>` are the individual user directories
* Assumption: relevant files per submission are `<user>/details.json` and `<user>/files/main.cpp`, whereas all other files and directories can be deleted:
* Assumption: relevant files per submission are `<user>/details.json` and `<user>/files/main.cpp`, whereas all other files and directories can be deleted:
* Now, each `<user>` directory should only have two files in it: `<user>/main.cpp` and `<user>/details.json`
## Renaming user directories
## Renaming user directories
* Rename directories from user names to Legi numbers before submitting data to Moss, e.g. rename `scmalte` to `01-234-567`. The file `<user>/details.json` provides the Legi number.
* Rename directories from user names to Legi numbers before submitting data to Moss, e.g. rename `scmalte` to `01-234-567`. The file `<user>/details.json` provides the Legi number.
...
@@ -53,37 +46,7 @@
...
@@ -53,37 +46,7 @@
```plain
```plain
$ cd ./bonus_exercise_1
$ cd ./bonus_exercise_1
$ ../rename_to_legi.sh
$ <path-to-mossutils>/rename_to_legi.sh
```
```
The script prompts for confirmation before the first renaming is executed.
The script prompts for confirmation before the first renaming is executed.
## Moss
### moss.py
* Edit `moss.py` and check configuration
* Execute `moss.py` from e.g. `./bonus_exercise_1/`:
```plain
$ cd ./bonus_exercise_1/
$ python ../moss.py
```
* If not configured otherwise, open `./bonus_exercise_1/moss-report.html` in your browser
### clusters.py
* Edit `clusters.py` and check configuration
* Execute `clusters.py` from e.g. `./bonus_exercise_1/`:
```plain
$ cd ./bonus_exercise_1/
$ python ../clusters.py
```
* If not configured otherwise, open `./bonus_exercise_1/clusters.html` in your browser