RE: hdf5 (h5py) anyone?

["Malitsky, Nikolay D" <malitsky@bnl.gov>]

>what does an 'extra service' mean?
>Are you talking about a client/server architecture?

yes. In short, you can consider it as the Channel Archiver extension/upgrade with
(one of) a new driver to the hdf5 backend.  As a result, conceptually everything
(including file structure) would be the same except several extensions like support
of the EPICS 4 structured data types. The type registry and associated topics will be
presented at the next EPICS meeting.

-Nikolay

---

From: Emmanuel Mayssat [emayssat@yahoo.com]
Sent: Thursday, March 22, 2012 1:00 PM
To: Malitsky, Nikolay D; epics
Subject: Re: hdf5 (h5py) anyone?

> read/write issues, multi-file data processing, etc require the corresponding extra service.

what does an 'extra service' mean?
Are you talking about a client/server architecture?
An add-on piece of software you have to pay for?

Is there a web page (a pointer) that talks about those topics and their implementation?
(sample code?)

It turns out a good starting point may be
http://www.hdfgroup.org/hdf5-quest.html#GENERAL

Although you may not have the answer yet, has anyone though (at least conceptually) of a h5 tree structure (database) design for archiving?
Would that be time based? (tree node like /date/20120315)
Would that be hardware based? (/chassis_id/device_type/device_id)
Would that be PV name base? (archiving of  AAA:BBB:CCC pv is located at /AAA/BBB/CCC )
Would that be subsystem based? ( /injector/solenoids/I:SO01/current )
the last 3 at once with links?

Thanks,
--
E