Collaborative git: Difference between revisions
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
Do the exercises in '''Python''' where applicable. Use git to track changes. Make one program per exercise (if relevant). Commit at least once per solved exercise - more often if you feel it relevant. At the end push everything to GitHub or more frequently if that is your pleasure - backup is nice. You gather all exercises into one file and hand that in on DTU Learn, hint ''cat'' in Unix. This is going to be the way we operate for large parts of the course.<br> | Do the exercises in '''Python''' where applicable. Use git to track changes. Make one program per exercise (if relevant). Commit at least once per solved exercise - more often if you feel it relevant. At the end push everything to GitHub or more frequently if that is your pleasure - backup is nice. You gather all exercises into one file and hand that in on DTU Learn, hint ''cat'' in Unix. This is going to be the way we operate for large parts of the course.<br> | ||
# Create a new private repository for your collaborative exercises for '''this single lesson''' on [https://github.com GitHub] as described in the powerpoint. You can choose whatever name you like for the repository. Form a little group, preferably a group of two, but max three if a person is left out. Invite your fellow group members to your repository. You are to "share" repositories.<br><br> | # Create a new private repository for your collaborative exercises for '''this single lesson''' on [https://github.com GitHub] as described in the powerpoint. You can choose whatever name you like for the repository. Form a little group, preferably a group of two, but max three if a person is left out. Invite your fellow group members to your repository. You are to "share" repositories. As an alternative to forming a small group, you can create two repos of your GitHub repository as shown in the powerpoint.<br><br> | ||
# Copy exercise 9 from last week into your new repository and introduce an error in the exercise. Make it a real algorithm error, not just a syntax error. The hand-in for this exercise is your "bad" program.<br><br> | # Copy exercise 9 from last week into your new repository and introduce an error in the exercise. Make it a real algorithm error, not just a syntax error. The hand-in for this exercise is your "bad" program.<br><br> | ||
# Now switch with the other person: Download his/hers repo, fix the error, push it back to the repo. The other person must accept the change on GitHub. The hand-in for this exercise is the fixed program.<br><br> | # Now switch with the other person: Download his/hers repo, fix the error, push it back to the repo. The other person must accept the change on GitHub. The hand-in for this exercise is the fixed program.<br><br> | ||
Revision as of 17:18, 20 February 2026
| Previous: Solo git | Next: Functions, namespace, memory management |
Required course material for the lesson
Powerpoint: Git
Optional - do you want to know more
Online: Coderefinery's introduction to git This is one of many git resources on the net.
Online: Markdown guide
Online: CI/CD - Continuous Integration and Continuous Delivery. It’s a DevOps practice used with GitHub/GitLab.
Subjects covered
- GitHub - inviting people to your repo
- Git - branching, merging
Exercises to be handed in
Do the exercises in Python where applicable. Use git to track changes. Make one program per exercise (if relevant). Commit at least once per solved exercise - more often if you feel it relevant. At the end push everything to GitHub or more frequently if that is your pleasure - backup is nice. You gather all exercises into one file and hand that in on DTU Learn, hint cat in Unix. This is going to be the way we operate for large parts of the course.
- Create a new private repository for your collaborative exercises for this single lesson on GitHub as described in the powerpoint. You can choose whatever name you like for the repository. Form a little group, preferably a group of two, but max three if a person is left out. Invite your fellow group members to your repository. You are to "share" repositories. As an alternative to forming a small group, you can create two repos of your GitHub repository as shown in the powerpoint.
- Copy exercise 9 from last week into your new repository and introduce an error in the exercise. Make it a real algorithm error, not just a syntax error. The hand-in for this exercise is your "bad" program.
- Now switch with the other person: Download his/hers repo, fix the error, push it back to the repo. The other person must accept the change on GitHub. The hand-in for this exercise is the fixed program.
- The input file scores.txt is a tab-separated file with an accession number in first column followed by 6 numbers (scores) between 0 and 1. You must find the accession numbers and scores (that means the entire line) of the 10 highest and 10 lowest "combined scores" (combined score is the metric for selection) and save the output in the file scoresextreme.txt.
The combined score is simply the 6 numbers added together. The order of the output must be from high to low. - Change exercise 2 in the following way: There is an input file, negative_list.txt, which is a list of genes which can NOT be part of the output. They are banned from your analysis. As can be seen, the genes are identified by their swissprot id. In order to translate from swissprot id to accession number so you can relate it to the scores.txt, you must use the input file translation.txt, where the first item on the line is a accession number, second item is the corresponding swissprot id.