<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:black'>Jason, (or whomever knows the answer to this)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:black'>In the case of the flex file (and other tiff derivative), how does
the usage of ome.tiff (or ome.xml) with a pointer to the flex file works? Will OMERO
allow this kind of import, even if the flex file format itself is not supported
by OMERO (but bioformat, supports the pixel type)?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:black'>Best,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:black'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>Ghislain Bonamy, PhD<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>__________________________________________<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>Research Investigator<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>Genomic Institute of the<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>Novartis Research<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>Foundation<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>Department of Molecular &
Cell Biology, room G214<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>10675 John Jay Hopkins Drive<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>San Diego CA 92121<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>USA<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>+1 (858) 812-1534 (W & F)<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>+1 (757) 941-4194 (H)<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>+1 (858) 354-7388 (M)<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'><a href="www.gnf.org">www.gnf.org</a><o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'>Hudson-Alpha Institute for
Biotechnology<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:11.0pt;
font-family:"Arial","sans-serif";color:black'><a href="www.haib.org">www.hudsonalpha.org</a><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:black'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
ome-users-bounces@lists.openmicroscopy.org.uk
[mailto:ome-users-bounces@lists.openmicroscopy.org.uk] <b>On Behalf Of </b>Jason
Swedlow<br>
<b>Sent:</b> Tuesday, May 05, 2009 7:46 AM<br>
<b>To:</b> <Matthew.Smicker@sanofi-aventis.com><br>
<b>Cc:</b> ome-users@lists.openmicroscopy.org.uk<br>
<b>Subject:</b> Re: [ome-users] Flex File Format<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi Matthew-<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal>On 4 May 2009, at 11:08, <<a
href="mailto:Matthew.Smicker@sanofi-aventis.com">Matthew.Smicker@sanofi-aventis.com</a>>
<<a href="mailto:Matthew.Smicker@sanofi-aventis.com">Matthew.Smicker@sanofi-aventis.com</a>>
wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>Does OMERO convert to OME-TIFF upon import of a non-OME-TIFF
file? <o:p></o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal>My<br>
impression was that it preserved the original format and just used<br>
Bio-formats to read it?<o:p></o:p></p>
</div>
</blockquote>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>OMERO uses Bio-Formats to read proprietary files. As
discussed before on this list, we turn on formats in OMERO once we are sure
metadata support is correct and we have a good set of test data.
Even then, we have problems with different versions of formats, specific
metadata types. <o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
I wanted to comment that the issue touched upon with vendor<br>
compatibility is a significant one. We have cases where usage of the<br>
vendor software is critical, but the development of that software to<br>
support OME-TIFF is not feasible. Conversion from proprietary formats<br>
would in most cases be possible, but not necessarily the other way. It<br>
also takes time and extra logic.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Converting files is certainly inconvenient, especially when
dealing with large data sets.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>A solution is to use an application like OMERO, that
provides a common interface to many different data types.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>Ghislain's idea of the 'chimeric' OME-TIFF/Flex-file sounds
nifty since<br>
the FLEX file is essentially TIFF. His other suggestion of having a<br>
pointer to the pixel data within the original file could be more<br>
flexible (e.g. non-TIFF formats as well).<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Yes, but think this through, and consider the difficulty of
maintaining metadata synchrony between the two, or more, files. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The idea of the pointer to the pixel data is already in
OME-TIFF.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>In general, this discussion demands a solution to this
problem, now. We sympathise-- our own science and discovery also suffers
from the difficulties imposed by lack of interoperability. So our work
towards standardised formats and interfaces is a work in progress. We are
far advanced over where we were one year ago. Given that progress and
momentum, we'd prefer to keep pushing the concepts of interoperability for all
developers. As a customer, you have alot of power to demand this type of
standardization from your vendors. OME's job is to ensure that
implementing interoperability is easy, cost effective for commercial entities,
and most importantly, enabling.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal><br>
<br>
Rather than conversion, I could imagine a metadata translation to<br>
OME-XML with pointers to the image file/index. After translation, the<br>
reader would start with OME-XML parsing, but use a specific native image<br>
reader for the pixels. (basically focus on the metadata standard as a<br>
file rather than pixels)<o:p></o:p></p>
</div>
</blockquote>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Interesting. You should come work with OME and see how
much fun we have just tracking the metadata! Pixels too?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>If:<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>1. someone out there can provide funding for this<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>2. get all the vendors to guarantee that they will
update us with correct specifications of new formats BEFORE they are released<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>we'll consider it. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
...that or hopefully things progress more quickly with OME-TIFF<br>
adoption!<o:p></o:p></p>
</div>
</blockquote>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Exactly. That seems the simplest, and ultimately the
most effective strategy.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Thanks very much for your feedback. This is a great
discussion, and covers many of the issues that we have worked through many
years.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Cheers,<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Jason<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal><br>
Matt<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ome-users-bounces@lists.openmicroscopy.org.uk">ome-users-bounces@lists.openmicroscopy.org.uk</a><br>
[<a href="mailto:ome-users-bounces@lists.openmicroscopy.org.uk">mailto:ome-users-bounces@lists.openmicroscopy.org.uk</a>]
On Behalf Of<br>
Ghislain Bonamy<br>
Sent: Sunday, May 03, 2009 4:04 PM<br>
To: Jason Swedlow<br>
Cc: <a href="mailto:ome-users@lists.openmicroscopy.org.uk">ome-users@lists.openmicroscopy.org.uk</a>;
John Moffat<br>
Subject: Re: [ome-users] Flex File Format<br>
<br>
Hi Jason,<br>
<br>
<br>
<br>
Thanks for the feedback! Let me try to clarify a few points:<br>
<br>
<br>
Unfortunately the flex file format is not up to date in the bioformats,<br>
although some of the new metadata is handled. In particular, bioformats<br>
is unable to retrieve the number of fields/z-section/channels/time<br>
point, which is critical point. <br>
<br>
<br>
<br>
Thanks for this feedback. This is news to us, as we correctly report<br>
this metadata from the test files we have. If you have had problems<br>
using Bio-Formats, the best thing to do is to send us details, and if<br>
possible, the offending files, and we'll certainly work to we fix any<br>
problems we find.<br>
<br>
<br>
<br>
GB: What I meant here is that many new tags are supported; however some<br>
of the critical one are not correctly handled. I do not believe that<br>
that I am using any special files, but rather that the way to extract<br>
the number of z-sections, fields etc. has not been implemented. I talked<br>
about his with Melissa a few months ago, and perhaps we can take this<br>
discussion off-line with users interested in FLEX file reader<br>
improvements in bioformats.<br>
<br>
<br>
I was hoping to work on this and add this capacity to the format but<br>
have not had a chance to it. I have contacted P&E about maybe helping<br>
out since they are using Omro a base for their Columbus platform, but I<br>
don't think, oddly enough, that they are interested to help. <br>
<br>
<br>
<br>
On the contrary, PerkinElmer (I assume that is who you are referring to)<br>
have been very helpful supplying test files. Again, if you have files<br>
that might expose something we don't know about, sending us specific<br>
details and the data is the best thing to do.<br>
<br>
<br>
<br>
GB: Yes I was referring to PerkinElmer. I am glad to hear that they<br>
provided file examples, although I still hope that perhaps they will<br>
provide some actual coding/testing support to allow full handling of<br>
their FLEX file format. As mentioned above, I do not think that the flex<br>
files that I am using differ from the one they have provided. I believe<br>
it is more a matter of parsing out the full information contained in<br>
their metadata.<br>
<br>
<br>
<br>
Perhaps if enough customer request that they help improving bioformats<br>
they might do it. I will try to work on it soon and will keep the Opera<br>
users posted. Furthermore, a nice feature would be to be able to keep<br>
the metadata from the flex file in addition to the metadata from OME, so<br>
that the flex file remains backward compatible with the Epochal (becomes<br>
both an ome.tiff and remains a flex file). This feature which could be<br>
extended to all TIFF derivative format, may require some serious<br>
modifications of bioformats, but I will let the expert (i.e.. Jason) see<br>
what they can do about t.<br>
<br>
<br>
<br>
Can you explain why we should do this? Why doesn't the metadata in<br>
OME-TIFF satisfy your needs? Note that we NEVER directly write<br>
proprietary formats-- we have enough problems supporting reads of all<br>
the variants. Writing as well would be a minefield, and more<br>
importantly, breaks the whole concept of supporting interoperability.<br>
<br>
<br>
<br>
GB: I am not suggesting writing a proprietary file format, although I<br>
see why it may sound like it. One of the limitations with using the<br>
OME-TIFF model is that the file becomes incompatible with the vendors<br>
tools. It seems that the format selected by P&E is very good in the<br>
sense that it builds on a format logic closely related to OME-TIFF.<br>
Thus, I though enabling creation of chimeric files could be useful for<br>
formats in which it can be implemented (manly with Tiff derivative<br>
formats). I wrote this in relation to importing files into OMERO, which<br>
was the purpose of the original thread. If Flex flex files can be<br>
converted as OME.TIFF, but retain the flex file characteristics (ie.<br>
flex extension + correct IFID), this would make it very convenient. I<br>
suppose that an easier (and perhaps better) alternative would be to<br>
generate an OME-TIFF file were the pixel data points to the flex file?<br>
Could this work and allow users to import there flex files into OMERO?<br>
<br>
On another note bioformats does support the luraware compression,<br>
granted hat you provide a license code for it. Logic would suggest that<br>
a key would be required to compress with luraware but not to decompress<br>
to make the forma at least partially open. This however is not the case.<br>
Perhaps P&E should in my opinion provide such license code since the<br>
capacity of a user to read an image is obviously a inherent part of<br>
their system. However, this may not be part of the agreement they reach<br>
with Luraware. In the mean time, saving as uncompressed tiff is the<br>
better solution.<br>
<br>
<br>
<br>
We can't comment on PerkinElmer's plans for file formats; we have no<br>
knowledge of their plans and agreements and any discussions of this with<br>
the community and users is up to them. We do however agree that saving<br>
data in uncompressed form often leaves the user with many more options<br>
for data handling and analysis.<br>
<br>
<br>
<br>
GB: Agreed, just brought it up for users employing Luraware compression<br>
and hoping to get a response from people at P&E, to see if it would be<br>
feasible within their licensing agreement with Luraware to provide a<br>
license key to their Opera users. In particular for working with OMERO<br>
with compressed FLEX files.<br>
<br>
Let me know if my points remain unclear.<br>
<br>
Best,<br>
<br>
Ghislain Bonamy, PhD<br>
_______________________________<br>
Genomic Institute of the<br>
Novartis Research<br>
Foundation<br>
Functional Genomics, G214<br>
+1 (858) 812-1534 (W & F)<br>
+1 (858) 354-7388 (C)<br>
www.gnf.org <<a href="http://www.gnf.org/%20%3chttp:/www.gnf.org/">http://www.gnf.org/
<http://www.gnf.org/</a>> > <br>
<br>
HudsonAlpha Instiute for Biotechnology<br>
www.hudsonalpha.org <<a href="http://www.hudsonalpha.org/">http://www.hudsonalpha.org/</a>>
<<a href="http://www.gnf.org/">http://www.gnf.org/</a>> <br>
<br>
________________________________<br>
<br>
From: <a href="mailto:ome-users-bounces@lists.openmicroscopy.org.uk">ome-users-bounces@lists.openmicroscopy.org.uk</a>
on behalf of John<br>
Moffat<br>
Sent: Fri 5/1/2009 11:40 PM<br>
To: <a href="mailto:ome-users@lists.openmicroscopy.org.uk">ome-users@lists.openmicroscopy.org.uk</a><br>
Subject: [ome-users] Flex File Format<br>
<br>
<br>
<br>
Hi,<br>
I was just about to ask the exact same question as the previous poster.<br>
Since I'm not using the Lurawave compression (not worth the hassle, in<br>
my opinion), is there a way we can activate the PerkinElmer .flex format<br>
in the bioformats library?<br>
<br>
Does anyone know if the flex file bioformat is up to date with the newer<br>
(Acapella 2) version of the format? Either way, I'd like to test it.<br>
<br>
Thanks<br>
John<br>
<br>
<br>
_______________________________________________<br>
ome-users mailing list<br>
<a href="mailto:ome-users@lists.openmicroscopy.org.uk">ome-users@lists.openmicroscopy.org.uk</a><br>
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users<br>
<br>
<br>
_______________________________________________<br>
ome-users mailing list<br>
ome-users@lists.openmicroscopy.org.uk<br>
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users<br>
<br>
<br>
<br>
<br>
<br>
**************************<br>
<br>
Wellcome Trust Centre for Gene Regulation & Expression<br>
<br>
College of Life Sciences<br>
<br>
MSI/WTB/JBC Complex<br>
<br>
University of Dundee<br>
<br>
Dow Street<br>
<br>
Dundee DD1 5EH<br>
<br>
United Kingdom<br>
<br>
<br>
<br>
phone (01382) 385819<br>
<br>
Intl phone: 44 1382 385819 <br>
<br>
FAX (01382) 388072 <br>
<br>
email: jason@lifesci.dundee.ac.uk <mailto:jason@lifesci.dundee.ac.uk> <br>
<br>
<br>
<br>
Lab Page: http://www.dundee.ac.uk/lifesciences/swedlow/<br>
<http://www.dundee.ac.uk/lifesciences/swedlow/> <br>
<br>
Open Microscopy Environment: http://openmicroscopy.org<br>
<http://openmicroscopy.org/> <br>
<br>
**************************<br>
<br>
<br>
<br>
The University of Dundee is a Scottish Registered Charity, No. SC015096.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
ome-users mailing list<br>
ome-users@lists.openmicroscopy.org.uk<br>
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users<br>
_______________________________________________<br>
ome-users mailing list<br>
ome-users@lists.openmicroscopy.org.uk<br>
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>**************************</span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:black'>Wellcome Trust Centre for Gene Regulation & Expression</span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:black'>College of Life Sciences</span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:black'>MSI/WTB/JBC Complex</span><span style='font-size:9.0pt;font-family:
"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>University of Dundee</span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>Dow Street</span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>Dundee DD1 5EH</span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>United Kingdom</span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>phone (01382) 385819</span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>Intl phone: 44 1382
385819 </span></span><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>FAX (01382)
388072 </span></span><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>email: <a
href="mailto:jason@lifesci.dundee.ac.uk">jason@lifesci.dundee.ac.uk</a></span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>Lab Page: <a
href="http://www.dundee.ac.uk/lifesciences/swedlow/">http://www.dundee.ac.uk/lifesciences/swedlow/</a></span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>Open Microscopy Environment: <a
href="http://openmicroscopy.org">http://openmicroscopy.org</a></span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:9.0pt;
font-family:"Helvetica","sans-serif";color:black'>**************************</span></span><span
style='font-size:9.0pt;font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'>The University of Dundee is a Scottish Registered Charity, No.
SC015096.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif";
color:black'><br>
<br>
</span><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>