Difference between revisions of "2013 Project Week:QualityAssuranceModule"

From NAMIC Wiki
Jump to: navigation, search
m
(→‎Project Description: Update of project week status)
Line 27: Line 27:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Approach, Plan</h3>
 
<h3>Approach, Plan</h3>
* Implement a test database on the fly
+
* Implement a test database on-the-fly
 
* Expand test code coverage (doctests, unittests via nose)
 
* Expand test code coverage (doctests, unittests via nose)
 
* Add logging
 
* Add logging
Line 37: Line 37:
 
<h3>Progress</h3>
 
<h3>Progress</h3>
 
* This is a continuation of [[2012_Summer_Project_Week:Evaluation_Module]]
 
* This is a continuation of [[2012_Summer_Project_Week:Evaluation_Module]]
 +
 +
==== Database interface ====
 +
* Implemented in-memory testing database on-the-fly (SQLite)
 +
* Added extensive testing and logging
 +
* Supports <em>both</em> Postgres and SQLite
 +
* Refactored to support all three existing modules
 +
* Implemented file-based configuration for customization
 +
 +
==== GUI ====
 +
* (in progress) GUI construction via configuration file
 +
 +
==== MRML ====
 +
* (in progress) code refactoring for generalization
 +
* (in progress) GUI-MRML coupling via configuration file
 +
 +
==== Additional ====
 +
* Improved Python structure and packaging
 +
* (in progress) Improved documentation of module
 
</div>
 
</div>
 
</div>
 
</div>

Revision as of 15:36, 11 January 2013

Home < 2013 Project Week:QualityAssuranceModule

Key Investigators

  • Dave Welch, UIowa SENAP
  • Hans Johnson, UIowa SENAP

Project Description

Objective

  • We have created several Python-based image quality assurance modules for use by research technicians in our lab. Our goals with this project are:
  1. Refactoring to enable more flexible extension of the modules
  2. Implementation of several user requests, such as hotkeys
  3. Improved interaction with our database for increased robustness
  4. Expanded testing and logging
  5. Documentation and examples on Slicer Wiki

Approach, Plan

  • Implement a test database on-the-fly
  • Expand test code coverage (doctests, unittests via nose)
  • Add logging
  • Decouple module code from DB interaction
  • Refactor and consolidate code from our three modules
  • Improve GUI and MRML interactions

Progress

Database interface

  • Implemented in-memory testing database on-the-fly (SQLite)
  • Added extensive testing and logging
  • Supports both Postgres and SQLite
  • Refactored to support all three existing modules
  • Implemented file-based configuration for customization

GUI

  • (in progress) GUI construction via configuration file

MRML

  • (in progress) code refactoring for generalization
  • (in progress) GUI-MRML coupling via configuration file

Additional

  • Improved Python structure and packaging
  • (in progress) Improved documentation of module