-
Notifications
You must be signed in to change notification settings - Fork 18
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
Make FoV routine #449
base: develop
Are you sure you want to change the base?
Make FoV routine #449
Conversation
Commented the exclude_outofscan subroutine.
Added more descriptions to the subroutine headers
First draft of a routine to read fit binaries to stdout
Renamed file to better reflect functionality
Copied the neccessary functions from make_grid. Need these to be somewhere common in the future.
Created routine to write out fit data in a human readable format.
Updated file to not contain the duplicate grid routines and use the new write function
Created a makefile for the new procedure
Changed tabbing.
Renamed directory to match binary
Added the basis for a median fitting routine that uses fit data.
Removed unnecessary routine created for summer student.
Added writing routine that cycles through new structure.
Created a new structure that will be needed for FoV calculation.
Added routines to support new fit structure
Fixed bug in end of line.
Moved multscan.h to the inlcude folder to follow the typical rst library structure and then modified the makefile to allow it to be compiled correctly.
Updated the .gitignore to ignore the local user changes needed to install RST.
Removed lines that weren't working.
Fixed errors and warnings present during compilation. Added comments to help ensure proper local libararies are included in the future.
Removed trailing whitespace from makefiles.
Added some whitespace to separate testing and reading parts of routine.
Moved read_fit from library to tools directory, a more appropriate location.
Generalized the loading routine, to either write the data line-by-line or store the data in a multi-scan linked list.
Removed unused libraries.
Removed trailing whitespace in makefile
Added the outline of the FoV routine. To avoid adding more data structures than necessary, included all of the data and flags that will be needed for the backscatter ID code as well.
Added make/free routines for the multscan structures.
Adapted Simon's elevation routine to incude a field of view flag.
Yep, I believe that what you are supposed to do with XMLs. |
So, opening any of the files in a web browser doesn't do anything but display the code. I guess the good news is that my xml behaves the same as the rest of the xml. None of them open. Given that it seems none of us have the knowledge to resolve this issue, here's what you need to run the code: Create ascii output: make_fov -ascii Because you need to look at the range and azimuthal variations, you need to separate frequency bands for the analysis. For best results, use the TDIFF suited to the choses radar channel and frequency! To convert the dmap binary to ascii, use |
Yep, the XML business looks like a separate issue. |
To view the documentation in a web browser, I think you first need to run
You can then navigate through the html documentation in the web browser. |
No, I put all the documentation in xml since that was the RST standard.
The most important thing is FOVFLG, which is 1 for the front FoV, -1 for the rear FoV, and 0 if a FoV could not be cleanly identified. GFLG is also updated so that it is -1 if it was formerly groundscatter and doesn't look like groundscatter.
|
@aburrell Now I am confused. Here's a screenshot from following the instructions I gave in my previous comment. Is this what @pasha-ponomarenko was looking for? |
Yes, @ecbland that is it! |
@ecbland, thanks a lot, I can see this page after I run make.doc |
@aburrell, I might miss something, but there seem to be fewer fields in a binary output of make_fov than in its ASCII one, e.g., MED_* and GRPFLG, GRPNUM, GRPID are all missing. |
Yes, those fields are for future routines down the backscatter ID stream. Because the binaries are the default output for RST, I wanted them to be streamlined and only have the appropriate information. Since the ASCII output is primarily diagnostic, I added less logic steps to remove currently unused parameters.
From: pasha-ponomarenko ***@***.***>
Reply-To: SuperDARN/rst ***@***.***>
Date: Wednesday, February 9, 2022 at 17:53
To: SuperDARN/rst ***@***.***>
Cc: "Burrell, Angeline" ***@***.***>, Mention ***@***.***>
Subject: Re: [SuperDARN/rst] Make FoV routine (#449)
@aburrell<https://github.com/aburrell>, I might miss something, but there seem to be fewer fields in a binary output of make_fov than in its ASCII one, e.g., MED_* and GRPFLG, GRPNUM, GRPID are all missing.
—
Reply to this email directly, view it on GitHub<#449 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABVYF7QPA6ZDYTJI7C4M3DDU2LV6DANCNFSM5BWQM2NQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
OK, here are some preliminaries. I processed this data for frequencies between 10 and 11 MHZ using following command line options:
After that used IDL to read and plot NetCDF FOV data: |
My understanding is that the majority of the 1.5 ionospheric scatter above rage gate 40 is removed due to one of the selection criteria (exceeding the maximum virtual height?). @aburrell, please correct me if I am wrong here. |
Made changes needed to use the new channel-dependent tdiff.
Update the parameter description for the lobe dependent elevation calculation.
Added a propagation path warning for the users.
Ok, I played around with things and the main reason some things aren't working well is the propagation grouping. I applied the HAN defaults (basically the same, but Looking at the azimuthal variations, it makes sense that much of the groundscatter returns from the front FoV, since the variations are consistent across the beams. |
It's the |
I don think there is such a parameter in the fitacf structure |
@aburrell , What language did you make your plots in? Python? IDL? |
There is! Just grep "sct" in $RSTPATH/include/superdarn/*.h and you'll see which structures it's in. You can also examine the code to see how it's used. It may not be included in the user-description of the output, but it's a code structure parameter.
Python. I don't know how to plot in C, so I won't be adding this to RST. They're just RTI plots like the ones you made, but further separated by hop or propagation path. The plots you made were fine, they confirmed the code is working as it should be! |
Added the IDL tarball created when computers without IDL compile RST to the list of ignored files.
A preliminary version of the routine that automatically determines the backscatter return direction. This partially addresses #135.
Test results using a fitacf 3.0 file:
make_fov -cn a ~/Programs/Data/SuperDARN/Downloads/19960916.0400.00.han.fitacf3 > han.tst_fov
This creates an ascii file with 13727 lines and the following columns:
Re-creating one of the figures from my paper leads to similar results. This scan is from a different time that was created during various spot checks.
Before moving this from draft status we need to: