localUrl: '../page/6hk.html',
  arbitalUrl: 'https://arbital.com/p/6hk',
  rawJsonUrl: '../raw/6hk.json',
  likeableId: '3697',
  likeableType: 'page',
  myLikeValue: '0',
  likeCount: '2',
  dislikeCount: '0',
  likeScore: '2',
  individualLikes: [
  pageId: '6hk',
  edit: '1',
  editSummary: '',
  prevEdit: '0',
  currentEdit: '1',
  wasPublished: 'true',
  type: 'wiki',
  title: 'Primer on Infinite Series',
  clickbait: 'What does it mean to add things together forever?',
  textLength: '11437',
  alias: '6hk',
  externalUrl: '',
  sortChildrenBy: 'likes',
  hasVote: 'false',
  voteType: '',
  votesAnonymous: 'false',
  editCreatorId: 'ChrisHolden',
  editCreatedAt: '2016-11-02 22:04:22',
  pageCreatorId: 'ChrisHolden',
  pageCreatedAt: '2016-11-02 22:04:22',
  seeDomainId: '0',
  editDomainId: 'AlexeiAndreev',
  submitToDomainId: '0',
  isAutosave: 'false',
  isSnapshot: 'false',
  isLiveEdit: 'true',
  isMinorEdit: 'false',
  indirectTeacher: 'false',
  todoCount: '0',
  isEditorComment: 'false',
  isApprovedComment: 'true',
  isResolved: 'false',
  snapshotText: '',
  anchorContext: '',
  anchorText: '',
  anchorOffset: '0',
  mergedInto: '',
  isDeleted: 'false',
  viewCount: '43',
  text: 'What does it mean to add things together forever? While many get introduced to infinite series in Calculus class, it seems that everyone skips ahead to memorizing terminology without first motivating the subject, or considering that it's sorta weird. In reality, the long history of infinite series would suggest that the subject is subtle and strange. But by steaming ahead, memorizing the vocabulary, examples, and rules for convergence, learners miss a chance to really think about what these infinite sums really are or could be. They end up being able to more or less accurately parrot those rules, but if you speak with them a bit or overhear a conversation with others about the topic, you realize their understanding is a hollow shell. This article is a look at infinite series, adding things together forever, from more or less first principles.\n\nExample One: Zeno Crosses the Room\n----------------------------------\n\nOne of the origin stories for infinite series is attributed to the Greek Philosopher Zeno. It's a good place to start motivating why you end up dealing with infinite series and also a place from which you can begin to appreciate the need for a way of thinking about infinity that doesn't lead to pure nonsense. Although he had many paradoxes, they all boil down to certain weirdnesses that come up when you imagine space or time being infinitely divisible. Things that are obvious and simple from the point of view of everyday experience are contradicted by their analysis from the point of view of infinite divisibility. Consider the following scenario.\n\nYou want to cross the room. \n\nThat is you wish to cover one room's worth of distance. Easy enough right? You don't even need to stretch. But...(Zeno's voice) to cross the room, first you need to get halfway there. Before you cross the 2nd half of the room, you need to cross half of the 2nd half of the room. And so forth. At each stage you subdivide the remaining distance in half and cover that distance.\n\nZeno's problem was that this sequence of instants is infinite. If each turn took say 1 second, it would take infinity seconds to cross the room. From this perspective any motion—not just room crossing—appears impossible. Zeno's conclusion was that bringing infinity into the discussion, in this case dividing a given distance into infinitely many pieces, leads to nonsense and should be avoided.\n\n%note:For this and other similar reasons, the official use of infinity in mathematical arguments was postponed until the innovation of Calculus. Essentially, due to the simultaneous creation of mechanics and all the practical uses to which it could be put, the problems with reasoning with infinite sums were swept under the rug for a while. Calculus uses infinity all the time and doesn't apologize for it. Newton, Leibniz, etc. didn't figure out how to solve Zeno's paradox, they just ignored it. It wasn't until a couple centuries later that mathematicians really confronted the problem.% \n\nZeno's room crossing can be written using numbers and symbols instead of sentences, where it might look a bit more familiar as an "infinite sum".\n\n$$\\frac{1}{2}+\\frac{1}{4}+\\frac{1}{8}+\\frac{1}{16}+\\frac{1}{32}+\\ldots$$\n\nAnd we can think of its sum either from the statement of the problem (where it is clear that the sum should be 1, a whole room) or by a direct calculation of the distance remaining to cover and noting where its limit is.\n\n<table>\n<colgroup>\n<col style="text-align:left;"/>\n<col style="text-align:left;"/>\n<col style="text-align:left;"/>\n</colgroup>\n\n<thead>\n<tr>\n\t<th style="text-align:left;">Step</th>\n\t<th style="text-align:left;">Distance Covered</th>\n\t<th style="text-align:left;">Distance Remaining</th>\n</tr>\n</thead>\n\n<tbody>\n<tr>\n\t<td style="text-align:left;">0</td>\n\t<td style="text-align:left;">0</td>\n\t<td style="text-align:left;">1</td>\n</tr>\n<tr>\n\t<td style="text-align:left;">1</td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{1}{2}\\)</span></td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{1}{2}\\)</span></td>\n</tr>\n<tr>\n\t<td style="text-align:left;">2</td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{1}{2}+\\frac{1}{4}\\)</span></td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{3}{4}\\)</span></td>\n</tr>\n<tr>\n\t<td style="text-align:left;">3</td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{1}{2}+\\frac{1}{4}+\\frac{1}{8}\\)</span></td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{7}{8}\\)</span></td>\n</tr>\n<tr>\n\t<td style="text-align:left;">4</td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{1}{2}+\\frac{1}{4}+\\frac{1}{8}+\\frac{1}{16}\\)</span></td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{15}{16}\\)</span></td>\n</tr>\n<tr>\n\t<td style="text-align:left;">5</td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{1}{2}+\\frac{1}{4}+\\frac{1}{8}+\\frac{1}{16}+\\frac{1}{32}\\)</span></td>\n\t<td style="text-align:left;"><span class="math">\\(\\frac{31}{32}\\)</span></td>\n</tr>\n</tbody>\n</table>\n\nSo, at this point, we have a good reason to want to be able to write \n\n$$\\frac{1}{2}+\\frac{1}{4}+\\frac{1}{8}+\\frac{1}{16}+\\frac{1}{32}+\\ldots = 1$$\n\nMetaphysical or existential doubts notwithstanding, it just looks like we should end up with one if this process of making up half the remaining distance were to continue. In this and many other situations, its clear that adding together infinitely many things should work out to give something finite. The way we would read these symbols in words is \n\n>If you keep adding halves of halves ($\\frac{1}{2}$ + \\frac{1{4}$ and so on), you get closer and closer to 1. If somehow you could add forever, you'd have exactly one.\n\nExact and Approximate\n---------------------\n\nAt this point we should clear up one thing about *exact* versus *approximate*.  You might be thinking that, regardless of the "infinite" part of the sum, this is a clear case of "good enough for all practical purposes". At some point you get close enough to touch the wall at the end of the room. So yes, we can think of the sum as approximating one. And these infinite sums were originally very useful because they gave ways of approximating difficult to calculate things with very easy to calculate things. But there is some subtlety here in the words we use. When we say, \n\n$$\\frac{1}{2}+\\frac{1}{4}+\\frac{1}{8}+\\frac{1}{16}+\\frac{1}{32}+\\ldots = 1$$\n\nWe do not mean\n\n$$\\frac{1}{2}+\\frac{1}{4}+\\frac{1}{8}+\\frac{1}{16}+\\frac{1}{32}+\\ldots \\approx \\text{ (is approximately equal to) }1$$\n\nIt *would* be correct to say\n\n$$\\frac{1}{2}+\\frac{1}{4}+\\frac{1}{8} \\approx 1$$\n\nor also\n\n$$\\frac{1}{2}+\\frac{1}{4}+\\frac{1}{8}+\\frac{1}{16}+\\frac{1}{32} \\approx 1$$\n\nbut once we have infinitely many terms, once we are asking what would happen if the process were allowed to continue indefinitely, we are no longer taking about approximately, we are talking about exactly equal. \n\nAnd this is where people, not just young students but the many mathematical thinkers through history, have had trouble. We are used to the things related by equal signs both being simple numbers. Finite things. Not infinite processes. So what does it mean for an infinite process to be *exactly equal* to a finite number? So far in this discussion we're not yet sure. But we have a clue. We have exactly one case where we have an infinite process that has an obvious limit. We'd like to equate them. \n\nNext, let's look at a case where the infinite process, instead of telling us something we already know, helps us see something new.\n\nExample 2: Archie and the Area of a Circle\n------------------------------------------\n\nYou may have been asked to remember formulas for the circumference and area of a circle in school. \n$$ \\text{Circumference }(C) = \\pi \\cdot \\text{Diameter }(D) = 2\\pi \\cdot \\text{Radius }(r)$$\n\n$$ \\text{Area of a Circle}(A) = \\pi \\cdot r^2$$\n\nBut did you ever wonder why these formulas are true or why they both happen to have $\\pi$ in them? Did you ever wonder how we figured out the area of a round shape like the circle in the first place?\n\nWell, Archimedes did. And the way he figured it out was by creating an infinite sum. \n\nThe formula for circumference is easy. It's just a definition. Ancient Greeks and many others noticed that $\\frac{C}{D}$ was the same ratio for any circle (*WHY?*). They didn't call this $\\pi$ or even consider it a number, but we do. By definition, $\\frac{C}{D} = \\pi$, so of course $C=\\pi D$. \n\nThe real mystery is with the area formula. And this is what Archimedes did. He imagined a regular polygon inscribed within a circle. Here's a picture.\n\n![](some pic)\n\nNow, in my picture, there are 8 sides. But there's nothing special about 8. It could be 6, or 12, or a million. But...the more sides there are, the more the polygon looks like a circle, the better approximation its area is for the area of the circle. And, as it turns out, the area of the polygon is easy to compute. Moreover, computing the area of the pylon, we can see how it changes with the number of sides and how it stays the same, *and* we can see what happens to this area if we somehow had infinitely many sides. Let's look:\n\nFirst, we notice that a polygon can be split into a bunch of triangles, each of which is the same. How many? The same number as we have sides of the polygon. Just like slices of pie. Add up the area of all the slices to get the area of the original polygon.\n\n$$\\text{Area of polygon with }n \\text{ sides} = \\text{sum of } n \\text{ triangles}$$\n\nOf course, each triangle has the same area, and any triangle has area $= \\frac{1}{2} \\cdot \\text{base}\\cdot \\text{height}$. Here, the base is the side of a polygon (let's call it $s$) and the height we can call $h$. Our formula for the area of a polygon becomes:\n\n$$\\text{Area of polygon with }n \\text{ sides} = \\underbrace{\\frac{1}{2}sh+\\frac{1}{2}sh+\\ldots+\\frac{1}{2}sh}_{n \\text{ times}}$$\n\nNow, factor the $\\frac{1}{2}h$ out of the above expression to get something even nicer.\n\n$$\\text{Area of polygon with }n \\text{ sides} = \\frac{1}{2}h(\\underbrace{s+s+\\ldots+s}_{n \\text{ times}})$$\n\nAnd look, $n$ sides added together is nothing other than the perimeter ($P$) of the polygon.\n\n$$\\text{Area of polygon} = \\frac{1}{2}hP$$\n\nThis formula is true regardless of how many sides we have. All we have to do now to recover the formula for the area of the circle is to imagine what happens to all of the parts when the number of sides, the extent of the approximation, the number of terms in the underlying sum, gets larger.\n\n$$ \\text{Area of polygon} \\rightarrow \\text{Area of a Circle}(A)$$\n\n$$h \\rightarrow r$$\n\n$$P \\rightarrow C$$\n\nSo our formula becomes \n\n$$ A = \\frac{1}{2}rC = \\frac{1}{2}r(\\pi D) = \\frac{1}{2}r(\\pi(2r))=\\pi r^2$$\n\nAmazing, no?\n\nThere are *tons* of other situations where you can answer a question by putting together infinitely many pieces, situations where we would like to be able to formally write down something of the sort:\n\n$$\\text{infinite sum} = \\text{finite number}$$\n\nbut there are also obvious and not so obvious situations where doing so is nonsense. We would like to go so far as to extend our rules for algebra to be able to operate on these infinite sums (things like multiplying both sides of an equation by the same number or grouping terms), but the truth is we don't have enough information to know when that does and doesn't work out. Next we will take a look at this more general question. ',
  metaText: '',
  isTextLoaded: 'true',
  isSubscribedToDiscussion: 'false',
  isSubscribedToUser: 'false',
  isSubscribedAsMaintainer: 'false',
  discussionSubscriberCount: '2',
  maintainerCount: '2',
  userSubscriberCount: '0',
  lastVisit: '',
  hasDraft: 'false',
  votes: [],
  voteSummary: 'null',
  muVoteSummary: '0',
  voteScaling: '0',
  currentUserVote: '-2',
  voteCount: '0',
  lockedVoteType: '',
  maxEditEver: '0',
  redLinkCount: '0',
  lockedBy: '',
  lockedUntil: '',
  nextPageId: '',
  prevPageId: '',
  usedAsMastery: 'false',
  proposalEditNum: '0',
  permissions: {
    edit: {
      has: 'false',
      reason: 'You don't have domain permission to edit this page'
    proposeEdit: {
      has: 'true',
      reason: ''
    delete: {
      has: 'false',
      reason: 'You don't have domain permission to delete this page'
    comment: {
      has: 'false',
      reason: 'You can't comment in this domain because you are not a member'
    proposeComment: {
      has: 'true',
      reason: ''
  summaries: {},
  creatorIds: [
  childIds: [],
  parentIds: [
  commentIds: [],
  questionIds: [],
  tagIds: [],
  relatedIds: [],
  markIds: [],
  explanations: [],
  learnMore: [],
  requirements: [],
  subjects: [],
  lenses: [],
  lensParentId: '',
  pathPages: [],
  learnMoreTaughtMap: {},
  learnMoreCoveredMap: {},
  learnMoreRequiredMap: {},
  editHistory: {},
  domainSubmissions: {},
  answers: [],
  answerCount: '0',
  commentCount: '0',
  newCommentCount: '0',
  linkedMarkCount: '0',
  changeLogs: [
      likeableId: '0',
      likeableType: 'changeLog',
      myLikeValue: '0',
      likeCount: '0',
      dislikeCount: '0',
      likeScore: '0',
      individualLikes: [],
      id: '20350',
      pageId: '6hk',
      userId: 'EricBruylant',
      edit: '0',
      type: 'newParent',
      createdAt: '2016-11-10 00:53:31',
      auxPageId: 'math',
      oldSettingsValue: '',
      newSettingsValue: ''
      likeableId: '3693',
      likeableType: 'changeLog',
      myLikeValue: '0',
      likeCount: '1',
      dislikeCount: '0',
      likeScore: '1',
      individualLikes: [],
      id: '20345',
      pageId: '6hk',
      userId: 'ChrisHolden',
      edit: '1',
      type: 'newEdit',
      createdAt: '2016-11-02 22:04:22',
      auxPageId: '',
      oldSettingsValue: '',
      newSettingsValue: ''
  feedSubmissions: [],
  searchStrings: {},
  hasChildren: 'false',
  hasParents: 'true',
  redAliases: {},
  improvementTagIds: [],
  nonMetaTagIds: [],
  todos: [],
  slowDownMap: 'null',
  speedUpMap: 'null',
  arcPageIds: 'null',
  contentRequests: {}