Odd Variety Behavior

nusouthsc

Member
Had this happen yesterday evening. Running on South Carolina RTN, LS+. It counted like this all the way up to 1.9 with 1 engine fix. It finally got 2 engines fixed and settled down around 1.4 Variety. I've never seen it do this before but I'm a noob. Any thoughts?

 

Eric Tweet

Active Member
Could have something to do with J-Field 3.0.11.816 which was pushed from PreRelease to Release yesterday.

That release includes some changes to how variety is calculated, which may be what you're seeing.

Interestingly, the selection of the best group in Phase-1 now appears to be influenced by the group's variety too! (I've been hoping for something like that, and didn't realize it was a real thing until I looked at the notes for this release!)
 

nusouthsc

Member
Could have something to do with J-Field 3.0.11.816 which was pushed from PreRelease to Release yesterday.

That release includes some changes to how variety is calculated, which may be what you're seeing.

Interestingly, the selection of the best group in Phase-1 now appears to be influenced by the group's variety too! (I've been hoping for something like that, and didn't realize it was a real thing until I looked at the notes for this release!)
Good point. I am running Pre-Release.
 

Nate The Surveyor

Well-Known Member
I could be wrong.....
But I'm seeing sorta the same thing. Internally, it decided that it was on a wrong group, and jumped on another one. With a lower variety count.
I've really pushed mine, to try to "break it".
In challenging places, I see this sort of behavior.
N
 

nusouthsc

Member
It may be a different way of counting variety as Eric suggested. As a side note it worked amazing during this same session so I don't think it was getting bad data. I took a few REALLY tough shots right after this.
 

Eric Tweet

Active Member
I gave the new J-Field update a try today, and didn't notice any unusual variety counting. However, I also don't have any profiles which use less than 2 engines during Phase-2, so I may have missed anything new in that regard. Still, I wouldn't expect a single engine to increase variety much in the way the video shows. So I'm a bit stumped there.

However, if the main point was a sudden "jump" of variety from 1.9 down to 1.4, then yes, I believe that's been a typical result of a "rejected bucket" for some time, since each group/bucket gets its own variety counter during Phase-1. In that case, Nate's got it. The spread plots in the video may very well be indicative of an imminent bucket switch depending on the confidence guard settings, environment, etc.

For example, if things aren't going well in the current bucket during Phase-2, it'll flip to a better bucket and restart Phase-2*, counting up from the variety values accumulated in that bucket during Phase-1.

Sort of like:
Bucket #Phase-1 variety valuePhase-2 variety increase, at the time of bucket rejectionPhase-2 variety increase, at the end of phase 2
10.31.6 (you see "1.9" variety at the moment this bucket is rejected)n/a - bucket #1 rejected, and bucket #2 chosen automatically
20.2n/a (not rejected)1.2 (you see "1.4" at the end of phase 2 in this "good" bucket)

*I could be wrong in stating that it re-starts Phase-2. It may just "transfer" all of the Phase-2 data into a more appropriate bucket but still use it upon switching to that bucket, instead of discarding it. I just don't recall off the top of my head.

Indeed the recent changes to variety algorithms might make some of this more apparent, or change it in some other ways - or maybe not. Details beyond my pay grade, and I have yet to fully investigate. :p Either way, the variety increase with 1 engine does seem a bit funky. If I'm drinking one kind of soda, no matter how many cans I crack open, I'm not increasing my variety of soda!
 

Adam

Well-Known Member
5PLS
Variety is now counting up when fixes occur with the same signals with a spread of 180 seconds between the fixes. You will see it count up by .01 which did not happen before.
 
Last edited:

nusouthsc

Member
Variety is now counting up when fixes occur with the same signals with a spread of 180 seconds between the fixes. You will see it count up by .01 which did not happen before.
Thanks for the info. Is all this spelled out in the release notes? If so, are they available online?
 

Adam

Well-Known Member
5PLS
You can see the release notes on the LS in software updates. Tap Notes in upper right.
 
Top