Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Using the HDF5 emulator library efficiently #2

Open
jgomezdans opened this issue Oct 30, 2015 · 0 comments
Open

Using the HDF5 emulator library efficiently #2

jgomezdans opened this issue Oct 30, 2015 · 0 comments

Comments

@jgomezdans
Copy link
Owner

While the I/O of emulators on to HDF5 files works, there are some things that we could definitely do to improve things. These are

  • Storing single band emulators for particular sensors. This could just be implemented as creating a subgroup for a particular emulator/geometry with the sensor name, and storing the different emulator parameters for the different bands. To make things easier, the sensor bands could be defined in the library (e.g. by having a MODIS set of bandpass functions, etc.)
  • Provide a simple way to retrieve emulators. This requires e.g. an environmental variable set to point to the directory where emulator HDF5 files are, and some exploration of file names etc.
jgomezdans pushed a commit that referenced this issue Jun 1, 2018
Emulators now use npz file format
c5393af 
The emulators (both spectral and scalar output) are both saved as
`.npz` files. This addresses #2. The idea is that you then have an
extra (text file) with some useful metadata for the emulators.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jgomezdans