Monthly Status Report

clutteredreverandΔιαχείριση Δεδομένων

31 Οκτ 2013 (πριν από 3 χρόνια και 9 μήνες)

268 εμφανίσεις

SAIC
-
Frederick

Version
1 as of 9/29/2010











Washington University in St. Louis



Monthly Status Report



XIP

/AVT


Maintenance and Support

29XS149ST



9
/2012








Lawrence Tarbox, Ph.D.

tarboxl@mir.wustl.edu


9

Octo
ber

2012


Monthly Status Report

XIP/AVT Maintenance and Support 9
/
2012

2


Project Background/Objectives


Provide operations and maintenance support for the XIP


and AVT


software
packages
, with targeted enhancements as directed.


Personnel Roster


Name

Title/Role

Lawrence Tarbox

Project Lead

Jarek Krych

Developer




Contract

Overview


XIP uses a combination of
Java (for portability) and c++ (for speed and access to the
full functionality of the c++ based ITK, VTK, and OpenGL technologies) as its basis. It
leverages the AIM, IVI Middleware, NBIA, and other caBIG® pro
jects, as well as
multiple external projects (e.g.

ITK, VTK, OpenGL, Open Inventor, OpenHealthTools,
dcm4che, dcmtk, PixelMed, IBM DB2 Express
-
C) and external standards (Web
Services, IHE, HL7, DICOM, and in parti
cular DICOM Application Hosting)

to provide

a
framework for creating and running imaging applications.


AVT is build upon the XIP framework, and leverages the R statistical package to provide
statistical analysis tools for comparing image post
-
processing algorithms.


Current
Project

Status


In September we began a concentrated push to incorporate AIM 3.0 into XIP and AVT. In particular, we
are focusing on MVT, since there is much external interest in the MVT program.



Jarek
briefly continued to

explore the use of asynchronous web services as part of revamping and
updating the Application Hosting interfaces. The asynchronous mode of web services potentially would
simplify programming and perhaps offer better performance since it fits better with

the programming
model used in the XIP Host™. The question is whether or not the asynchronous and synchronous modes
work with each other, i.e., can an asynchronous host work with a synchronous application and visa versa.


We revised the build and packagin
g scripts (from the AVT project) to incorporate the new XIP Host™, and
to simplify installation by including all 3
rd

party libraries, with the exception of the IBM DB2 Express C
database. The license for the database seems to disallow distribution in the
XIP packaging. Since it is
optional (only needed for AVT), we do not feel that this is a major roadblock to installer simplification, but
we hope to investigate ways to automate the download and install of DB2, or at least to insert the links
and instruct
ions on the installer screens.


In testing the build package, we came across potential problems for those who previously might have
installed, then uninstalled the AD database
. We will incorporate warnings in the install instructions, with a
description

of how to resolve the problem
.


Monthly Status Report

XIP/AVT Maintenance and Support 9
/
2012

3


Though not part of the XIP/AVT project, we
completed in September a pilot (more just a simplified proof
of concept) showing how to
t
ie

XNAT to an NBIA repository, and importing AIM annotation in a
searchable form into XNAT.


In September

our work will
continue to

focus on:


1.

Continuing
the changes needed to more completely support the final DICOM Application Hosting
API specification (minus Abstract Image Models).

2.

Incorporating AIM 3.0 into AVT and XIP. (AIM 4.0 is not yet r
eady.)

3.

Prototyping the use of 3D slicer as a tool for creating AIM objects for AVT. We are coordinating
with the community who are adding AIM capabilities to 3D Slicer.

4.

Building up AVT use cases, drawing from the QIN experiences.

5.

Revamping XIP documentati
on


Description of Work Completed During the Month


External Meetings

(Summarize for Frequent Communications)


Date

Topic

Project Attendees (Optional)

Every other
Tuesday


(
5, 19 September
)

XIP/AVT Status Meeting

Lawrence Tarbox, Ulrike
Wagner,
Jonathan
Lin

