<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Bernard,<div><br><div><div>On Apr 11, 2012, at 11:10 AM, Kelly, Bernard J. (GSFC-660.0)[UNIVERSITY OF MARYLAND BALTIMORE COUNTY] wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Which reminds me: can frequent Visit/CarpetHDF5 users confirm for me where<br>they get (a) Visit, and (b) CarpetHDF5? For me the answers are:<br><br>(a) the "Mac OS X - Intel 64 bit" binary from here:<br><a href="https://wci.llnl.gov/codes/visit/executables.html">https://wci.llnl.gov/codes/visit/executables.html</a><br></div></blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I also use the 64 bit binary (version 2.3.2 in my case).</div><br><blockquote type="cite"><div>(b) the cactuscode VizTools trunk via svn: svn co<br><a href="https://svn.cactuscode.org/VizTools/CarpetHDF5/trunk/">https://svn.cactuscode.org/VizTools/CarpetHDF5/trunk/</a> CarpetHDF5<br></div></blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>yes, this is the correct repository. I didn't need to update the path in my case. I just followed the standard installation instructions and it worked without problems.</div><div><br></div><div>Cheers,</div><div>Bruno</div><br><blockquote type="cite"><div>The instructions in the latter's README.txt seem a bit out of date, which<br>made me suspicious. The lines about "updating the paths to the HDF5<br>library", for instance:<br><br>install_name_tool -change '@executable_path/../lib/libhdf5.dylib'<br>'/usr/local/lib/libhdf5.1.dylib'<br>~/.visit/darwin-i386/plugins/databases/libEvisitCarpetHDF5Database_ser.dyli<br>b<br><br>Now my 64-bit installation generates three subdirectories in ~/.visit:<br>"2.4.2", "darwin-i386", and "darwin-x86_64". Of these, only "2.4.2" had<br>any content in the "plugins/databases/" subdirectory, and these dylibs<br>were *similar but not identical* in name to what's mentioned in the README<br>(e.g., libECarpetHDF5Database_ser.dylib rather than<br>libEvisitCarpetHDF5Database_ser.dylib).<br><br>So ... should I be using a different version of Visit (older, 32-bit,<br>etc.)?<br><br>Bernard<br><br>On 4/10/12 4:24 PM, "Ian Hinder" <<a href="mailto:ian.hinder@aei.mpg.de">ian.hinder@aei.mpg.de</a>> wrote:<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">On 10 Apr 2012, at 22:21, Kelly, Bernard J. (GSFC-660.0)[UNIVERSITY OF<br></blockquote><blockquote type="cite">MARYLAND BALTIMORE COUNTY] wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Hi all. I'd like to visualise some 3D data produced by an initial-data<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">run<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">of the EinsteinToolkit (Maxwell).<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I'm outputting using CarpetIOHDF5; I have an output file<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">"hahndol::hahndol_coulomb.h5", and decided to use Visit, as recommended<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">by<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">cactuscode, etc.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I grabbed the CarpetHDF5 plugin code from svn, and installed as per<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">instructions (pointing at the ETK-installed HDF5 in my<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Cactus/configs/<config-name>/scratch/external directory).<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Starting Visit (2.4.2) , and trying to load a .h5 file yields the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">following error:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-------------------------------------------------------------------------<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">----<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">The metadata server running on host localhost has exited abnormally.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">VisIt<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">is trying to restart it.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Shortly thereafter, the following occured...<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">VisIt was unable to open<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">"/Users/bjkelly1/Projects/CODES/Cactus/exe/BL_IJS_test/hahndol::hahndol_c<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">ou<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">lomb.h5". Each attempt to open it caused VisIt's metadata server to<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">crash. This can occur when the file is corrupted, or when the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">underlying<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">file format has changed and VisIt's readers have not been updated yet,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">or<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">when the reader VisIt is using for your file format is not robust.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Please<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">check whether the file is corrupted and, if not, contact a VisIt<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">developer.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-------------------------------------------------------------------------<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">----<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I have no idea whether the file is corrupted, but wanted to know: is the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">CarpetHDF5 plugin up-to-date with the output of Maxwell's CarpetIOHDF5?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Any basic ideas where I might have gone wrong?<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">One problem can come from Visit trying to open too many files for the<br></blockquote><blockquote type="cite">maximum open file limit of your OS. Mac OS, for example, has a very<br></blockquote><blockquote type="cite">small limit. Try changing this with ulimit. But ultimately, you should<br></blockquote><blockquote type="cite">try to find the actual error message. I think there is an option for<br></blockquote><blockquote type="cite">Visit to output the errors to a file, but it's so long since I've used<br></blockquote><blockquote type="cite">Visit that I don't remember. Probably someone else can fill that in...<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-- <br></blockquote><blockquote type="cite">Ian Hinder<br></blockquote><blockquote type="cite"><a href="http://numrel.aei.mpg.de/people/hinder">http://numrel.aei.mpg.de/people/hinder</a><br></blockquote><blockquote type="cite"><br></blockquote><br>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@einsteintoolkit.org">Users@einsteintoolkit.org</a><br>http://lists.einsteintoolkit.org/mailman/listinfo/users<br></div></blockquote></div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><div>Dr. Bruno Giacomazzo</div><div>JILA - University of Colorado</div><div>440 UCB<br>Boulder, CO 80309</div><div>USA</div><div><br></div><div>Tel. : +1 303-492-0389</div><div><div>Fax : +1 303-492-5235</div></div><div>email : <a href="mailto:bruno.giacomazzo@jila.colorado.edu">bruno.giacomazzo@jila.colorado.edu</a></div><div>web: <a href="http://www.brunogiacomazzo.org">http://www.brunogiacomazzo.org</a></div><div><br></div><div>----------------------------------------------------------------------</div><div>There are only 10 types of people in the world:</div><div>Those who understand binary, and those who don't</div><div>----------------------------------------------------------------------</div></div></span></span></span></div></span></div></span></div></span></div></span></span>
</div>
<br></div></body></html>