Face the Boss w/o Auto Quest?

Auto Quest is achieved a lot, it seems. On the other hand, Face the Boss is rather uncommon. However, I can imagine a bot with failed auto code that then is able to be supported by another bot for a Face the Boss. Has this happened?

I have seen an alliance which one robot’s auto failed get the levitate and the two other robots successfully climb together for the face the boss.

it happened to both alliances at the same time during Q4 in NYTR

https://youtu.be/PMKds5_g9Fo

blue had 7031 not moving in auto, red had 20.
blue had a double climb + levitate thanks to 3996
red had a single climb + levitate + contacted 7031 in the platform zone during endgame.

1 Like


5254 has a code bug that causes us to not move in auto. At the end of the match, 1507 and 5254 climb together, which, along with levitate, achieves the “Face the Boss” RP

It has happened for sure, including this match (https://www.thebluealliance.com/match/2018mokc_qm7), though it is very uncommon

There were a few instances at WPI. Q23 had 213 dead for most of the match, but blue got levitate, a climb from 78, and another free climb for contact in the platform zone.

4905 also got a levitate + double lift in Q71 after a failed auto.

2605 was getting pretty consistent with facing the boss during the Auburn district event. There were a few matches where they didn’t get auto quest for various reasons, but did get the face the boss at the end. One match it happened in was qualification 52.

As of right now, there are 73 matches where the Autoquest flag is false and the Face the Boss flag is true.

FLOR, MIKET, and NYRO all had 7 matches where this was the case.

This has been the case several times for 1986.

Great Northern Q37 and Q51
Kansas City Q7 and Q48

Happened to us 3 times in Orlando Q12, Q32, and Q71. Its quite painful.

Q29and Q42at Orlando also make the list and are interesting because they didn’t involve a triple climb, but actually were created by penalties from an opposing robot during the endgame.

This happened to my team, 3512, @ LA in Qual 14:

Although in this case, our third alliance partner never made it to the match so we had no hope of getting the auto quest ranking point. I will say that we were able to get some autonomous going for 848 by working with their programmers before the match, so that was neat to see! And we still won the match thanks to levitate and our ramps!

Edit: I just noticed we got 3 Fouls in that match lol. Whoops :stuck_out_tongue:

Happened in match 74 at Mt. Vernon with 1318 and 4469 climbing and 4173 using the levitate.

I actually count 168 matches so far… with 169 occurrences. The only match where it occurred for both alliances was 2018nytr_qm4.


2018alhu_qm1       
2018alhu_qm20      
2018alhu_qm25      
2018arli_qm19      
2018arli_qm4       
2018ausp_qm23      
2018ausp_qm51      
2018ausp_qm57      
2018ausp_qm67      
2018azfl_qm2       
2018azfl_qm30      
2018azfl_qm80      
2018capo_qm14      
2018capo_qm38      
2018capo_qm6       
2018capo_qm72      
2018casd_qm15      
2018casd_qm26      
2018casd_qm31      
2018casd_qm35      
2018casd_qm51      
2018casd_qm86      
2018ctsct_qm16     
2018ctsct_qm18     
2018ctsct_qm24     
2018ctsct_qm52     
2018ctsct_qm7      
2018ctwat_qm20     
2018ctwat_qm24     
2018ctwat_qm32     
2018ctwat_qm34     
2018flor_qm10      
2018flor_qm12      
2018flor_qm29      
2018flor_qm32      
2018flor_qm42      
2018flor_qm49      
2018flor_qm71      
2018ilpe_qm38      
2018ilpe_qm41      
2018isde1_qm49     
2018isde2_qm23     
2018isde2_qm30     
2018isde2_qm36     
2018isde2_qm49     
2018isde3_qm6      
2018isde4_qm57     
2018marea_qm20     
2018marea_qm59     
2018marea_qm80     
2018mawor_qm23     
2018mawor_qm55     
2018mawor_qm71     
2018mdoxo_qm40     
2018mdoxo_qm44     
2018miesc_qm2      
2018miesc_qm23     
2018miesc_qm68     
2018migib_qm17     
2018migib_qm32     
2018mike2_qm22     
2018mike2_qm73     
2018miket_qm51     
2018miket_qm57     
2018miket_qm67     
2018miket_qm69     
2018miket_qm70     
2018miket_qm74     
2018miket_qm75     
2018milin_qm4      
2018milin_qm68     
2018mimil_qm2      
2018mimil_qm4      
2018mimil_qm40     
2018mimil_qm51     
2018misjo_qm20     
2018misjo_qm4      
2018misjo_qm44     
2018misjo_qm60     
2018misou_qm3      
2018misou_qm35     
2018miwat_qm31     
2018mndu_qm2       
2018mndu_qm20      
2018mndu_qm41      
2018mndu_qm55      
2018mndu2_qm16     
2018mndu2_qm72     
2018mndu2_qm83     
2018mokc_qm48      
2018mokc_qm7       
2018mokc2_qm55     
2018mokc2_qm70     
2018mokc2_qm77     
2018ndgf_qm26      
2018ndgf_qm31      
2018ndgf_qm37      
2018ndgf_qm51      
2018ndgf_qm55      
2018ndgf_qm83      
2018nhgrs_qm40     
2018njbri_qm69     
2018njbri_qm7      
2018njfla_qm63     
2018nyro_qm20      
2018nyro_qm24      
2018nyro_qm32      
2018nyro_qm44      
2018nyro_qm47      
2018nyro_qm61      
2018nyro_qm70      
2018nytr_qm14      
2018nytr_qm18      
2018nytr_qm27      
2018nytr_qm28      
2018nytr_qm4       
2018nytr_qm47      
2018nyut_qm9       
2018ohmv_qm27      
2018ohmv_qm35      
2018onbar_qm31     
2018onosh_qm21     
2018onosh_qm45     
2018onto1_qm5      
2018onto1_qm55     
2018onto1_qm57     
2018onto1_qm63     
2018orore_qm47     
2018orore_qm57     
2018orwil_qm21     
2018orwil_qm26     
2018orwil_qm57     
2018paphi_qm1      
2018paphi_qm54     
2018pawch_qm13     
2018pawch_qm28     
2018pawch_qm3      
2018pawch_qm41     
2018pawch_qm76     
2018qcmo_qm21      
2018qcmo_qm35      
2018qcmo_qm44      
2018qcmo_qm64      
2018qcmo_qm79      
2018scmb_qm24      
2018scmb_qm95      
2018shmi_qm55      
2018txda_qm28      
2018txda_qm36      
2018txda_qm68      
2018txda_qm78      
2018txho_qm78      
2018txlu_qm14      
2018txlu_qm18      
2018utwv_qm44      
2018utwv_qm48      
2018vagdc_qm67     
2018vahay_qm41     
2018vahay_qm50     
2018vapor_qm49     
2018vapor_qm62     
2018waahs_qm22     
2018waahs_qm52     
2018waahs_qm58     
2018waahs_qm59     
2018wamou_qm30     
2018wamou_qm54     
2018wamou_qm74 

As the above lists states, NE Waterbury Qualification 20: https://www.thebluealliance.com/match/2018ctwat_qm20

Whoops, I was counting unique match numbers, not unique event + match numbers.

I think that the probability an alliance successfully completes Auto Quest is fairly independent from the probability that same alliance completes Face the Boss, so let’s use MATH!

A – Auto quest successful
B – face the Boss successful
A’ – negation of A, i.e. Auto quest unsuccessful
B’ – negation of B, i.e. face the Boss unsuccessful

So we’re going to be looking for matches which meet the criteria A’ AND B

From TBA Insights we can get A and B (have to combine qual and elims data):

A = 0.401
B = 0.049

which means that we can get A’ and B’ (A’=1-A, B’=1-B):

A’ = 0.599
B’ = 0.951

Then multiplying A’ and B gives us:

A’*B = 0.029

This relies on the probability of success of A and B being completely independent which may or may not be a good assumption. We can quickly check if it was by calculating the value for A AND B, which TBA Insights lists as “Unicorn Matches”

A*B = 0.020

TBA Unicorn Matches = 0.022

Not too shabby.

An even better test would be comparing it to someone who actually scraped all the data:

169 instances / 7094 matches = 0.029
My value was 0.029 as well. Neat.

More decimal places:
True = 0.02869
Calc = 0.02948

I think it makes sense that A*B would be further from the true value than A’*B, since we’re not exactly flipping a coin and rolling a die (elims matches don’t have random participants, not completing Auto Quest may say something about that alliance, etc.)

Just out of curiosity, was any of these true triple climbs? (IE no levitate or end-game-penalty)

2018orwil_qm26

At least this one was. It was our only triple climb, and our auto hadn’t been cooperating the entire tournament. Two of our other double climbs made this list during that week 2 event.

https://www.thebluealliance.com/match/2018orwil_qm26