[MINC-users] [Fwd: OHBM Announcement 3/9/04]

Jon Erik Ween minc-users@bic.mni.mcgill.ca
Sun Mar 14 18:21:05 2004


--Apple-Mail-4--46315359
Content-Type: multipart/alternative;
	boundary=Apple-Mail-5--46315359


--Apple-Mail-5--46315359
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	delsp=yes;
	charset=ISO-8859-1;
	format=flowed

Great!

Jon

On Friday, March 12, 2004, at 07:24 PM, Scskiwiz@aol.com wrote:

> Jon and Yasser:
> =A0
> The DFWG committee is very aware of the latest MINC developments =20
> through Colin Holmes' able and enthusiastic advocacy of MINC to the =20=

> committee. In addition, we have been provided with MINC 1.0 namespace =20=

> (7/5/2003) and MINC 2.0 file format (11/18/2003) documents by Robert =20=

> Vincent in Montreal. Most of the DFWG committee meet with Alan Evans, =20=

> John Sled, Robert Vincent and several others to discuss MINC and its =20=

> proposed developments at the last OHBM meeting in NewYork.
> =A0
> I will discuss lines of communication between the DFWG and MINC =20
> development community with Alan Evans and Colin Holmes. It=A0is my =20
> current impression that information is flowing freely, particularly =20=

