-
Notifications
You must be signed in to change notification settings - Fork 2
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
cFit read support missing from superdarn.py #19
Comments
Thank you for the feedback, I was not aware cFit is still used as FITACF is distributed more often and has a stronger support system. Due to the loss of the DSWG chair, there hasn't been much action on pyDARNio and knowing what the standard formats are. However, you can try |
Hi Marina,
That didn't work:
>> import pydarn
>> file = '/Users/chartat1/superdarn/data/cfit/2020/01/20200131.wal.cfit'
>> pydarn.SuperDARNRead().read_dmap(file)
Error: /Users/chartat1/superdarn/data/cfit/2020/01/20200131.wal.cfit contains an block size 0 == 0 at record 0.
Error: /Users/chartat1/superdarn/data/cfit/2020/01/20200131.wal.cfit contains an block size 0 == 0 at record 0.
..... Will try to read DMap file with read_dmap
IF THIS FAILS please make an issue on pyDARNio, not pyDARN's issue
<bound method DmapRead.read_records of SuperDARNRead(/Users/chartat1/superdarn/data/cfit/2020/01/20200131.wal.cfit, 8, 0, 3384079)>
cFit is used quite widely I think, because it's so much smaller than fitACF. I've made what I think should be the format description for cFIT, but I'm not 100% sure how it goes into pydarn. Example cFit attached.
Alex
class cFit():
"""
Class containing Fitacf fields
"""
# Standard fields
types = {
'radar.revision.major': 'c',
'radar.revision.minor': 'c',
'origin.time_unix': 'd',
'origin.command': 's',
'stid': 'h',
'scan': 'h',
'cp': 'h',
'bmnum': 'h',
'bmazm': 'f',
'channel': 'h',
'intt.sc': 'h',
'intt.us': 'i',
'frang': 'h',
'rsep': 'h',
'rxrise': 'h',
'tfreq': 'h',
'noise': 'f',
'atten': 'h',
'nave': 'h',
'nrang': 'h',
}
…________________________________
From: Marina Schmidt ***@***.***>
Sent: Friday, March 19, 2021 11:35 AM
To: SuperDARN/pyDARNio ***@***.***>
Cc: alexchartier ***@***.***>; Author ***@***.***>
Subject: Re: [SuperDARN/pyDARNio] cFit read support missing from superdarn.py (#19)
Thank you for the feedback, I was not aware cFit is still used as FITACF is distributed more often and has a stronger support system. Due to the loss of the DSWG chair, there hasn't been much action on pyDARNio and knowing what the standard formats are.
However, you can try read_dmap() to see if it reads the file as long as it is in DMAP format.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#19 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABCK6UA4DTVTIFQ5GHHUI53TENVKPANCNFSM4ZOL3CUA>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The cFit format (described here https://superdarn.github.io/rst/superdarn/src.doc/rfc/0007.html) is not supported by the current pydarnio. cFit is used quite widely as it contains most of the same stuff as fitACF but is typically 10x smaller.
The text was updated successfully, but these errors were encountered: