> From: carandraug+...@gmail.com
> Date: Tue, 2 Oct 2012 11:42:25 +0200
> Subject: Re: [OctDev] Analyze75
> To: adamaitkenh...@hotmail.com
> CC: octave-dev@lists.sourceforge.net
>
> On 2 October 2012 11:11, adam aitkenhead wrote:
> >> From: carandraug+...@gmail.
> From: carandraug+...@gmail.com
> Date: Tue, 2 Oct 2012 09:33:17 +0200
> Subject: Re: [OctDev] Analyze75
> To: adamaitkenh...@hotmail.com
> CC: octave-dev@lists.sourceforge.net
>
> On 1 October 2012 22:30, adam aitkenhead wrote:
> > I've just submitted analyze75
Hi Carnë,
I've just submitted analyze75write.m to SVN.
Adam --
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamic
> Date: Mon, 1 Oct 2012 13:01:36 +0100
> Subject: Re: [OctDev] DICOM package installation problem
> From: andybuc...@gmail.com
> To: adamaitkenh...@hotmail.com
> CC: octave-dev@lists.sourceforge.net
>
> On 1 October 2012 12:51, adam aitkenhead wrote:
> > Hi,
>
Hi,
I've been having trouble installing the DICOM toolbox, which fails with the
following error message:
octave:2> pkg install dicom-0.1.1.tar.gz
/usr/bin/ld: /usr/local/lib/libgdcmDSED.a(gdcmReader.cxx.o): relocation
R_X86_64_32 against `a local symbol' can not be used when making a shared
> From: carandraug+...@gmail.com
> Date: Wed, 26 Sep 2012 12:10:06 +0200
> Subject: Re: [OctDev] Dicom package / isdicom function: Carnë, please read
> To: adamaitkenh...@hotmail.com
> CC: andybuc...@gmail.com; octave-...@lists.sf.net
>
> On 26 September 2012 11:18, adam
Draug wrote:
> > On 25 September 2012 21:23, Andy Buckle wrote:
> >> On 19 September 2012 17:26, adam aitkenhead
> >> wrote:
> >>>
> >>> Hi Andy,
> >>>
> >>> I've attached an updated version of the isdicom function w
> From: carandraug+...@gmail.com
> Date: Tue, 25 Sep 2012 19:34:15 +0200
> Subject: Re: [OctDev] Analyze75
> To: adamaitkenh...@hotmail.com
> CC: octave-dev@lists.sourceforge.net
>
> hey, please avoid top posting. Reply at the bottom
>
> On 25 September 2012 17:07
All sounds good to me. Makes sense to keep to the standard way of doing things
to make it behave as others might expect. I'm not all that familiar with the
standard (yet), so if you see any ways to standardise it that is great.
About the input checks - I'd aimed to make it behave as Matlab do
lyze75
> To: adamaitkenh...@hotmail.com
> CC: octave-dev@lists.sourceforge.net
>
> On 25 September 2012 11:17, adam aitkenhead
> wrote:
> > Hi Carnë,
> >
> > Attached are those m files for analyze75info and analyze75read - I've
> > reformatted them to
24 Sep 2012 10:40:17 +0200
> Subject: Re: [OctDev] Dicom package / isdicom function
> To: adamaitkenh...@hotmail.com
> CC: octave-dev@lists.sourceforge.net
>
> On 21 September 2012 16:10, adam aitkenhead
> wrote:
> >> From: carandraug+...@gmail.com
> >> Date: Fri, 2
, 21 Sep 2012 13:53:56 +0200
> Subject: Re: [OctDev] Dicom package / isdicom function
> To: adamaitkenh...@hotmail.com
> CC: andybuc...@gmail.com; octave-dev@lists.sourceforge.net
>
> On 21 September 2012 10:18, adam aitkenhead
> wrote:
> > The underlying read function ha
ave 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 Septe
Hi,
I've written isdicom (as an .m file), a function which is currently missing
from the Dicom package. If it's likely to be useful then I'm happy to submit
it to Octave-forge (is there a different mailing list for Octave-forge?), or I
could forward the code to the maintainer of the pa
14 matches
Mail list logo
