<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Hi List,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>For the extremely interested parties, you can also get the same archive referenced below at the following link:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="https://skydrive.live.com/redir?resid=71D8AA22E9EC883E!160&authkey=!AOwhwcNGc-RqfQE">https://skydrive.live.com/redir?resid=71D8AA22E9EC883E!160&authkey=!AOwhwcNGc-RqfQE</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Regards and thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>John<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><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"'> openslide-users-bounces+jminnie=live.com@lists.andrew.cmu.edu [mailto:openslide-users-bounces+jminnie=live.com@lists.andrew.cmu.edu] <b>On Behalf Of </b>John Minnie<br><b>Sent:</b> Tuesday, September 11, 2012 6:54 AM<br><b>To:</b> Openslide Users Mailing List <br><b>Subject:</b> Information regarding MIRAX v2.2 tile positioning<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi List,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For the past few months I have been working on bug #92 on the openslide issue list. The main problem is that the new format (greater than v1.9) appears to have missing position data, which manifests as seams when positioning the tiles. It is my contention that the “usual” slide position file present in v1.9 data has been dropped, in favor of an xml-based layout of the same positioning data.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the hierarchical section of the ini file, one will find several xml related NONHIER sections. I have been able to consistently extract from the data files some xml-based information that seems to be 1-to-1 related to the slide position file of old. I have to get final confirmation, but I think the xml-based position data is found in the “ProfileXML” section of the “Scan data layer” NONHIER level. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have a zip archive of 1.5Mb with both sets of data. If you are interested in reviewing the data, please let me know then I can forward it directly to you. In the archive you will find a dump of the original slide position buffer, where the *.xyp files are named as follows: {slide position record number}_{x-position}_{y-position}.xyp. The slide in question from which this data was extracted is the CMU-1 test slide available on the openslide site.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The xml scaninfo files are also present, and the names of these files are the tile index to which the scaninfo applies, extracted directly from a data file and not computed based on any formula.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For all of the v1.9 MIRAX slides at my disposal, there is ALWAYS a 1-to-1 correlation between the total number of xyp files and xml files, supporting the notion of a relationship between the old slide position file buffer previously found in the NONHIER section “VIMSLIDE_POSITION_BUFFER” and the xml-based scaninfo data. For v2.2 slides, the old position buffer cannot be located, but the xml-based data is always present.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>My quest is now to seek consensus from the openslide community that this is a real correlation and not coincidence. It is my further contention that the “VIMSLIDE_POSITION_BUFFER” data has been removed from v2.2 slides (and possibly in v2.0) due to redundancy, and that the xml-based positioning is the only available data for tile positioning.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Any advice and suggestion how to interpret the xml-based position data in terms of the old slide position buffer will be hugely appreciated. My own work in this area continues.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards and thanks,<o:p></o:p></p><p class=MsoNormal>John<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>