Excellent tutorial in excell! A top notch instruction video. Easy to follow and understand, even when your'e allergic to a spreadsheet!
@sdkweber9 ай бұрын
Thank you!
@billr46772 жыл бұрын
I’m so excited for this file. I knew there was a lot of information locked away in the excel doc of the LabRadar. Thanks again for your assistance. I’ll be sure to share my data once I’ve populated it. I’ve got so much raw data it’s not even 🤩
@sdkweber2 жыл бұрын
Super Bill. I look forward to seeing your results. Thank you for watching and posting!
@bartomiejhrehorowicz4418 Жыл бұрын
Pure gold, thank you! It shows how Labradar can be more powerfull tool, also I like the way you explain.
@sdkweber Жыл бұрын
Thank you very much!
@LiquidColourDesignBallycarry Жыл бұрын
Outstanding thank u so much, looking forward to working on this myself.
@sdkweber Жыл бұрын
You are welcome, and thank you for watching.
@andywilson5049 Жыл бұрын
Thank you for your work and sharing this helpful information
@sdkweber Жыл бұрын
You are welcome Andy. And thank you for watching.
@Dwayne78342 жыл бұрын
Thanks for the video and information.
@sdkweber2 жыл бұрын
You are welcome. Thanks for watching Dwayne.
@BobJones-zw3ui Жыл бұрын
Thank you.
@sdkweber Жыл бұрын
You are welcome. We will be releasing another video on further analysis of Labradar data to calculate Drag Coefficients. That video will be out in a few weeks. Thakns for watching and posting.
@paulg.2201 Жыл бұрын
A brilliant video/tool for the enthusiast, who wants this level of detail, analysis. Do you have a link that gives G7 output, please?
@sdkweber Жыл бұрын
Thanks Paul. I would very much like to include an estimated G7 but cannot find the equation to calculate it. I believe it is a more complicated calculation requiring data that I do not have available in the spreadsheet. I did find this online though and will look into it myself www.longrangehunting.com/threads/labrabaco-a-g7-bc-calculator-from-labradar-tracks.269557/
@Nonedw2 жыл бұрын
Great video and run down. I wonder how this data would change if you took the readings out to say 200yds? Also, the BCs seem lower than what Brian Litz’s data shows. Be interesting to see how much better your first round hits are at 1000k yds using data derivatives from their Labradar.
@sdkweber2 жыл бұрын
I would like to try it with data out to and beyond 200 yards as the results should be even better. The problem is I rarely get a reading past 150 yards with the labradar. I suspect Litz's data is from a more powerful doppler system. I am hoping to use this data to "true" my BC for these rifles and improve my drop tables. Thanks for watching and posting.
@ClaytonMacleod Жыл бұрын
Your SNR values seem on the low side to me. A 3D-printed sight add-on to help align the unit to the target can result in a much better signal and give you better tracking for longer distances. For comparison, my readings are starting off in the 42-43 dB range for 22 LR bullets and doesn’t seem to start having trouble tracking until the 90-100 metre range. I believe the reason you can see tracking data past where your target is is because the radio waves easily pass through the target and backer material and so can still reach and reflect off the bullet just fine. If the SNR is still in the usable range past that point the data should still be good. But it is probably uninteresting by that point anyway. And from the looks of it, is already below your acceptable SNR floor anyhow. By the way, this seems like a huge amount of busy-work. It is begging for a python script to do all of this for you automatically. Maybe I can find some free time to do just that soon here. Should be able to simply run a script from the LabRadar directory and automatically do this for all subdirectories that haven’t been processed yet. Save a ton of time.
@sdkweber Жыл бұрын
Good ideas Clayton. The sighting plane on the LabRadar is very short, maybe 1.5" at best and based on the user manual, aligning the unit to the target is important. Tracking the bullet after it passes through the target is not of interest as the bullet will likely be yawing and losing stability so discarding those values is fine. I am very interested in your idea to use a Python script to create and populate a CSV file with the necessary calculations. That would be a great benefit to the shooting community. If you ever have time to do this, please post a link so others can download and use it. It could make for a very interesting follow up video too. Thanks for the post and for watching.
@ClaytonMacleod Жыл бұрын
@@sdkweber Just finishing it up now. I’m just wondering how to handle the target distance, as that wouldn’t always be the same, necessarily. Maybe have to put it in a target-distance.txt file in the series subdirectory, and if it exists, cull anything beyond the number contained in the file. With 22 LR and >15 dB I’m finding the drop in SNR is enough anyway, heh. Even in the >12 dB data the number of data points beyond the 77 m I was shooting at are practically irrelevant anyway. But it may still be a good idea to have the option to limit it to target distance. Shouldn’t be hard to add. I currently have it outputting a PNG file with a scatter plot for BC vs SNR and one for BC vs distance, plus the same stats you had. And this is output into a single 1920x1080 PNG. It actually outputs two of these, one for >12 dB and one for >15 dB. I prefer the latter. I also have it ignoring anything
@sdkweber Жыл бұрын
@@ClaytonMacleod That is cool! If you would share that script I would like to do a video on it. If there is a GUI with the script or someway for user input, the target distance could be set that way. I too am thinking about a longer sighting and I wonder if having something that (in storage) lies parallel to the labradar but then lifts (unlocks) and rotates to be perpendicular to the labradar might work. This could give about a 12" plane. Even having a sighting plane that clamps gently to the top of the labradar and sits in the existing sighting plane groove could woork
@ClaytonMacleod Жыл бұрын
@@sdkweber Well, I've currently got it looking for a target-distance.txt file in each subdirectory so that you can have different target distances for each series. If it finds one, it will use that to limit the upper end of the data. It is just a text file that you put a number inside of to tell it what the limit is. It doesn't need a unit, as it takes the unit you used from your shot data. It might be easier to simply use a command line parameter and use that for all series, but this would mean you couldn't have different values for different series unless you made different directory trees for each target distance. If you have a ton of data to process that is at one distance then that would be more efficient than having to put a copy of the target-distance.txt file into each subdirectory. When you have some new data it shouldn't be as big of a deal to put a handful of new target-distance.txt files in the new series subdirs. Both methods have pluses and minuses, I suppose. Maybe a combination of the two methods would be better. A separate directory tree for each target distance, and make it check for a single target-distance.txt file in the main subdirectory and use that for all series in that tree. I suppose most people only shoot at a handful of different distances, so that might be the most handy. Not a big deal to make small alterations to act each of those ways and just have a separate script to use for however one thinks will be better for them, for that matter.
@666-y8w2 жыл бұрын
This video just took all the fun out of using a labradar. Just dragged on and was not that useful of information.
@billr46772 жыл бұрын
I’d disagree; he has unlocked what already should have been there. How is having an accurate BCs a bad thing? LabRadar is a tool not a toy to have “fun” with. Well not for me.
@patricktoms51192 жыл бұрын
Advanced use cases, or not always fun… It’s about squeezing every bit of performance from a tool, that you can.