![]() It is difficult to remember the differences between the versions of the files and, more importantly, which version you used to produce specific results, especially if you return to the code months later. However, this can quickly become a problem because it clutters your file system with uninformative filenames, e.g., analysis.sh, analysis_02.sh, analysis_03.sh, etc. One often-utilized solution is to make a copy of the script before making new edits. First, you often need to experiment with new ideas, such as adding new features to a script or increasing the speed of a slow step, but you do not want to risk breaking the currently working code. However, a few key problems can arise when iteratively developing code that make it difficult to document and track which code version was used to create each result. Just as experiments are logged in laboratory notebooks, it is important to document the code you use for analysis. Many scientists write code as part of their research. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |