You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in using the geoh5py Drillhole class (and associated ones like DrillholeGroup) in a project I'm working on but would strongly prefer to not create a geoh5 file. It seems this isn't currently possible, as a Workspace object is needed to create objects of these classes. Is that the case? If so, do you see a path to making the classes usable without a Workspace object? Would certainly be beneficial for the crowd interested in just loading some data into a jupyter notebook for a quick look!
Best,
Robert Collar
The text was updated successfully, but these errors were encountered:
If you change your mind and would like to create a disk representation, you simply run
workspace.save(filepath)
We initially didn't intend to have these classes used outside of geoh5, but looks like it might be desirable in the future. The plan would be to allow instantiating the objects outside the workspace, but that will require some re-write.
Hey Dom, great to hear that you've built in this work around. I'll give it a go. And def looking forward to instantiating objects outside of a workspace!
Turns out that our @benk-mira hit the same wall recently trying to parallel read/create drillholes. H5 files are not picklable, so this issue will be elevated.
Hey Mira Geoscience Team!
I'm interested in using the geoh5py
Drillhole
class (and associated ones likeDrillholeGroup
) in a project I'm working on but would strongly prefer to not create a geoh5 file. It seems this isn't currently possible, as aWorkspace
object is needed to create objects of these classes. Is that the case? If so, do you see a path to making the classes usable without aWorkspace
object? Would certainly be beneficial for the crowd interested in just loading some data into a jupyter notebook for a quick look!Best,
Robert Collar
The text was updated successfully, but these errors were encountered: