706
edits
Dahlquist:TRACE Documentation: Difference between revisions
From OpenWetWare
Jump to navigationJump to search
→5. Implementation Verification: Quick outline of what I hope to elaborate on after I meet with Eddie
(added link to GRNmap) |
(→5. Implementation Verification: Quick outline of what I hope to elaborate on after I meet with Eddie) |
||
| Line 104: | Line 104: | ||
=== Details === | === Details === | ||
<b>Testing of GRNmap</b> | |||
GRNmap is tested by both its coders and the lab’s data analyst users. The coding team tries to break the code with various tasks in order to increase its functionality. The data analysts run their generated GRNs through the code and analyze the outputs. When running the code whether through the executable or MATLAB and errors appear, the data analyst notifies the coding team of the specific bugs and where they lie within the code. For example, when running a few networks in June 2015, an issue appeared on the screen. After tracing the issue back to the specific line, the code had a problem with reading a sheet in the Excel file. Some genes were missing data at duplicate time points, leaving some cells without a value. As a result of this error, the coding team now works to re-write the code to be able to handle missing data values. | |||
For implementing the model & ensuring it’s been thoroughly tested, talk to GRNmap coding team or have them write this portion of this section | |||
<b>GRNmap Results</b> | |||
<b>Software Design and Documentation</b> | |||
Documentation and design provide necessary usability tools & to facilitate future installation, modification, and maintenance | |||
#*Design (help of Eddie) | |||
#*Open Source Code on GitHub & allows you to track changes of versions of code | |||
#*Executable & MATLAB | |||
== 6. Model Output Verification == | == 6. Model Output Verification == | ||
