BuzzerBeater Forums

The following shots from (90296919) are all 'SPINNY'. As you can see there is always reference to open space. It is clearly a jump shot, if I had to guess it's probably a turnaround jumper. Fall away is a fade away and I'm not 100% if it should be considered an inside shot or a jumper. Both have 0% chance of going in when unguarded (see very last example).

Spinny

1 7:05 14 — 8 P. Cuvelier (A) loses his man and uses the open space to set his feet before taking a jump shot, guarded closely by M. Bello (H). Scored.

P. Cuvelier (A) loses his man and uses the open space to set his feet before taking a jump shot with M. Bello (H) guarding him closely. Shot missed.

1 3:26 22 — 18 E. Župan (A) loses his man and uses the open space to set his feet before taking a jump shot over K. Hunt (H). Scored.

2 7:55 35 — 32 S. Čalić (A) loses his man and uses the open space to set his feet before taking a jump shot, guarded closely by D. Meek (H). Shot missed.

3 11:03 44 — 48 B. Tamariz Vargas (A) loses his man and uses the open space to set his feet before taking a jump shot with B. Stanimirović (H) guarding him closely. Shot missed.

Fall away

1 1:53 24 — 20 P. Gorzel (H) can't shake his defender and is forced to shoot a fade-away, guarded closely by P. Cuvelier (A). Scored.

1 0:49 24 — 22 T. Bajlec (A) fakes before attempting a fade-away jumper with S. Bowens (H) guarding him closely. Shot missed.

3 10:06 46 — 48 P. Cuvelier (A) can't shake his defender and is forced to shoot a fade-away, guarded closely by M. Bello (H). Scored.

4 10:46 73 — 73 P. Cuvelier (A) fakes before attempting a fade-away jumper with M. Bello (H) guarding him closely. Scored.

4 3:54 81 — 79 D. Meek (H) sparks the offense with a pass to B. Isom (H). B. Isom (H) shoots while falling back from the basket. Shot missed.

Amazing work, mate! Thumbs up!

Maybe as a next step you can distribute those shots by position. That (if at all possible) will be a huge breakthrough in terms of understanding the game engine. The usage of semi-blank lineups will probably make it nearly impossible though.

From what I`ve seen quite a lot of teams use it. It was used in the final game last season as well.

Holy Mother of All Things Good in this World!

I was following along in the Princeton thread and wishing there was something like for the other tactics. I've started to give Princeton a try based off those stats and currently going to try out Inside ISO tonight in my CUP.

I hope you continue the discussion in this thread. Looking forward to hearing everyone's thoughts. I had heard that Inside ISO ends up taking a good number of threes because of kickouts. My first look at these findings was to confirm that Inside ISO does indeed have a good share of the attempts being from beyond the arc, but surprisingly it's got a low rate of assisted attempts.

I'll have to review the other offenses to see how it really compares still, but it was surprising nonetheless.

Do you by chance happen to have the defense these offenses faced?

Yes for all games I both have the play by play (where there is no information on the tactics) and the boxscore, which I download through the BBApi. In the boxscore I get all kinds of information on tactics, GDP, effort etc.

I need the boxscore data both to check that the totals of the play by play are correct and to allocate the steals from one team to the players of the other team as turnovers, because the play by play does not track who gets stripped.

However as you can see from the following pic, boxscores in BBApi have all the info on the game and all the traditional stats:
http://tinypic.com/r/2emieer/9

There is both delta effort and (TIE vs CT = -2, Normal vs TIE = +1 etc), defense used and GDP focus and pace (N/A = not used GDP).

Last edited by Lemonshine at 4/19/2018 4:54:40 AM

Making tables by position will take quite a lot of time. The overall table runs quite fast but when you add more and more criteria (like the tactic or the position who took the shot) it slows the code quite noticeably. I need to rework the code before I can do this, so that the dataset used for each query is as small as possible.

Note that the boxscore will not tell you where a player was playing when he took a shot (although most players only play at 1 position) while from the pbp I build the lineups for each action that happens (from starting lineup following with swaps and substitutions) so I could actually do this properly (i.e. if a player has 24 minutes at PG and and 24 at C I know which shots were taken at PG and which were taken at C).

I need to rewrite the code because the pbp dataset has 121k lines (most games have between 450-550 lines) and 56k are shots or FTs.

Last edited by Lemonshine at 4/18/2018 4:54:06 PM