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
The older version of blimpy allowed .fil files to have their headers read with the read_header function. Are the .h5 files supposed to be compatible with this function as well? It's not clear from read_header's docstring or from my perusing of the source code for the past several minutes.
I ask because I am getting errors when attempting to use this function on .h5 files. For example, attempting to call read_header on any of the files in bls0:/mnt_bls5/datax3/holding.Lband.692.0001020304050607/ gives me the following error:
/opt/pyve/sci/local/lib/python2.7/site-packages/blimpy/sigproc.pyc in read_header(filename, return_idxs)
230
231 # Check this is a blimpy file
--> 232 keyword, value, idx = read_next_header_keyword(fh)
233
234 try:
/opt/pyve/sci/local/lib/python2.7/site-packages/blimpy/sigproc.pyc in read_next_header_keyword(fh)
193 return keyword, 0, fh.tell()
194 else:
--> 195 dtype = header_keyword_types[keyword]
196 #print dtype
197 idx = fh.tell()
KeyError: '\r\n\x1a\n\x00\x00\x00\x00\x00\x08\x08\x00\x04\x00\x10\x00'
The text was updated successfully, but these errors were encountered:
Thanks @telegraphic! And yes, I think a universal blimpy function to read headers would be convenient and appreciated in the future, even if just a combined wrapper around the sigproc and h5py functions.
Hi folks,
The older version of blimpy allowed
.fil
files to have their headers read with theread_header
function. Are the.h5
files supposed to be compatible with this function as well? It's not clear fromread_header
's docstring or from my perusing of the source code for the past several minutes.I ask because I am getting errors when attempting to use this function on
.h5
files. For example, attempting to callread_header
on any of the files inbls0:/mnt_bls5/datax3/holding.Lband.692.0001020304050607/
gives me the following error:The text was updated successfully, but these errors were encountered: