<div dir="auto">I recall that I tested the fixed nrrd files with other volume rendering capable browsers. Let me look for the corresponding X3D scenes and post their URLs for further testing.<div dir="auto"><br></div><div dir="auto">I remember it was pretty difficult to discover the files on savage.</div><div dir="auto"><br></div><div dir="auto">Cheers,</div><div dir="auto"><br></div><div dir="auto">Andreas</div><br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On Feb 13, 2018 10:29 AM, "Don Brutzman" <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nicholas... am following up on this lingering item from the holiday break.<br>
<br>
Can you please confirm the correction by Andreas, and advise on how we are handling the files?<br>
<br>
I don't mind hosting at <a href="http://savage.nps.edu" rel="noreferrer" target="_blank">savage.nps.edu</a> but often there are difficulties with server certificates and cross-origin resource sharing (CORS). Thus it would be good to figure out how best to handle this large Web3D dataset.<br>
<br>
If the "right answer" isn't immediately clear, perhaps a short session in one of the regular teleconferences might be appropriate sometime, then we can figure it out together.<br>
<br>
TIA.<div class="elided-text"><br>
<br>
On 1/2/2018 12:30 AM, Don Brutzman wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for further checking Andreas.<br>
<br>
Nicholas (cc:ed) is originator of these files. Have also copied Medical working group since these are relevant examples.<br>
<br>
I will be happy to post updates to these files but am hoping that we all proceed consistently to avoid versionitis later. Further most are large (indeed overwhelming usual .zip distributions) so it is good to get them all sorted out correctly together.<br>
<br>
v/r Don<br>
<br>
On 1/1/2018 5:32 PM, Andreas Plesch wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It turns out that<br>
<br>
<a href="http://savage.nps.edu/Savage/VolumeRendering/datasets/nrrd/mri_ventricles_segment.nrrd" rel="noreferrer" target="_blank">http://savage.nps.edu/Savage/V<wbr>olumeRendering/datasets/nrrd/m<wbr>ri_ventricles_segment.nrrd</a><br>
<br>
has the same problem of a malformed header line, eg. an excess space<br>
character in the spacings line.<br>
<br>
Here is a corrected nrrd file:<br>
<br>
<a href="https://cdn.glitch.com/405924cd-3c0d-476e-9b88-520a5610604c%2Fmri_ventricles_segment_fixed.nrrd?1514854259949" rel="noreferrer" target="_blank">https://cdn.glitch.com/405924c<wbr>d-3c0d-476e-9b88-520a5610604c%<wbr>2Fmri_ventricles_segment_<wbr>fixed.nrrd?1514854259949</a><br>
<br>
-Andreas<br>
<br>
On Mon, Dec 18, 2017 at 4:18 PM, Andreas Plesch <<a href="mailto:andreasplesch@gmail.com" target="_blank">andreasplesch@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am working on ImageTexture3D support for x3dom using the existing<br>
ImageTextureAtlas node and <a href="https://github.com/scijs/nrrd-js" rel="noreferrer" target="_blank">https://github.com/scijs/nrrd-<wbr>js</a> as a<br>
parser.<br>
<br>
It turns out the the parser is very strict, and so discovered a<br>
malformed header line in<br>
<a href="https://savage.nps.edu/Savage/VolumeRendering/datasets/nrrd/mri_ventricles.nrrd" rel="noreferrer" target="_blank">https://savage.nps.edu/Savage/<wbr>VolumeRendering/datasets/nrrd/<wbr>mri_ventricles.nrrd</a><br>
used in <a href="http://www.web3d.org/x3d/content/examples/Basic/VolumeRendering/BasicVentriclesIndex.html" rel="noreferrer" target="_blank">http://www.web3d.org/x3d/conte<wbr>nt/examples/Basic/VolumeRender<wbr>ing/BasicVentriclesIndex.html</a><br>
<br>
Specifically, the header line<br>
'spacings: NaN 0.009 0.009 0.009'<br>
<br>
has _two_ space character after the colon delimiter. Exactly _one_<br>
space is allowed, however, as described here:<br>
<br>
<a href="http://teem.sourceforge.net/nrrd/format.html#general.2" rel="noreferrer" target="_blank">http://teem.sourceforge.net/nr<wbr>rd/format.html#general.2</a><br>
second paragraph:<br>
... a string "<field>" identifying the field (called the field<br>
identifier), then a colon followed by a single space ": ", and then<br>
the information describing the field "<desc>" (called the field<br>
descriptor) ...<br>
<br>
The second space then acts as a separator making the first value in<br>
the array an empty string which causes throwing when attempting to<br>
parse as a float.<br>
<br>
I made an attempt at fixing the header by removing one space and made<br>
the file available here:<br>
<br>
<a href="https://cdn.glitch.com/af228b45-6772-432d-a549-74f9f447b2c3%2Fmri_ventricles2.nrrd?1513631507711" rel="noreferrer" target="_blank">https://cdn.glitch.com/af228b4<wbr>5-6772-432d-a549-74f9f447b2c3%<wbr>2Fmri_ventricles2.nrrd?<wbr>1513631507711</a><br>
<br>
-Andreas<br>
<br>
-- <br>
Andreas Plesch<br>
Waltham, MA 02453<br>
</blockquote></blockquote></blockquote>
<br>
all the best, Don<br>
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA <a href="tel:%2B1.831.656.2149" value="+18316562149" target="_blank">+1.831.656.2149</a><br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">http://faculty.nps.edu/brutzma<wbr>n</a><br>
</div></blockquote></div><br></div></div>