> from the MINC community to the committee.
> =A0
> Stephen Strother
> =A0
> In a message dated 3/11/2004 7:20:23 PM Central Standard Time, =20
> jween@som.llu.edu writes:
>
> I would be in favor of the Minc format as a rich, compact and elegant
> standard. I wonder, though, how significant the issue is as long as =
all
> formats are transparent, non-proprietary and translatable? Knowing the
> community, I can't imagine there will be 100% agreement any time soon
> no matter what happens with the Analyze format. I would only hope that
> the capable minc-group is actively included in the development of a
> more widely adopted, uniform standard. I notice they are not mentioned
> in the statement!
>
> Jon
>
> Jon Erik Ween, MD, MS
> Assistant Professor
> Cognitive and Cerebrovascular Neurology
> Director, Stroke Program
> Loma Linda University
>
>
>
<image.tiff>
>
>
> On Wednesday, March 10, 2004, at 03:30 PM, Yasser Ad-Dab'bagh wrote:
>
> >
> > Should we be concerned?
> >
> > Yasser
> >
> > -----Forwarded Message-----
> > From: Organization for Human Brain Mapping =20
> <info@humanbrainmapping.org>
> > To: yasser.ad-dabbagh@MAIL.MCGILL.CA
> > Subject: OHBM Announcement 3/9/04
> > Date: 09 Mar 2004 15:43:11 -0700
> >
> >
> >
> > Dear OHBM Colleagues:
> >
> > We are writing on behalf of the Data Format Working Group (DFWG), a
> > committee set up under the Neuroimaging Informatics Technology
> > Initiative (NIfTI, http://nifti.nimh.nih.gov), which is jointly
> > sponsored by NIMH and NINDS. We have been charged with arriving "at =
a
> > technical solution to the problem of multiple data formats in fMRI." =
=20
> We
> > have met several times and decided that one of our first priorities =20=

> is
> > to describe and attempt to merge the variants of the ANALYZE(TM) 7.5
> > image header that are being used by the developers of the major fMRI
> > data analysis packages.
> >
> > We have defined a compromise data format, dubbed NIfTI-1, that is =20=

> based
> > on these variants and is "mostly compatible" with the ANALYZE(TM) =
7.5
> > header, while using many of the "unused and lesser-used" fields for
> > fMRI-specific purposes. Developers of five of the major fMRI data
> > analysis packages (FSL, SPM, AFNI, BrainVoyager, and FreeSurfer) =
have
> > agreed to use this compromise format in the future, and will support
> > both input and output of the NIfTI-1 format. A considerable effort =20=

> was
> > required to reach agreement with all of these developers. Given the
> > extremely limited space in the 348 byte header, it is unlikely that =20=

> any
> > substantial changes will be possible in the NIfTI-1 format if we are =
=20
> to
> > retain the support of all five packages.
> >
> > We envisage NIfTI-1 replacing the current range of ANALYZE 7.5 =20
> variants
> > both for file interchange and data storage.=A0 NIfTI-1, while still
> > limited, contains a considerably richer set of metadata than exists =20=

> in
> > the ANALYZE-based formats.
> >
> > As of this message, the NIfTI-1 format specification, demonstration
> > programs, and related documents are being released to the general
> > neuroimaging community on the DFWG website
> > http://nifti.nimh.nih.gov/dfwg/ along with an interactive forum for
> > comments and discussion. The DFWG committee will next meet in early =20=

> May
> > 2004, and any comments you care to make and would like to have
> > considered at the next committee meeting should be received by =
April=A0
> > 15,
> > 2004.
> >
> > Please feel free to pass this message along to any other person you
> > think might be interested.=A0 Comments and questions should be =20
> directed=A0
> > to
> > the NIfTI-1 interactive forum, and not to DFWG committee members via
> > e-mail.=A0 The full list of DFWG committee members can be found at =
the
> > DFWG website.
> >
> > Stephen Strother, PhD
> > Chair, Data Format Working Group
> > NIfTI, National Institutes of Health
> >=A0 =A0 =A0 =A0 =A0 =A0 =A0 and
> > Professor of Radiology
> > University of Minnesota
> > mailto:steve@neurovia.umn.edu
> >
> >
> > Robert W. Cox, PhD
> > Director, Scientific and Statistical Computing Core
> > National Institute of Mental Health
> > National Institutes of Health
> > Department of Health and Human Service
> > Mailto: rwcox@nih.gov=A0=A0 http://nifti.nimh.nih.gov/dfwg/
> >
> >
> >
> >
> > To be removed from this mailing list, please click here.
> >
> > --=A0
> >=A0=A0
> > =20
> =
-----------------------------------------------------------------------
> >=A0 Yasser Ad-Dab'bagh, MD, DPM, FRCPC.
> >=A0 Divisions of Child & Adolescent Psychiatry (Montreal Children's
> >=A0 Hospital), and of Neuroscience (Brain-Imaging Center of the=A0 =20=

> Montreal
> >=A0 Neurological Institute), McGill University.
> >
> >=A0 Tel:=A0 =A0 =A0 =A0 (514) 412-4400 ext 22359 [MCH], (514) =
398-8330 [BIC]
> >=A0 Fax:=A0 =A0 =A0 =A0 (514) 412-4337 [MCH]
> >=A0 Pager:=A0 =A0 =A0 =A0 (514) 580-4388
> >=A0 E-mail:=A0 =A0 yaddab@bic.mni.mcgill.ca
> >=A0 =A0 =A0 =A0 =A0 yasser.ad-dabbagh@mail.mcgill.ca
> >=A0 =A0 =A0 =A0 =A0 yasser@doctoraddabbagh.com
> >=A0 Web:=A0 =A0 =A0 =A0 http://www.doctoraddabbagh.com
> >=A0=A0
> > =20
> =
-----------------------------------------------------------------------
> >
> > _______________________________________________
> > MINC-users@bic.mni.mcgill.ca
> > http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
> >
> >
>
>
>
Jon Erik Ween, MD, MS
Assistant Professor
Cognitive and Cerebrovascular Neurology
Director, Stroke Program
Loma Linda University


--Apple-Mail-5--46315359
Content-Transfer-Encoding: quoted-printable
Content-Type: text/enriched;
	charset=ISO-8859-1

Great!


Jon


On Friday, March 12, 2004, at 07:24 PM, Scskiwiz@aol.com wrote:


<excerpt>Jon and Yasser:

=A0

The DFWG committee is very aware of the latest MINC developments
through Colin Holmes' able and enthusiastic advocacy of MINC to the
committee. In addition, we have been provided with MINC 1.0 namespace
(7/5/2003) and MINC 2.0 file format (11/18/2003) documents by Robert
Vincent in Montreal. Most of the DFWG committee meet with Alan Evans,
John Sled, Robert Vincent and several others to discuss MINC and its
proposed developments at the last OHBM meeting in NewYork.

=A0

I will discuss lines of communication between the DFWG and MINC
development community with Alan Evans and Colin Holmes. It=A0is my
current impression that information is flowing freely, particularly
from the MINC community to the committee.

=A0

Stephen Strother

=A0

In a message dated 3/11/2004 7:20:23 PM Central Standard Time,
jween@som.llu.edu writes:


<fontfamily><param>Arial</param>I would be in favor of the Minc format
as a rich, compact and elegant

standard. I wonder, though, how significant the issue is as long as all

formats are transparent, non-proprietary and translatable? Knowing the

community, I can't imagine there will be 100% agreement any time soon

no matter what happens with the Analyze format. I would only hope that

the capable minc-group is actively included in the development of a

more widely adopted, uniform standard. I notice they are not mentioned

in the statement!


Jon


Jon Erik Ween, MD, MS

Assistant Professor

Cognitive and Cerebrovascular Neurology

Director, Stroke Program

Loma Linda University




</fontfamily></excerpt><fontfamily><param>Arial</param><<image.tiff>

<excerpt>


On Wednesday, March 10, 2004, at 03:30 PM, Yasser Ad-Dab'bagh wrote:


>

> Should we be concerned?

>

> Yasser

>

> -----Forwarded Message-----

> From: Organization for Human Brain Mapping
<<info@humanbrainmapping.org>

> To: yasser.ad-dabbagh@MAIL.MCGILL.CA

> Subject: OHBM Announcement 3/9/04

> Date: 09 Mar 2004 15:43:11 -0700

>

>

>

> Dear OHBM Colleagues:

>

> We are writing on behalf of the Data Format Working Group (DFWG), a

> committee set up under the Neuroimaging Informatics Technology

> Initiative (NIfTI, http://nifti.nimh.nih.gov), which is jointly

> sponsored by NIMH and NINDS. We have been charged with arriving "at a

> technical solution to the problem of multiple data formats in fMRI."
We

> have met several times and decided that one of our first priorities
is

> to describe and attempt to merge the variants of the ANALYZE(TM) 7.5

> image header that are being used by the developers of the major fMRI

> data analysis packages.

>

> We have defined a compromise data format, dubbed NIfTI-1, that is
based

> on these variants and is "mostly compatible" with the ANALYZE(TM) 7.5

> header, while using many of the "unused and lesser-used" fields for

> fMRI-specific purposes. Developers of five of the major fMRI data

> analysis packages (FSL, SPM, AFNI, BrainVoyager, and FreeSurfer) have

> agreed to use this compromise format in the future, and will support

> both input and output of the NIfTI-1 format. A considerable effort
was

> required to reach agreement with all of these developers. Given the

> extremely limited space in the 348 byte header, it is unlikely that
any

> substantial changes will be possible in the NIfTI-1 format if we are
to

> retain the support of all five packages.

>

> We envisage NIfTI-1 replacing the current range of ANALYZE 7.5
variants

> both for file interchange and data storage.=A0 NIfTI-1, while still

> limited, contains a considerably richer set of metadata than exists
in

> the ANALYZE-based formats.

>

> As of this message, the NIfTI-1 format specification, demonstration

> programs, and related documents are being released to the general

> neuroimaging community on the DFWG website

> http://nifti.nimh.nih.gov/dfwg/ along with an interactive forum for

> comments and discussion. The DFWG committee will next meet in early
May

> 2004, and any comments you care to make and would like to have

> considered at the next committee meeting should be received by April=A0

> 15,

> 2004.

>

> Please feel free to pass this message along to any other person you

> think might be interested.=A0 Comments and questions should be
directed=A0

> to

> the NIfTI-1 interactive forum, and not to DFWG committee members via

> e-mail.=A0 The full list of DFWG committee members can be found at the

> DFWG website.

>

> Stephen Strother, PhD

> Chair, Data Format Working Group

> NIfTI, National Institutes of Health

>=A0 =A0 =A0 =A0 =A0 =A0 =A0 and

> Professor of Radiology

> University of Minnesota

> mailto:steve@neurovia.umn.edu

>

>

> Robert W. Cox, PhD

> Director, Scientific and Statistical Computing Core

> National Institute of Mental Health

> National Institutes of Health

> Department of Health and Human Service

> Mailto: rwcox@nih.gov=A0=A0 http://nifti.nimh.nih.gov/dfwg/

>

>

>

>

> To be removed from this mailing list, please click here.

>

> --=A0

>=A0=A0

>
-----------------------------------------------------------------------

>=A0 Yasser Ad-Dab'bagh, MD, DPM, FRCPC.

>=A0 Divisions of Child & Adolescent Psychiatry (Montreal Children's

>=A0 Hospital), and of Neuroscience (Brain-Imaging Center of the=A0
Montreal

>=A0 Neurological Institute), McGill University.

>

>=A0 Tel:=A0 =A0 =A0 =A0 (514) 412-4400 ext 22359 [MCH], (514) 398-8330 =
[BIC]

>=A0 Fax:=A0 =A0 =A0 =A0 (514) 412-4337 [MCH]

>=A0 Pager:=A0 =A0 =A0 =A0 (514) 580-4388

>=A0 E-mail:=A0 =A0 yaddab@bic.mni.mcgill.ca

>=A0 =A0 =A0 =A0 =A0 yasser.ad-dabbagh@mail.mcgill.ca

>=A0 =A0 =A0 =A0 =A0 yasser@doctoraddabbagh.com

>=A0 Web:=A0 =A0 =A0 =A0 http://www.doctoraddabbagh.com

>=A0=A0

>
-----------------------------------------------------------------------

>

> _______________________________________________

> MINC-users@bic.mni.mcgill.ca

> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users

>

></excerpt></fontfamily><excerpt>




</excerpt>Jon Erik Ween, MD, MS

Assistant Professor

Cognitive and Cerebrovascular Neurology

Director, Stroke Program

Loma Linda University



--Apple-Mail-5--46315359--

--Apple-Mail-4--46315359
Content-Disposition: inline;
	filename=ADIlogoFinalSmall.jpg
Content-Transfer-Encoding: base64
Content-Type: image/jpeg;
	x-unix-mode=0644;
	name="ADIlogoFinalSmall.jpg"

/9j/4AAQSkZJRgABAQEASABIAAD//gAXQ3JlYXRlZCB3aXRoIFRoZSBHSU1Q/9sAQwBQNzxGPDJQ
RkFGWlVQX3jIgnhubnj1r7mRyP//////////////////////////////////////////////////
/9sAQwFVWlp4aXjrgoLr////////////////////////////////////////////////////////
/////////////////8AAEQgAQgAyAwEiAAIRAQMRAf/EABgAAQADAQAAAAAAAAAAAAAAAAABAgME
/8QAJBAAAgICAgICAgMAAAAAAAAAAAECEQMhEjFBURNxIjJhgZH/xAAVAQEBAAAAAAAAAAAAAAAA
AAAAAf/EABcRAQADAAAAAAAAAAAAAAAAAAABETH/2gAMAwEAAhEDEQA/AO0Aq5AYU5Tk7d34Rp8v
GuUXXspklGLttJlFk5WlUkCHUmmrXRJTHqKXRcAAAM5St96KZMnCPv8AgnyZ5Vc0gMGm25PbCW/R
o4tLqwkkuiqthnJS4ydp9HUmcmPeXSN5ycXGiI1BFgCjjTMskZdpW7s6Ssot9Ac0Zq2348hrm6VJ
eWaTjCSpx2yPjVa1QsWxRSVomUfyi1sm2oJxX9FoPkrapgKYLAAAAOZNLJJO+V+zT43Jbbr7M6Tn
K+79l3kcEnSa+wa0cajSKwaTovGSlFNdMwvb09AdAIXQAkAAY5Eua0XjFcVpf4AEMX6IR/V/YAUX
QAA//9k=

--Apple-Mail-4--46315359
Content-Type: multipart/alternative;
	boundary=Apple-Mail-6--46315358


--Apple-Mail-6--46315358
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed



--Apple-Mail-6--46315358
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
	charset=US-ASCII




--Apple-Mail-6--46315358--

--Apple-Mail-4--46315359--