[Ctk-developers] Fwd: 9th CTK Hackfest summary

Thu May 15 10:59:27 EDT 2014

Thanks, Steve. That makes a lot of sense.
Ultimately, it would good to have a pure js solution, but of course this
mean a lot of work :)

Aaron

On Thu, May 15, 2014 at 7:34 AM, Steve Pieper <pieper at isomics.com> wrote:

> Hi Yves, Aaron -
>
> Thanks for the links!  We spent some time at the hackfest discussing and
> thinking about the various approaches and definitely considered and were
> motivated by the current ongoing projects like Cornerstone and dwv.
>  Excellent work and it would great to collaborate.
>
> Speaking for myself, and specifically about the DICOM object management, I
> agree that a natively-written javascript version could be cleaner and more
> efficient than cross-compiled C++.  But given that DICOM is exceptionally
> complicated and infamous for non-conformant data 'in the wild', it may be a
> while before new software can be written that has been battle hardened to
> the extent of DCMTK.  Correct me if I'm wrong, but when you start to look
> at things like RT, SR, and a host of other aspects of the standard I think
> there's a lot of work to be done before Cornerstone or dwv have parity with
> DCMTK.
>
> So one way to look at things is that dcmjs is a transitional tool, that
> allows Cornerstone and dwv to reap the benefits of decades of DCMTK
> development without starting from scratch -- for example, you might use it
> only as a fallback option on tricky cases.
>
> Another way to look at it is that new developments can easily be deployed
> in multiple scenarios.  For example, there's new work adding high-level
> segmentation object support to DCMTK in C++.  Now with emscripten, the same
> source code can be used either for heavy duty batch processing on a cluster
> or for a lightweight viewer on a phone.  This should significantly improve
> the maintainability since you only need one code base for both scenarios.
>
> Also we were really happy at how relatively easy it was to take C/C++
> projects and compile them for asm.js.  If you look at the emscripten
> project, a real value appears to be there are tricky codebases like zlib,
> pgp, png that are available for use from javascript without a tedious and
> error-prone porting exercise.
>
> With dcmjs we can focus on the fun parts of web based medical imaging
> software and let DCMTK handle the trickiest parts of DICOM.
>
> -Steve
>
>
> On Thu, May 15, 2014 at 4:20 AM, Yves Martelli <yves.martelli at gmail.com>wrote:
>
>> dcmjs looks very interesting!
>> If you haven't had enough js, you can have a look at
>> https://github.com/ivmartel/dwv...
>> Best
>>
>>
>> On 15 May 2014 04:16, Aaron Boxer <boxerab at gmail.com> wrote:
>>
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Aaron Boxer <boxerab at gmail.com>
>>> Date: Wed, May 14, 2014 at 10:16 PM
>>> Subject: Re: [Ctk-developers] 9th CTK Hackfest summary
>>> To: Jean-Christophe Fillion-Robin <jchris.fillionr at kitware.com>
>>>
>>>
>>> Regarding web access to DICOM images, you folks might be interested in
>>> the new Cornerstone open source project:
>>>
>>> https://github.com/chafey/cornerstone
>>>
>>> A nice demo can be found here:
>>>
>>> http://chafey.github.io/cornerstoneDemo/
>>>
>>> Currently the demo only pulls canned DICOM images and displays them, but
>>> it will shortly handle query/retrieve (via QIDO)
>>> storage (via STOW), and local file viewing.
>>>
>>>
>>> There is also a DICOM parser:
>>>
>>> https://github.com/chafey/dicomParser
>>>
>>> with examples here:
>>>
>>> https://rawgit.com/chafey/dicomParser/master/examples/index.html
>>>
>>>
>>> Note that these are pure html/js libraries.
>>>
>>>
>>> Cheers,
>>> Aaron
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wed, May 14, 2014 at 3:50 PM, Jean-Christophe Fillion-Robin <
>>> jchris.fillionr at kitware.com> wrote:
>>>
>>>> Hi CTK community,
>>>>
>>>> Few days ago, we were all at work in St Louis attending the 9th CTK
>>>> hackfest hosted by Lawrence Tarbox and Dan Marcus from Mallinckrodt
>>>> Institute of Radiology of the Washington University in St. Louis School of
>>>> Medicine.
>>>>
>>>> You can read more about this great week here:
>>>>
>>>>        http://www.kitware.com/blog/home/post/676
>>>>
>>>>
>>>>
>>>> The content of the post (without hyperlinks) is also copied below:
>>>>
>>>>
>>>> 8<-------8<-------8<-------8<-------8<-------8<-------8<-------8<-------8<-------
>>>>
>>>> Hosted by Lawrence Tarbox and Dan Marcus from Mallinckrodt Institute of
>>>> Radiology of the Washington University in St. Louis School of Medicine, the
>>>> 9th CTK hackfest was again a great success !
>>>>
>>>> During the week, the group of international and enthusiastic hackers
>>>> addressed a large number of topics including DICOM support, CLIs, XNAT and
>>>> also the CTK build and testing infrastructure.
>>>>
>>>> --==[ DICOM ]==-
>>>>
>>>> dcmjs.org - We created dcmjs - A javascript cross-compilation of dcmtk
>>>> that can be re-used in a HTML5 compliant browser. It allows the analysis
>>>> and the process of DICOM images directly within the browser. Two demos have
>>>> been crafted: (1) dcmjs dump to “View the header of a dicom file” and (2)
>>>> dcmjs view to "View the pixel data of a dicom file”
>>>>
>>>>
>>>> WG27 - DICOM and Web technology - We discussed with Lawrence Tarbox
>>>> about the possible direction to consider regarding the support of web
>>>> technology in DICOM. Some notes and links have been reported here:
>>>> http://www.commontk.org/index.php/CTK_DICOM_Web_Services
>>>>
>>>>
>>>> CTK DICOM widgets have been improved to better support the Quantitative
>>>> Image Informatics for Cancer Research project (QIICR). Details list of
>>>> improvements is reported here:
>>>> https://github.com/QIICR/ProjectIssuesAndWiki/wiki/Slicer-Infrastructure-Projects
>>>>
>>>>
>>>> --==[ CLIs ]==-
>>>>
>>>> MedInria integration - In order to fully leverage the CLI framework,
>>>> CTK has been integrated into the MedInria build system. The CLI plugin was
>>>> also updated to the latest version of the medInria internal APIs, and
>>>> preliminary work was done to integrate the CLI framework more natively into
>>>> the medInria architecture. Checkout the list of frameworks that already
>>>> integrated the CLI mechanism:
>>>> http://www.commontk.org/index.php/CLI_In_Context.
>>>>
>>>> SlicerChronicle - A Slicer module that communicates with Chronicle has
>>>> been prototyped. Chronicle is a scalable, distributed, standards-based
>>>> database to support detailed descriptions of patient state and treatment
>>>> scenarios in support of multi-system modelling. See
>>>> https://github.com/pieper/SlicerChronicle
>>>>
>>>> --==[ XNAT ]==-
>>>>
>>>> CTK XNAT support has been extended and improved to fully leverage
>>>> qRestAPI library capabilities. qRestAPI is simple Qt library allowing to
>>>> synchronously or asynchronously query a REST server. Improvements include
>>>> support for addition of new subjects, folders and data, as well as saving
>>>> changed objects back to the XNAT server. Further, access to assessments,
>>>> reports and forms was improved/added.
>>>>
>>>>
>>>> --==[ CTK infrastructure ]==-
>>>>
>>>> Qt5 support - User pull requests updating both CTK and PythonQt have
>>>> been consolidated and reviewed. In the coming weeks, corresponding work
>>>> will be finalized and integrated into CTK.
>>>>
>>>> Back to “regular” CDash layout - When establishing the CTK
>>>> infrastructure, we initially chose to “hijack” the capabilities of CDash to
>>>> support subprojects to display build and test results of CTK internal
>>>> libraries as subprojects. While the initial idea was ambitious, it
>>>> complexified the underlying infrastructure and make the review of
>>>> submissions more difficult. We decided to revert to a more traditional
>>>> layout and present result on a single consolidated page.
>>>>
>>>> TravisCI - Work has been done to leverage the continuous integration
>>>> platform TravisCI, when integrated. Every integration to CTK master branch
>>>> will trigger a build and associated build and testing results will be
>>>> uploaded to CDash.
>>>>
>>>> CTK Debian package - We continue our effort to provide CTK packages on
>>>> Debian based linux distribution. Details reported here:
>>>> http://www.commontk.org/index.php/Debian_Packaging
>>>>
>>>> Bug tracker - We reviewed the long standing issues and closed the one
>>>> which were not relevant any more.
>>>>
>>>> This post was collaboratively edited and reviewed by the CTK hackers.
>>>>
>>>> 8<-------8<-------8<-------8<-------8<-------8<-------8<-------8<-------8<-------
>>>>
>>>> --
>>>> +1 919 869 8849
>>>>
>>>> _______________________________________________
>>>> Ctk-developers mailing list
>>>> Ctk-developers at commontk.org
>>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Ctk-developers mailing list
>>> Ctk-developers at commontk.org
>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>>
>>>
>>
>> _______________________________________________
>> Ctk-developers mailing list
>> Ctk-developers at commontk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>
>>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20140515/c0120f28/attachment-0002.html>