Description
Currently, pull_spots from the HEDM_Instrument class outputs either a text file (spots_#####.out) or an h5 file (spots_#####.hdf5). Would be nice if in the config file, in addition to the output filetype being either 'txt' or 'h5' add a potential key for 'both'. Only changes the types of outputs, no implications on rest of library. I currently have a work around that I use to do this.
Rationale
The h5 files contain much more information about the spots than the text files. In its current state, if I want to get that information I either have to lose the txt files during the fit-grains to output h5 files, or ex-situ run pull_spots which effectively doubles the time for running as you have to go back and grab the spots again.
Specification
No comment
Compatibility
No affect to the code other than changing the pull_spots output filepaths.
Affected Workflows
Description
Currently, pull_spots from the HEDM_Instrument class outputs either a text file (spots_#####.out) or an h5 file (spots_#####.hdf5). Would be nice if in the config file, in addition to the output filetype being either 'txt' or 'h5' add a potential key for 'both'. Only changes the types of outputs, no implications on rest of library. I currently have a work around that I use to do this.
Rationale
The h5 files contain much more information about the spots than the text files. In its current state, if I want to get that information I either have to lose the txt files during the fit-grains to output h5 files, or ex-situ run pull_spots which effectively doubles the time for running as you have to go back and grab the spots again.
Specification
No comment
Compatibility
No affect to the code other than changing the pull_spots output filepaths.
Affected Workflows