I can verify that compiling hdf5-1.8.5-patch1 on Suse 11.1, with gnu
compilers (4.3) and just:
./configure
fails during make by running out of virtual memory compiling tselect.c.
The trunk also fails due to __h5global_MOD_ for
./configure --enable-fortran --enable-parallel
On Sun, 4 Sep 2011 16:12:41 +0200, Paul Anton Letnes wrote:
Hello everyone.
My fortran code using hdf5 compiles nicely on a number of machines.
After losing my laptop (sad, but true) I am now installing hdf5 (and
other stuff) on my machine to be able to compile my code again.
Needless to say, I
You probably looked at the C function for H5LTset_attribute_int and
found hsize_t size. The types usually match between Fortran and C and
actually there is a mistake in the C documentation and size should be
of type size_t and not hsize_t, we'll fix it in the documentation.
On Mon, 5 Sep 2011
Can you provide the contents of: H5fort_type_defines.h and
H5fortran_types.f90?
Thanks,
Scot
On Fri, 23 Sep 2011 15:54:20 +0200, Pierre de Buyl wrote:
Dear HDF5 users,
I am currently not able to build HDF5. I have the intel compilers
(full suite: C/C++ and Fortran) on a Core 2 Duo MacBook
int8 = selected_int_kind(8) (i.e int range 10^8) will not be big enough
to hold the numbers you are trying to read, try selected_int_kind(15)
which should give you an 8 byte integer.
On Tue, 04 Oct 2011 09:55:48 -0500, Denis wrote:
Hello,
I ran into a problem reading H5T_STD_I64BE data
You will have to compile hdf5 so that 8 byte integers are the default
integer type ( FCFLAGS = : -i8 with intel, fdefault-integer-8 with
gfortran). In the next release this requirement will be removed and,
additionally, you will be able to associated the KIND type with the hdf5
type.
On
Quoting Corey Bettenhausen corey.bettenhau...@ssaihq.com:
Howdy,
When fetching a string attribute using h5ltget_attribute_string_f(),
the string returned seems to be a C string i.e null terminated, even
when using the Fortran interface. Thus, one could set an attribute
of length 10 and
Also note, currently some of the C HL DS functions do and do not
include the NULL character in the returned length.
For example, H5DSset_scale returns a size which includes the NULL
termination. H5DSget_label does not include the NULL termination in
the returned size.
Quoting Zaak
did you declare the correct types for dset,ref_out,ref_size,hdferr?
INTEGER(HID_T) :: dset
what type is your ref_out??? :: ref_out
INTEGER(HSIZE_T) :: ref_size
INTEGER :: hdferr
On 08.12.2011 22:06, dyjbean wrote:
hi,
in my hdf5 file, there includes object reference, i want to read
Side note, change integer(8) to:
integer(size_t) :: type_size, offset
integer(size_t) :: type_sizei, type_sizer
Other then that, I removed the module specific variables and the code
compiled fine using gcc version 4.6.2
Are you sure you enabled the Fortran 2003 interface, i.e. the configure
Hi,
suggestions about storing this data as a compound type with variable
length fields without using pointers as explained in
h5ex_t_vlen_F03.f90 [1] example script on HDF GROUP web site. Thank
you in advance for your concerns.
I don't understand what you mean by not using pointers, do you
(1) you should use size_t not KIND=8, i.e.
INTEGER(size_t) :: sz1, sz2, sz3, sz, offset
(2) your compound datatype size is wrong, use instead:
sz = H5OFFSETOF(C_LOC(wdata(1)%a(1)), C_LOC(wdata(2)%a(1)))
On 2012-03-20 08:50, Ekin Akoglu wrote:
Dear members,
Attached are a script for
Try using H5OFFSETOF for the offset in H5Tinsert_f instead of
calculating it yourself.
offset = H5OFFSETOF(C_LOC(ms_data(1)),C_LOC(ms_data(1)%biomass))
call H5Tinsert_f(s_tid, biomass, offset, s1_tid, hdferr)
etc..
On 2012-03-21 07:22, Ekin Akoglu wrote:
Dear brtnfld,
Ok, I have found out
You need to initialize the Fortran interface:
CALL h5open_f(hdferr)
On 2012-03-26 06:22, Ekin Akoglu wrote:
Dear all,
I cannot read compound data from HDF file. I created the data and
wrote it to a HDF file with a FORTRAN subroutine and now trying to
read it within another FORTRAN program.
Ah yes, this problem sounded familiar, you can look at the
discussion/resolution at:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48404
Scot
On 2012-06-06 15:01, Kacper Kowalik wrote:
On 06.06.2012 20:48, brtn...@hdfgroup.org wrote:
Hi,
It should work with older gfortran versions.
Is this
H5LTpath_valid will tell you if the path exists. For your case it would
be:
htri_t path_valid =
H5LTpath_valid(file_id,/mygroup1/mygroup2/dataset1,FALSE)
(side note: Are you saying the above path does actually not exists and
therefore should return FALSE?)
This would check if all the
NB: I also have a separate version of gfortran in my home
directory (as opposed to an old one in the usual /usr/bin/gfortran)
and for the HDF5 installation to look for the correct library
files (specifically libquadmath) I not only had to add FCLIBS=xxx
before ./configure but also go in
The Fortran2003 option is not supported on windows with Visual Studio,
you can look at RELEASE.txt for the platforms supporting F2003. It is,
however, on our to-do list.
Scot
On 2012-11-16 09:24, Ekin Akoglu wrote:
P.S. Sorry for cross-posting but I forgot to edit the subject field
in my
On 2013-01-10 08:20, Marcin Dulak wrote:
Hi,
On 01/10/13 00:30, brtn...@hdfgroup.org wrote:
SIZEOF is a non-standard compiler intrinsic. Your compiler's version
of SIZEOF can not handle derived types. Fortunately, F2008 has
introduced intrinsic functions STORAGE_SIZE and C_SIZEOF, but this
The HDF5 file uses C storage conventions, which is why the matrix is
transposed.
See http://www.hdfgroup.org/HDF5/doc/UG/UG_frame12Dataspaces.html
section: 7.3.2.5. C versus Fortran Dataspaces
On 2013-02-27 06:32, Pradeep Jha wrote:
Hello,
I am trying to convert a unformatted data file
The following similar example might help you, can you check if you
obtain a similar output.
PROGRAM main
USE HDF5
INTEGER, PARAMETER :: nx=2
INTEGER :: error
INTEGER(HID_T) :: out_file, out_file_id,dspace_id
INTEGER(HID_T) :: dset_id_r, dset_id_d
INTEGER, PARAMETER :: rank=1
On 2013-03-04 10:02, M Pa wrote:
Hello,
I inherited a code that converts MODIS (MYD04_L2 type) data to bufr.
I compiled the code and checked files for content and they contain
the
data I want to use. Also I checked that the code is got the name of
the file right.
When I try to read dimensions
On 2013-02-27 21:01, Pradeep Jha wrote:
Thanks for the response. So from what I understand, the HD5 fortran
wrapper automatically transposes the matrix to store it in the C
storage conventions. So puttings dims(1) = Nx and dims(3) = Nz is
correct. HDF5 fortran wrapper is just transposing the
Are you sure mpif90 is working, configure stops when trying to compile
a test fortran program. You should still be able to compile the
configure fortran tests with mpif90, regardless of the status of
fc_version_info. Can you look in the config.log and see why configure
failed to compile the
24 matches
Mail list logo