13

September

Monthly QI
-
bench meeting

Lawrence Tarbox, Andrew
Buckler, several others

18 September

Pre
-
discussion, Interconnectivity

All IMAG project leads, CIP, NCI,
SAIC
-
F COTR

20 September

Staffing for XIP

Lawrence Tarbox, Bruce Vendt,

External
staffing agency

24 September

CBIIT Imaging Suite Interconnectivity Meeting

All IMAG project leads, CIP, NCI,
SAIC
-
F COTR

24 Sept

XIP/AVT/Middleware Planning

Lawrence Tarbox,

Ashish Sharma

26

September

XIP Documentation Project

Rachel Shortt

26
September

XIP/AVT/AIM planning

Lawrence Tarbox,

Pat M
ongkolwat




Monthly Status Report

XIP/AVT Maintenance and Support 9
/
2012

4



Project

Progress


Activity

Description

Increment 13

Revamp AIM libraries with the 3.0 model, and
begin adapting MVT to use AIM 3.0
.

Investigations
into the asynchronous mode of web services in the
context of the Application Hosting interfaces.

Increment 12

Snapshot release package finished, and in test.

Community outreach

Continued discussions on

the use of AVT
,
particularly MVT,

i
n the QI
-
Bench project.

Discussions on the use of AVT/XIP technology in
XNAT.

Discussions on the use of AVT/XIP technology in
CIP’s QIN and TCIA programs

Continued discussions on

the use of Application
eosting in feE most mrocessing torkflow.

Continued dis
cussions on afClj teb pervicesI
and how they might be used in the research world.

hnowledge Center

fn the absence of a knowledge centerI we will be

monitoring hC resources (e.g. corumsI gfoA) for
questions and support issues.


Monthly Status Report

XIP/AVT Maintenance and Support 9
/
2012

5


Status of
Milestones


Mileston
e

Delivery Date

Status

Project Management Plan

20 days following
project kickoff

MS Project plan sent
by e
-
mail to COTR

Monthly Status Report

10
th

of each month

This is the
twelve

monthly report

Project Summary Report

No later than 30 days
before project
completion

Not started

XIP Maintenance Support

No later than 30 days
before contract ends

Ongoing

AVT Maintenance Support

No later than 30 days
before contract ends

Ongoing

Software Code Base

No later that 10 days
after completion of
each

development
iteration

Code checked into the
XIP code repository
continuously during
the development
process

Software Issues Tracking

Updated as required

JIRA updated with
currently known issues
and in use for project
tracking

Upgrade XIP and AVT to work

with caGRID 1.4
, and
incorporating STS

90 days after the
contract is awarded or
60 after IVI middleware
and NBIA access
libraries with
appropriate test sites,
with caGRID 1.4
access incorporated,
are available to the
XIP/AVT team for
integration, whicheve
r
is later

Continued

discussions
with Emory

and the
NBIA team
.
No
access libraries
incorporating
caGrid
1.4 expected
for
Middleware or NBIA
until
summer

or early
fall
.

Have incorporated
STS into the XIP
Host™ login
procedures as an
option.

Asq and ufm
release packages including both major
and minor releases

oefer to the mroject
mlan

torking on

package
incorporating bug fixes
from feE
I NBfA 5.0
access.

‘S
napsh
ot’
development release

built and packagedI in
test
.

Asq rse Cases for the nfN mrogram

No later

than N5 days
before the contract end

aiscussions startedI
information gathering
in play.


Monthly Status Report

XIP/AVT Maintenance and Support 9
/
2012

6



Work Planned for Next Month


Activity

Description

Update documentation

Further updates to user guides and developer
documentation to reflect the current state of
the
code (ongoing).

Update DICOM Application Hosting support

Move from the Frozen Draft API specification to the
Final Text specification, complete work started,
then stopped, in a previous XIP contract.

Update XIP/AVT with AIM 3.0

Continue

the process,
which will run into
subsequent months, starting with MVT.

Additional code cleanup in XIP Host

Minor code clean up continuing.

Continuing improvements to Mac compatibility

Continued testing and improving MAC
compatibility.

3D Slicer annotation tool

Stay in contact with the
3D Slicer
team who are
adding to 3D slicer the capability to
generat
e

AIM
annotations for use in AVT.

AVT Use Cases

Continue

gathering

further information for
generating new AVT use cases
, and for refreshing
the existing ones
.

In part i cul ar, begi n shadowi ng a
speci fi c QIN proj ect as part of t he i nformat i on
gat heri ng.

Devel opment Snapshot Rel ease

Snapshot rel ease bei ng post ed aft er some
addi t i onal t est i ng
.



Travel

Planned for Next Month


Attendees (name)

Travel Purpose

Descri pti on

(i ncl ude ci ty)







Monthly Status Report

XIP/AVT Maintenance and Support 9
/
2012

7



Issue Man
a
gement



ID

Description

Owner

Actions

Priority

Status
(Open,
Closed)














See JIRA

online


Risk Management


ID

Description

Owner

Potential Impact

Priority
(H, M, L)

Status
(Open,
Closed)

1

Needed

AIM model
and test AIME data
service not available

Tarbox

Project delay

L

Open

2

Needed test site for
caGRID 1.4
DICOM
PACS Data Service
not
available

Tarbox

Project delay

L

Open

3

Needed IVI Middleware
Libraries for caGRID
1.4 not available

Tarbox

Project delay

L

Open

4

Needed NBIA test site
and access libraries for
caGRID 1.4 not
available

Tarbox

Project delay

H

Open

5

Development
resources (people) not
sufficient to finish
project

Tarbox

Project not completed

M

Open

Track risks from
month
-
to
-
month.

Take off the
closed

risks after they’ve been closed
for one reporting period.


External Dependencies


Dependency

Date

Status

Comments

AIM Model

December 20, 2011

Have AIM 3.0

AIM 4.0
Model in
discussion

IVI Middleware

for
caGRID 1.4

December 20, 2011

TBD

Development not
completed

NBIA for caGRID 1.4

December 20, 2011

TBD

No development team

ISS for caGRID 1.4

December 20, 2011

Running in VM

First release received

May 8, 2012

STS on production grid
running, incorporated
into XIP


Monthly Status Report

XIP/AVT Maintenance and Support 9
/
2012


SAIC
-
Frederick

Version
1 as of 9/29/2010


Status of Deliverables


Notes:



All deliverables need to be deposited to SAIC
-
Frederick gForge site assigned by COTR


{insert link here}



Include the release cycle and iteration for all of the Contract Deliverable

in a row by itself.


Contract
Deliverable
Number

Contract
Deliverable
Name

Project
Artifact Name

Wo
r
king

Copy
Link

Final
, Published

Copy

Link

Due Date

Date
Delivered

Status


COTR Comments

Release 1,
Iteration 3









10
-
ST1011
-
D03

Project
Summary
Report

Project
Summary
Report





August 31,
2012






10
-
ST1011
-
D04

Design Review
Package

Service
Integration





{date}




Plan to carry this artifact
development for this service into
next iteration.






10
-
ST1011
-
D12

508 Compliance
Package

508
Compliance
Package





{date}






Release 1,
Iteration 4









10
-
ST1011
-
D03

Project
Summary
Report

Project
Summary
Report





August 31,
2012






10
-
ST1011
-
D04

Design Review
Package

Service
Integration





{date}




Plan to carry this artifact
development for this service into
next iteration.






10
-
ST1011
-
D12

508 Compliance
Package

508
Compliance
Package





{date}







For the first month, include all deliverables for the entire project. For subsequent months, update as necessary and
highlight any changes from the previous month. Add rows as
needed.

Monthly Status Report

XIP/AVT Maintenance and Support 9
/
2012


SAIC
-
Frederick

Version
1 as of 9/29/2010