Serial Code for Project due

At this point the code does not need to be optimized. If you have time, it would be best to include the results of benchmarking and/or profiling in the README, to help both you and the reviewer identify which sections are ammenable to optimization.

Grading Rubric

Preparing Your Own Code for Review

Provide overview to help reviewer

Please provide your reviewers with a README or other instructions to help them figure out how to spend their time reviewing your code in a way that is most likely to be helpful to you.

Make sure code is in plain text files (i.e., not only Jupyter notebooks)

Jupyter and Pluto notebooks are great to document how to use your code. As functions mature, it’s nature to move well tested functions into ‘.jl’ files. If your code is in the form of julia code (.jl files) or markdown (.jmd) or a Pluto notebook (also a .jl file), then reviewer can already comment on your code directly in GitHub. If you’ve been developing code inside a Jupyter notebook (.ipynb file), then remember to create (and commit and push) a .jl or .jmd version for your reviewers to comment on, just as you’ve been doing for homework assignments.

julia -e 'using Weave; convert_doc("NOTEBOOK_NAME.ipynb","NOTEBOOK_NAME.jmd")'

Organize your files.

If you only have a few functions, then (for now) it’s reasonable to have just one file for your main code and one file for tests. If you already have a larger code base, then organize your functions into multiple files .jl and place them in a src directory. Similiarly, use test, and optionally examples and docs directories to make it clear where user/reviewers can find tests, examples and additional documentation.

Give your reviewer permission to access your repository.

Go to your repository’s GitHub page and click “Settings” and “Collaborators & teams”. Under “Collaborators” (near the bottom), there’s a box “Search by username, full name or email address”. Enter the github username of your peer reviewer(s). Then click “Add collaborator”. The easiest option is to leave the permission level as “Write”.1 That should trigger an email inviting them to join the repository2. If your project repo was created by following the link I gave, then I should already have access to your project repository. If you created your project repository some other way, then please send me an email with “Astro 528 project url” in the subject line and the repo url in the message body (as well as the github id of your partner if working in a team).

  1. If you’d rather not give your peer reviewer write access to your repository, then you could create a new repository, copy your files into that repository, and given your peer reviewer write access to just that repository copy. You’d also need to invite your instructor to have access to your new repository. (Personally, I doubt it’s worth the extra effort.) ↩︎

  2. Some times automated emails from github can be overlooked. So if it might be nice if you also click “Copy invite link”, click the little clipboard icon, and send them an email saying “here’s the link to my repository for you to review”. ↩︎