Conversation
|
I am having issues compiling this on CentOS release 6.10. Less worrying: I am getting this warning that may or may not need to be addressed: The error (shortened for legibility): I tried added the |
codebase/superdarn/src.bin/tk/tool/make_fov.1.0/eval_groundscatter.c
Outdated
Show resolved
Hide resolved
aburrell
left a comment
There was a problem hiding this comment.
Also need to remove "#rawrite.c#" file.
codebase/superdarn/src.lib/tk/fitmultbsid.1.0/src/write_binary.c
Outdated
Show resolved
Hide resolved
codebase/superdarn/src.lib/tk/fitmultbsid.1.0/src/write_binary.c
Outdated
Show resolved
Hide resolved
|
Ok @ecbland and @egthomas I am a bit stuck on the last step: creating a binary file. I can write a binary without issue, but I can't read it back in. This could be:
I added a utility |
|
@aburrell if it is a valid
to see all of the scalar fields in the file in plain-text format, or
to see both the scalars and contents of any arrays. |
|
Ok @egthomas the good news is that the output file is valid! The bad news is I still have things I need to fix 🙀 But that's a better problem to have. |
|
@aburrell, I am a bit confused about how to test this routine. |
|
@pasha-ponomarenko before I give you detailed instructions (which I am happy to do) could you try following the examples I wrote up in the local routine docs? I think it would be good to have someone unfamiliar with the routine, but a competent RST user try to follow them so I can use your feedback to make them clearer. But to answer a quick question you raised, there are two output formats: ascii and a dmap binary. It is basically fitacf + some fields. Not all fields are used by this routine, some are there in preparation for the rest of the backscatter ID processing that I will code up following this pull. |
|
@aburrell sorry what are the new fields called? Make sure to add them to pyDARNio so people can read them :) |
|
@aburrell, do you mean this one? When I try to open it in a browser, I get this error: It might be something very simple, but ... |
|
I do mean that one! Unfortunately I do not know XML, so I made the docs by copy-pasta + add sauce. Can someone with XML knowledge take a look at that file and let me know what might be wrong? @pasha-ponomarenko do you know anyone with this skill set? @mts299 the new fields are all in the new structure housed in |
|
I will do it next week (maybe), currently cannot stare at a screen due to a concussion. Was just looking for quick things to do or ask. |
|
Apparently, there is a know issue with Github: one should never download a web file from Git as it will contain the Git webpage information as well: However, when I tried to open the same file from an RST package installed on my Linux desktop, it just showed a "raw" ASCII content and the following error(?) message: @aburrell, are you able to see the document properly in your web browser? |
No, but I don't know how to open up any of the RST xml docs. So it's a matter of me not knowing how to create something that I could open. Do you just try to open the xml files in a web browser? |
|
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. |
Added development gotchas and a summary of the FitMultBSID structures to the docs.
Added missing asterisk to the docstring.
Fixed bugs involved in loading data from multiple binary files including: - reading in multiple filenames from the command-line input, - reading in the binary header data, and - cycling through the new scans.
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.
Added the IDL tarball created when computers without IDL compile RST to the list of ignored files.
Added pointer initialization.
Added an evaluation for all elevation angles having extreme values (at the upper edge of elevation angle measurements).
Added support for extreme fov evaluation.
Updated the order in which the two fields of view are evaluated (front first) and incorporated support for extreme elevation angle evaluation.
Added a new gflg to the updated data structure. Preserves original groundscatter flag `gsct`.
Initialize a new groundscatter flag value with the original groundscatter flag value when loading scans.
Update beam evaluation to use new groundscatter flag instead of the original groundscatter flag.
Updated the groundscatter flag evaluation to alter the new flag value and maintain the old one for continuity with previous code and ease of comparison.
Some libraries that `make_fit` needs were removed during the process of resolving merge conflicts.
Fixed a typo in the structure reference.
Removed unused variables from the `make_fov` functions.
Updated the mpfit library version.
aburrell
left a comment
There was a problem hiding this comment.
@egthomas the compilation is failing for two routines that I can't see any connection to:
- rpos_v2_test.1.0
- make_sim.1.0
In both cases I think it's because the rpos.1 library is not being made correctly. Any idea why? I tried a few things without success.
|
|
||
| struct CellBSIDFlgs | ||
| { | ||
| int gflg; |
There was a problem hiding this comment.
New groundscatter flag.
| if((strcmp(aptr->name, "gsct") == 0) && (aptr->type == DATASHORT) | ||
| && (aptr->dim == 1)) | ||
| { | ||
| for(j = 0; j < aptr->rng[0]; j++) | ||
| bm->rng[slist[j]].gsct = aptr->data.sptr[j]; | ||
| } | ||
| else if((strcmp(aptr->name, "gflg") == 0) && (aptr->type == DATASHORT) | ||
| && (aptr->dim == 1)) | ||
| { | ||
| for(j = 0; j < aptr->rng[0]; j++) | ||
| bm->rng_flgs[slist[j]].gflg = aptr->data.sptr[j]; | ||
| } |
There was a problem hiding this comment.
Now with two groundscatter flags (original and new).
| { | ||
| sprintf(scan_info, "#STID"); | ||
| sprintf(bm_info, "DATE TIME INTT_US BMNUM BMAZM CPID NAVE FRANG RSEP RXRISE FREQ NOISE ATTEN CHANNEL NRANG"); | ||
| sprintf(rng_info, "RG GFLG NEW_GFLG FOVFLG FOV_PAST GRPFLG GRPNUM GRPID P_0 P_0_ERR V V_ERR W_L W_L_ERR P_L P_L_ERR PHI0 PHI0_ERR ELV ELV_LOW ELV_HIGH VH VH_ERR VH_METHOD REGION HOP DIST MED_P_0 MED_P_0_ERR MED_V MED_V_ERR MED_W_L MED_W_L_ERR MED_P_L MED_P_L_ERR MED_PHI0 MED_PHI0_ERR OPP_ELV OPP_ELV_LOW OPP_ELV_HIGH OPP_VH OPP_VH_ERR OPP_VH_METHOD OPP_REGION OPP_HOP OPP_DIST"); |
There was a problem hiding this comment.
New groundscatter output is provided alongside original.
| gsct = DataMapStoreArray(ptr, "gsct", DATASHORT, 1, &ngood, NULL); | ||
| gflg = DataMapStoreArray(ptr, "gflg", DATASHORT, 1, &ngood, NULL); |
There was a problem hiding this comment.
New groundscatter flag provided alongside original. Original keeps the name, new flag has new name.
| bm_new->rng[irg].elv = bm_old.rng[irg].elv; | ||
|
|
||
| /* Initialize the range gate flags */ | ||
| bm_new->rng_flgs[irg].gflg = bm_new->rng[irg].gsct; |
There was a problem hiding this comment.
New gflg is initialized here.
| } | ||
|
|
||
| /* Update the groundscatter flag */ | ||
| EvalGroundScatter(beam); |
There was a problem hiding this comment.
Updates to new gflag happen here.
| * - at least 3 groundscatter points are found in a 10 range gate box | ||
| **/ | ||
|
|
||
| void EvalGroundScatter(struct FitBSIDBeam *beam) |
There was a problem hiding this comment.
Updated this function to leave the original gsct flag alone.
Remove lines added during bad merge resolve.
Remove file that shouldn't be there?
Copied file back from develop.
Removed tabs from the end of each line.

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_fovThis 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: