Learning example: using Tinderbox to track US election results

Watching the US presidential election results and building a Tinderbox document to track state electoral vote results. A learning exercise with agents & stamps.

Comments & criticisms welcome …

2024 US Election.tbx (391.0 KB)

1 Like

The first comment that comes to my mind regards one of the candidates but I’m sure that is not what you meant …

1 Like

Paul - thanks for sharing! An interesting exercise, indeed. May I ask why you put the latitude and longitude in? Or were they simply in the data from which you downloaded the state names?
Just asking out of interest.

This seems a good scenario for experimenting with Gaudí view. an aspect of the view is to use the ‘Force’ query to clouster notes of a type (size, winner, swing/not, etc.).

Great question … I realized of course that state-by-state voting returns were coming in as polls closed, and poll-closings were set by time zone across the US. So, by using the “Place” prototype for states and including GPS coordinates, I could reverse-sort the “Undecided” group of alias notes by longitude to show the expected timing of results.
I asked ChatGPT for the addresses of each state capitol in CSV format, and dragged those into Tinderbox to update the Address attribute for each state; Tinderbox automatically populated the lat/long values. Nice! (btw, I didn’t automate the updating of Address attributes–that would be a good exercise. Instead, I used cut-and-paste manually to add the Addresses for each state. This helped calm my nerves–lol).

1 Like

Yes! I may adapt this document to include US House of Representative races–still undecided at this hour–and use Gaudi view to examine clusters.

1 Like

Cool, I’d love to learn more on

  1. how you used the views in real-time
  2. what your source documents were, it would be nice to cite these, I’m assuming CSV.
    2a). I could image that that you had updated sources you could repeat the import process each time you got an update, time stemp the notes and the direct the agents to different categories so that you could maintain a timebased record. I could not say more until I saw the source docs.
  3. I noted that two of your attributes start with a lower case, e.g., @ $electoralCount, and $winner. The TBX RegEx doe snot recognize these and is not coloring them as valid attributes. I wonder if this is something that @eastgate can address in a future release or is this a part problem to solve. I also noted that a capitalized attribute gets higher sort order than lower case attribute in the User attribute list.
  4. In your states your $Rule show if ($winner=="*) ($Color-pink; ) . First, the color should be in " ". Also TBX does not have “pink” in the pallet. If you wanted a real pink you could use a HEX color, e.g. if ($winner=="") ($Color="#ff13f0"; } to get the pink’
  5. There is a ton you could do with preview, templates, and posters.
  6. Depending on source material you could make a killer timline view.
  7. I could say Table be useful for creating summaries of the data.

Oh…lots more ideas, but need to get back to work. :slight_smile:

2 Likes

Yes, this seems an obvious on to try for someone with time to tinker.

1 Like