NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Excerpt

LIDC Conversion to AIM Meeting Notes

Month

1st Week

2nd Week

3rd Week

4th Week

5th Week

April

 

 

04-14

04-21

04-28

May

05-05

 

 

 

 

June

 

 

 

 

 

July

 

 

 

 

 

Month

1st Week

2nd Week

3rd Week

4th Week

5th Week

January

 

 

 

 

 

February

02-03


02-17

02-24

 

March

03-05

03-12

 

 

 

April

04-02


04-16


 

May


05-14


05-28

 

June

 

06-11

06-18

06-23

 

July

 

 




August

 

 


 

 

September

 

 



 

February 3, 2009

Participants: John Freymann, Justin Kirby, Qinyan Pan, Pat Mongolowat

Pat: 

AIM Schema Generation:

First we curate UML in Enterprise Architect.

Generate xmi file

use caCORE 3.2.1 to generate XML schema for AIM

Then modify it by hand

Separately, we use EA to generate some C++ library (non-platform-specific), manually modify

THis C++ is a representation of an AIM object 

use this code to generate DICOM SR, AIM XML documents

for each attribute we have a method, we have a set/get.

 Tony does not use the C++ library.  He uses the AIM Schema directly.

AIM Schema has two types:

1)Bi-directional Schema  (file name ends with "model")

This is a superset of uni-directional

For example, when you translate these UML diagrams to an XML, you would be able to create an AIM object.  User, equipment can be root.

Why? Because it supports more queries such as "Get the total number of RECIST markups that Reader One generated"

This was requested by Baris Susek (the mentor)

2) Uni-directional Schema

only "image annotation" and "annotation annotation" are roots.

The reason this one is still supported to generate AIM XML document