Learning about commenting code changes to avoid confusion when working in a group sounds like something along the lines of common sense. No one can agree what constitutes common sense so this week, in addition to learning more about the hardware setup, involved reading the user’s manual to the version control software used to manage the version control on our code. The best part of this software, Subversion, is that it requires any user committing a change to the master code must comment what they did e.g. “function foo has been entirely gutted and reworked” to be tagged with the version number. Thanks CREU for giving me something new to put on my resume.
Looking over the state of our hardware being used for testing involved the decision to save headaches now or later on in the research. Naturally we opted to save headaches now rather than down the line by committing to changes in the operating system setup. Instead of remaining with an older flavor of Linux, Fedora, we’re changing to a newer flavor, Ubuntu to better utilize a program that will give us access to more detailed information about the CPU.
No comments:
Post a Comment