Opened 2 years ago

Last modified 2 years ago

#1994 new defect

PITTNUllCode/SphericalHarmonicRecon uses HDF5 1.8 functions

Reported by: Roland Haas Owned by:
Priority: minor Milestone:
Component: EinsteinToolkit thorn Version: development version
Keywords: SphericalHarmonicRecon Cc:


SphericalHarmonicRecon's file uses H5LTread_dataset_double ( which is only available in the hdf5 hl level library which is only provided in hdf5 1.8.7.

Nothing in the ET states that HDF5 1.8 is required.

This can be fixed my making sure that hdf5_hl is included in HDF5_LIBS which also will make compilation fail if the library in indeed missing.

We should decide whether we want to bump ExternalLibraries/HDF5's version number and have it itself check for HDF5 1.8 in which case thorns can rely on this version being present (if they require a new enough HDF5 ExternalLibraries) or provide workarounds in

Attachments (0)

Change History (5)

comment:1 Changed 2 years ago by anonymous

I think it is probably time to require the 1.8 API.

comment:2 in reply to:  1 Changed 2 years ago by anonymous

Replying to anonymous:

I think it is probably time to require the 1.8 API.

This was Frank...

comment:3 Changed 2 years ago by Frank Löffler

On the ET users call on 9. Jan 2017 was decided that the best course of action is to make 1.8 a requirement for the toolkit.

comment:4 Changed 2 years ago by Ian Hinder

I think this is good, but would like to know Erik's opinion. I think he joined the call after we discussed it.

comment:5 Changed 2 years ago by Erik Schnetter

I was not there during the discussion. HDF5 is now at version 1.10, so requiring 1.8 is possible. I am not aware of an HPC system that only has HDF5 1.6, and HDF5 is easy to install. Plus, we started supporting HDF5 1.8 in Cactus more than ten years ago, so this is not a surprise.

Now, HDF5 1.10 does have some very interesting features that we should use (or explore), such as e.g. virtual datasets (no more recombining!), or the new file format that promises much higher performance. But that's for another time.

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
Next status will be 'review'.
as The resolution will be set.
to The owner will be changed from (none) to the specified user.
Next status will be 'confirmed'.
The owner will be changed from (none) to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.