Home The Bridge

Getting to the bottom of ANDGate

I wanted to start a thread for anyone interested in investigating the AND issue. I started doing missions and quickly realized that I am not sure which ones I should be running and how. If those who did the initial gathering of info would like to share which missions they ran and the criteria so others can help, that would be great. If those people would like to run the statistics again please let the rest of us know here where to send our data to be analyzed. Any help would be greatly appreciated.
«1

Comments

  • When I saw this post I thought it looks a bit silly only be teaching one of the foundational logical gates.

    But here is the foundational post, they specify which missions they ran and every thing, its a good writeup, See https://forum.disruptorbeam.com/stt/discussion/5097/edit-final-results-2nd-experiment-results-and-shuttles-are-absolutely-bugged/p1
  • Thanks. I was just looking for that to add here for reference.
  • I had no idea about this bug. That's insane
  • [SSR] GTMET[SSR] GTMET ✭✭✭✭✭
    Basically, the rule of thumb is you want to maximize the difference between displayed actual results. The further apart they are, the easier it is to determine if the bug is fixed.
  • Peachtree RexPeachtree Rex ✭✭✭✭✭
    Basically, the rule of thumb is you want to maximize the difference between displayed actual results. The further apart they are, the easier it is to determine if the bug is fixed.

    Yes. Showing that specific bug isn't active anymore is actually pretty easy to do since you can get a display/actual difference on the order of 50%.

    However, if your intent is to show that displayed success is accurate, it will take thousands of runs to have much confidence in the numbers.
  • Capt. ChaosCapt. Chaos ✭✭✭✭✭
    It may have been intentional all along. Just because a logical AND is commutative doesn't mean that missions have to be that way. Even in the last event, the "Parent Survey" mission had AND slots with CMD/SEC and SEC/CMD. It would be nice if DB would just explain the way it is supposed to work and put this all to bed.
  • Cranky (SC) Cranky (SC) ✭✭✭✭✭
    It may have been intentional all along. Just because a logical AND is commutative doesn't mean that missions have to be that way. Even in the last event, the "Parent Survey" mission had AND slots with CMD/SEC and SEC/CMD. It would be nice if DB would just explain the way it is supposed to work and put this all to bed.

    That could be true, except for the fact that the displayed success rate is/was wrong.
  • Peachtree RexPeachtree Rex ✭✭✭✭✭
    It may have been intentional all along. Just because a logical AND is commutative doesn't mean that missions have to be that way. Even in the last event, the "Parent Survey" mission had AND slots with CMD/SEC and SEC/CMD. It would be nice if DB would just explain the way it is supposed to work and put this all to bed.

    The displayed expected % did not match the observed success rates by a significant margin. It is not possible that there wasn't a bug here.

    They DID explain how it was supposed to work and the front end success % reflected their public description.
  • Basically, the rule of thumb is you want to maximize the difference between displayed actual results. The further apart they are, the easier it is to determine if the bug is fixed.

    My wife takes me to task when I use the phrase "rule of thumb" even though there's no proof its origins are what she says. It's plausible though so I don't say it anymore. Domestic tranquility and all that.
  • I'm not aware of this "AND" bug. What is it?
  • I'm not aware of this "AND" bug. What is it?

    HAHAHAH ... all i can think of is someone joining a conference call 10 minutes late and saying...

    "i just joined... can you start again"

    Captain Kathryn Janeway i suggest you look down in the forum and you will find multiple conversations about and describing it.
  • Cranky (SC) Cranky (SC) ✭✭✭✭✭
    I'm not aware of this "AND" bug. What is it?

    It’s probably best to start with the original thread, here: https://forum.disruptorbeam.com/stt/discussion/5097/edit-final-results-2nd-experiment-results-and-shuttles-are-absolutely-bugged/p1
  • I'm not aware of this "AND" bug. What is it?

    It’s probably best to start with the original thread, here: https://forum.disruptorbeam.com/stt/discussion/5097/edit-final-results-2nd-experiment-results-and-shuttles-are-absolutely-bugged/p1

    Thanks. Dang, this is pretty serious...
  • Dirk GundersonDirk Gunderson ✭✭✭✭✭
    edited September 2018
    I'm not aware of this "AND" bug. What is it?

    It’s probably best to start with the original thread, here: https://forum.disruptorbeam.com/stt/discussion/5097/edit-final-results-2nd-experiment-results-and-shuttles-are-absolutely-bugged/p1

    The tl;dr version is that the displayed success percentage and the real success percentage for shuttle missions were not the same number due to a problem with how each crew’s skills were added together for two-skill AND slots (single-skill and OR slots were not affected). This caused countless shuttles to fail unexpectedly, unfairly depriving people of a litany of rewards over a months-long period.

    DB denied the issue existed until a lot of people came together and generated statistically valid data proving that there was a problem, at which point DB ceased acknowledging the entire debacle and then slipped what appears to be a stealth fix into a server update some time later. To date, we have never received any sort of closure, never mind an apology or restitution...and some of us at this point don’t even care about refunds on failed transmissions or Faction-only items, we just want some honest, forthright communication on the error that helps everyone, DB included, move on.
  • I'm not aware of this "AND" bug. What is it?

    It’s probably best to start with the original thread, here: https://forum.disruptorbeam.com/stt/discussion/5097/edit-final-results-2nd-experiment-results-and-shuttles-are-absolutely-bugged/p1

    The tl;dr version is that the displayed success percentage and the real success percentage for shuttle missions were not the same number due to a problem with how each crew’s skills were added together for two-skill AND slots (single-skill and OR slots were not affected). This caused countless shuttles to fail unexpectedly, unfairly depriving people of a litany of rewards over a months-long period.

    DB denied the issue existed until a lot of people came together and generated statistically valid data proving that there was a problem, at which point DB ceased acknowledging the entire debacle and then slipped what appears to be a stealth fix into a server update some time later. To date, we have never received any sort of closure, never mind an apology or restitution...and some of us at this point don’t even care about refunds on failed transmissions or Faction-only items, we just want some honest, forthright communication on the error that helps everyone, DB included, move on.

    WOW... that is bad. Affected players deserve an apology and compensation.
  • Data1001Data1001 ✭✭✭✭✭
    I'm not aware of this "AND" bug. What is it?

    It’s probably best to start with the original thread, here: https://forum.disruptorbeam.com/stt/discussion/5097/edit-final-results-2nd-experiment-results-and-shuttles-are-absolutely-bugged/p1

    Thanks. Dang, this is pretty serious...

    Not all of us think so. ;) Personally, I never had an issue with "AND" event shuttles, and don't care a single lick about the topic. But I guess I'm in the minority — at least here on this forum. 🤷‍♂️


    Could you please continue the petty bickering? I find it most intriguing.
    ~ Data, ST:TNG "Haven"
  • Cranky (SC) Cranky (SC) ✭✭✭✭✭
    I'm not aware of this "AND" bug. What is it?

    It’s probably best to start with the original thread, here: https://forum.disruptorbeam.com/stt/discussion/5097/edit-final-results-2nd-experiment-results-and-shuttles-are-absolutely-bugged/p1

    DB denied the issue existed until a lot of people came together and generated statistically valid data proving that there was a problem, at which point DB ceased acknowledging the entire debacle and then slipped what appears to be a stealth fix into a server update some time later.

    Excellent summary, thank you, mind if I copy it for future use?

    I would add - we don’t know if there’s been a stealth fix, there’s not been any serious testing. Subjectively I feel the problem still exists.
  • Dirk GundersonDirk Gunderson ✭✭✭✭✭
    I'm not aware of this "AND" bug. What is it?

    It’s probably best to start with the original thread, here: https://forum.disruptorbeam.com/stt/discussion/5097/edit-final-results-2nd-experiment-results-and-shuttles-are-absolutely-bugged/p1

    DB denied the issue existed until a lot of people came together and generated statistically valid data proving that there was a problem, at which point DB ceased acknowledging the entire debacle and then slipped what appears to be a stealth fix into a server update some time later.

    Excellent summary, thank you, mind if I copy it for future use?

    I would add - we don’t know if there’s been a stealth fix, there’s not been any serious testing. Subjectively I feel the problem still exists.

    Go for it, and change whatever you need to change.

    Personally, I still try to populate shuttles by first/second skills rather than high/low. It doesn’t always work out and sometimes a crew member’s skills are so close it doesn’t matter that much (Mirror Picard, Spider Barclay, and Mirror Cochrane come to mind)...but darn it all, it’s a matter of principle.
  • Paladin 27Paladin 27 ✭✭✭✭✭
    We really should have been testing this the last few days, the one seat federation and missions are only real definitive ones since the expected success rates can be 80% one way and 30% the other
  • WebberoniWebberoni ✭✭✭✭✭
    edited September 2018
    At this point I just want a clear explanation of how shuttle success rates are calculated, assuming the front line calculation matches the back end calculation.

    Seat #1 - SEC & MED
    Seat #2 - MED & SEC

    Option 1 - they have the same calculation, since order doesn't matter and it's 50/50 split

    Option 2 - skill #1 + (skill #2 * 0.25) -- this is the generally accepted forum approach

    Option 3 - (skill #1 * ???) + (skill #2 * ???) -- similar to option 2, but with unknown calculations for one/both skill(s)


    Another issue that comes to mind is that the auto-sort of crew still seems to be based on option 1, which could very well lead people to select crew that are not optimized for the seat/shuttle.

    Yet another issue is the impact of boosts. Depending on which option is correct, do boosts work differently when boosting skill #1 or skill #2? Does the visible boost in front line success rate correctly match the actual back end increase in success rates that the boost provides?

    Soooooo many unanswered questions...
  • DavideBooksDavideBooks ✭✭✭✭✭
    In the last event, I used the auto sort and just went with it. I also used various boosts, but my success rate was amazingly high. This is way different from before they stealth fixed (I assume) the issue. My personal belief is that you can successfully just go with it now, but no one has officially confirmed that there is no current issue. Even ignoring any comment on once having issues, it would be nice if they would at least assure us that there is no CURRENT issue.
  • WebberoniWebberoni ✭✭✭✭✭
    edited September 2018
    Prior to the apparent stealth fix, using the recommended crew was consistently giving me actual results that were about 15% lower than posted success rates. I tracked this across probably 6-10 faction/hybrid events, and even shared my results in the thread that was active at the time.

    Once I switched to the forum approved method [1+(0.25*2)], I found my actual results were within 1-2% of the expected results, sometimes even slightly higher.

    Fixed or not, I continue to the use that approach and rank my crew before each event. During last week's event all my shuttles were in the 91-93% posted success rate range, using no more than 3* skill boosts, and I think I only failed about 4 shuttles throughout the entire event. Until I get official confirmation, I'm just going to keep using the forum approach.
  • Cranky (SC) Cranky (SC) ✭✭✭✭✭
    Webberoni wrote: »
    Prior to the apparent stealth fix

    What apparent stealth fix?

    A while back they changed shuttles to say ‘mission completed’ instead of ‘failed’, but I can’t recall any explicit mention, verbally or visually, of a fix.
  • <TGE> Clifford<TGE> Clifford ✭✭✭✭✭
    Webberoni wrote: »
    Prior to the apparent stealth fix

    What apparent stealth fix?

    A while back they changed shuttles to say ‘mission completed’ instead of ‘failed’, but I can’t recall any explicit mention, verbally or visually, of a fix.

    That's why it's a "stealth" fix.

    Some of us noticed a decrease in shuttle failures related to AND slots after that change went live.
  • DavideBooksDavideBooks ✭✭✭✭✭
    Webberoni wrote: »
    Prior to the apparent stealth fix

    What apparent stealth fix?

    A while back they changed shuttles to say ‘mission completed’ instead of ‘failed’, but I can’t recall any explicit mention, verbally or visually, of a fix.

    That is the point. There is no mention of it. The AND issue apparently stopped being a problem (it seems fixed to me, anyway) at the same time they put in new visuals.
  • Cranky (SC) Cranky (SC) ✭✭✭✭✭
    edited September 2018
    Webberoni wrote: »
    Prior to the apparent stealth fix

    What apparent stealth fix?

    A while back they changed shuttles to say ‘mission completed’ instead of ‘failed’, but I can’t recall any explicit mention, verbally or visually, of a fix.

    That's why it's a "stealth" fix.

    Some of us noticed a decrease in shuttle failures related to AND slots after that change went live.

    But until DB announce it, or we spend hours of our own time performing another scientific study, it’s at best subjective. So I wish we, as those most aware of the issue in the first place, would stop assuming this has been fixed.

    My own experiences in Shuttle events have been that it’s not fixed. I have a good-high depth of crew (379 immortals) and it feels like I’m failing slightly more missions than I should. I say slightly, because I think I’m tuned now to loading slots in the workaround way when I remember to (‘most of the time’). Other times I do not.
  • Data1001 wrote: »
    I'm not aware of this "AND" bug. What is it?

    It’s probably best to start with the original thread, here: https://forum.disruptorbeam.com/stt/discussion/5097/edit-final-results-2nd-experiment-results-and-shuttles-are-absolutely-bugged/p1

    Thanks. Dang, this is pretty serious...

    Not all of us think so. ;) Personally, I never had an issue with "AND" event shuttles, and don't care a single lick about the topic. But I guess I'm in the minority — at least here on this forum. 🤷‍♂️

    I care, mostly because I am anally retentive and like the displayed success rate to match the actual success rate. Otherwise my OCD kicks in and I start getting really angry.

    If we get any compensation, I'd like a year's counseling for frustration issues and that includes the gauntlet :smiley:
    Ten Forward Loungers - Give Your Best, Get Our Best!
    Check out our website to find out more:
    https://wiki.tenforwardloungers.com/
  • Data1001Data1001 ✭✭✭✭✭
    You don't think it's serious that DB was misleading players about percentages on things that people spent real money on? And denied that anything was wrong for months? And then when confronted with proof, they released a new set of graphics for shuttle completions after a few weeks, and may or may not have stealth fixed their error, without acknowledging it ever existed?

    I mean, you be you and all that, but I find that position hard to understand.

    Like I said, I realize this is not a popular opinion around here, which is why I haven't said anything up until now. (The only reason I finally mentioned it is because every post makes it seem like every single player is up in arms about it, and I wanted to share my point of view — that there was at least one outlier. ;) ) In a nutshell, the "AND" issue that was described here on the forums never affected me. Just from my experience, I have no evidence that it ever even existed. Sure, I had the occasional streaks of shuttles failing, but I also had streaks of shutttles succeeding with relatively low percentages. By my count, it all evened out, and I've had an overall solid average rate of successes both before and after people claimed there was a "stealth fix". As to DB misleading people, I can't speak to that, because I don't know their side of things, and honestly (because it wasn't anything that mattered to me in the slightest) I always skimmed over those posts that purported to have data collected on the topic.


    Could you please continue the petty bickering? I find it most intriguing.
    ~ Data, ST:TNG "Haven"
  • Paladin 27Paladin 27 ✭✭✭✭✭
    Data1001 wrote: »
    You don't think it's serious that DB was misleading players about percentages on things that people spent real money on? And denied that anything was wrong for months? And then when confronted with proof, they released a new set of graphics for shuttle completions after a few weeks, and may or may not have stealth fixed their error, without acknowledging it ever existed?

    I mean, you be you and all that, but I find that position hard to understand.

    Like I said, I realize this is not a popular opinion around here, which is why I haven't said anything up until now. (The only reason I finally mentioned it is because every post makes it seem like every single player is up in arms about it, and I wanted to share my point of view — that there was at least one outlier. ;) ) In a nutshell, the "AND" issue that was described here on the forums never affected me. Just from my experience, I have no evidence that it ever even existed. Sure, I had the occasional streaks of shuttles failing, but I also had streaks of shutttles succeeding with relatively low percentages. By my count, it all evened out, and I've had an overall solid average rate of successes both before and after people claimed there was a "stealth fix". As to DB misleading people, I can't speak to that, because I don't know their side of things, and honestly (because it wasn't anything that mattered to me in the slightest) I always skimmed over those posts that purported to have data collected on the topic.

    What sample size of something that is supposed to be 80% coming in below 30% do you need for it to have been conclusive.

    While it was hard to get statistically significant results on event shuttles with three slots, one slot fed shuttles with an and mission had huge variations like this and were completely repeatable by all who tested them.
Sign In or Register to comment.