[Users] Visit & CarpetHDF5 mismatch?

[Kelly, Bernard J. (GSFC-660.0)[UNIVERSITY OF MARYLAND BALTIMORE COUNTY]]

Hi Ian, Christian.

I'd be great if the plugin became part of VisIt itself, since that would
remove some possible mismatches in HDF5 library versions (as well as
avoiding the need for separate compilation).

In the mean time, what I *really* need is a version of the CarpetHDF5
plugin with up-to-date installation instructions that is known to work
with the *current* VisIt release (2.4.2). I tried moving back to VisIt
2.3.2 to match what Bruno mentioned, but it didn't work any better.

Has anyone installed VisIt + CarpetHDF5 on a Mac from scratch *recently*?

Bernard



On 4/11/12 1:20 PM, "Ian Hinder" <ian.hinder at aei.mpg.de> wrote:

>
>On 11 Apr 2012, at 19:10, Kelly, Bernard J. (GSFC-660.0)[UNIVERSITY OF
>MARYLAND BALTIMORE COUNTY] wrote:
>
>> Hi Ian.
>> 
>> 
>> I'll look for a logfile, but there was nothing generated in my ~/.visit
>> that I could see.
>> 
>> Which reminds me: can frequent Visit/CarpetHDF5 users confirm for me
>>where
>> they get (a) Visit, and (b) CarpetHDF5? For me the answers are:
>> 
>> (a) the "Mac OS X - Intel 64 bit" binary from here:
>> https://wci.llnl.gov/codes/visit/executables.html
>> 
>> (b) the cactuscode VizTools trunk via svn:  svn co
>> https://svn.cactuscode.org/VizTools/CarpetHDF5/trunk/ CarpetHDF5
>> 
>> The instructions in the latter's README.txt seem a bit out of date,
>>which
>> made me suspicious. The lines about "updating the paths to the HDF5
>> library", for instance:
>
>Is the Carpet VisIt plugin part of the ET?  If it is, then we should make
>sure the documentation (i.e. the README) is up-to-date for each ET
>release.  If not, we should probably do it anyway :)