-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hdf5 output structure #21
Comments
I think so. That's a good point. Metadata never hurts! |
If we include the parameters in the hdf5 file, the structure would become
Would it be better to make a separate h5 file? i.e. do we want more files or more in the hdf5 file? |
One file is fine I think but put the parameters under a 'parameters' tree
to keep it cleaner.
…On Sat, Jan 28, 2017 at 6:45 PM, Ryan Levy ***@***.***> wrote:
If we include the parameters in the hdf5 file, the structure would become
├─ alps::params
├─ FREQUENCY_GRID
├─ SPREAD
├─ CUT
├─ alpha
│ ├─ values
│ ├─ probability
├─ DATA
├─ BACKCONTINUE
├─ SELF
├─ BETA
├─ LOG_MIN
├─ MAX_IT
├─ OMEGA_MAX
├─ VERBOSE
├─ DEFAULT_MODEL
├─ BASENAME
├─ SHIFT1
├─ NORM1
├─ PARTICLE_HOLE_SYMMETRY
├─ SHIFT
├─ help.grids
├─ ALPHA_MIN
├─ KERNEL
├─ NORM
├─ NDAT
├─ ALPHA_MAX
├─ help
├─ DATA_IN_HDF5
├─ DATASPACE
├─ TEXT_OUTPUT
├─ GENERATE_ERR
├─ N_ALPHA
├─ help.models
├─ spectrum
│ ├─ omega
│ ├─ chi
│ ├─ maximum
│ ├─ average
│ ├─ variance
├─ NFREQ
Would it be better to make a separate h5 file? i.e. do we want more files
or more in the hdf5 file?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AH6noBFueQIZ_QvmuM4bI2kKxHs_YbUHks5rW73zgaJpZM4LwlqD>
.
|
ryanlevy
added a commit
that referenced
this issue
Jan 28, 2017
saves under /parameters directory, which if maxent is reloaded from hdf5 should be read properly See: #21
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The structure to the HDF5 file produced by maxent isn't well defined. So far it has
Should we include the parameters used/calculated (through the ALPSCore param saving)?
The text was updated successfully, but these errors were encountered: