Re: [OctDev] Dicom package / isdicom function

[Andy B. <and...@gm...>]

>> Date: Thu, 13 Sep 2012 14:57:29 +0100
>
>> Subject: Re: [OctDev] Dicom package / isdicom function
>> From: and...@gm...
>> To: ada...@ho...
>>
>> > I have access to Matlab too, and it recognises the non-standard DICOM
>> > file.
>> > (Just to note, although I have tested the ML behaviour for a some test
>> > files, I didn't use Matlab as a basis for the code.)
>>
>> Excellent. That is the way to do it. We are careful about copyright.
>>
>> Andy
On 19 September 2012 17:26, adam aitkenhead <ada...@ho...> wrote:
>
> Hi Andy,
>
> I've attached an updated version of the isdicom function which can now check
> a list of files (in a cell array) in one go, which is much quicker than
> checking each file separately.  Again, no rush for releasing a new version
> of the toolbox - just some changes I was making for my own code anyway.
>
> Also on a different note, I've written functions which read/write the
> Analyze format, giving functions equivalent to Matlab's analyze75info and
> analyze75read.  Would you rather keep the Dicom toolbox purely for the Dicom
> format, or are you interested in expanding it to become a general Medical
> File Format toolbox?  No worries if not, just thought I'd see what you
> thought before I see where else they could fit into Octave-forge.
>
> Adam

Note that I have included the list for further discussion, and edited
older text to chronological order.

I have not used analyze75. If it is just m-files, then the image
package is probably a good place. The main reason dicom is on its own
is that it has burdensome dependencies.

-- 
/* andy buckle */