ITK Release 4/SimpleITK/Tcon 2012 2 15: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
Line 44: Line 44:
* working on fixing the automatic testing for R
* working on fixing the automatic testing for R
* Richard Beare is hacking away he is reporting the following:
* Richard Beare is hacking away he is reporting the following:
  I'm thinking about import options based on my old R imaging package.
  I'm thinking about import options based on my old R imaging package.
  Images were also represented by a pointer to a C object (external
  Images were also represented by a pointer to a C object (external
Line 49: Line 50:
  the image as an array for purposes of subsetting. This meant that you
  the image as an array for purposes of subsetting. This meant that you
  could do something like this:
  could do something like this:
 
  im2 <- im1[100:200,]  # im2 is another image, not an array, with all
  im2 <- im1[100:200,]  # im2 is another image, not an array, with all
  the columns and rows 100 to 200
  the columns and rows 100 to 200

Revision as of 13:57, 15 February 2012

Tcon Information

NEW Phone Line: 

  Please join the following teleconference line:
      Toll-Free #:      1-888-677-0429
      Participant Code: 96280

  Wednesday, February 8th, 9:30am Eastern Time

Attendees

  • Bradly Lowekamp
  • Dan Blezek

Links

Release 0.4.0

  • Currently 53 binary downloads
  • Topics to be merged into release?
    • SIMPLEITK-239_AddingSetupForDevelopment
    • SIMPLEITK-245_ImageJ64ForMac??

Priorities for next release

  • Registration
  • C++ installation
  • Splitting BasicFilters Library
  • improved vector image support

R Wrapping Follow-up

  • working on fixing the automatic testing for R
  • Richard Beare is hacking away he is reporting the following:
I'm thinking about import options based on my old R imaging package.
Images were also represented by a pointer to a C object (external
reference). By providing the right generic operators we could treat
the image as an array for purposes of subsetting. This meant that you
could do something like this:

im2 <- im1[100:200,]  # im2 is another image, not an array, with all
the columns and rows 100 to 200

If we wanted an array version of an image we'd do
 
im2 <- as.array(im1)

as.array is a generic R operation that we specialised for images.

The SimpleITK bindings are already capable of doing:

pixval <- im1[c(100,200)]

so we're well on the way.

The other neat thing I'd like is operator overloading. R has
facilities for that, so that you should be able to write expressions
which treat images just like any other variable.1

Daily Details

  • The Stage Repository
          SIMPLEITK-221_Java_packaging | master=1 next=1
    SIMPLEITK-255_AddLabelVotingFilters | master=0 next=1
SIMPLEITK-239_AddingSetupForDevelopment | master=0 next=1
SIMPLEITK-224_AddVectorSupportGetBuffer | master=0 next=0
         SIMPLEITK-98_add_install_rules | master=0 next=0
      SIMPLEITK-241_DocumentationReview | master=0 next=1
   SIMPLEITK-211_AddingWatershedFilters | master=0 next=0


Outstanding Test Failures


Other Open Topics

  • Wiki and Doxygen pages should be review for release.
  • Adding support for import and export vector images to numpy
  • Registration
    • to be major new feature to work on in Febuary
  • C++ installation

Schedule

  • Discuss long term goals and milestones.
  • Documentations
  • Automate Script to List filters wrapped
    • This script should take as input a list of ITK Modules or Directories, for each modual determine which filters are implemented in SimpleITK
    • Additional input would include filter/files to exclude
    • Output could be a dox file, so that it could be a doxygen related page
  • Registration is very important

Action Items

Retrieved from "https://public.kitware.com/Wiki/index.php?title=ITK_Release_4/SimpleITK/Tcon_2012_2_15&oldid=46016"