Suppose you have a torus. You triangulate it. Suppose you want to compute $H_{1}(X)$. If you let $z$ be a $1$cycle, why do you change it by a multiple of a triangle to get a homologous cycle? What is the algorithm? Why do we do this?
closed as too localized by Anweshi, Robin Chapman, Loop Space, Qiaochu Yuan, Ryan Budney Aug 4 '10 at 19:41This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question. 


I'm not completely sure if I understand the question, but I will at least try to answer the "why we do this" part. I think you're asking, "Why do we look at cycles modulo boundaries instead of just cycles?" and the answer to this is pretty simple: boundaries are uninteresting. If some $n$cycle is the boundary of an $(n+1)$simplex, then the boundary can be "pulled across" the simplex to no longer represent a "loop." In otherwords; boundaries don't represent true holes. We care about cycles that surround a hole, so that's why we look at cycles modulo boundaries. I'm not sure what you mean by "what is the algorithm." If you mean, "how do you compute homology?", then you can look that up in any algebraic topology book or wikipedia. 


One way of thinking about this is that homology gives a way to almost answer the questions you would try to answer by homotopy, but in a way that allows you to use linear algebra to get the answer. You don't get all the way  which is why homology and homotopy are actually different entities  but anything that would have been identified by homotopy certainly will be identified by homology. Key in this process is the transferral from topological arguments to algebraic arguments: we would be interested in, say, nontrivial loops under the equivalence relation given by homotopies of functions, but that's topological and potentially hard. Instead, we find correspondences in algebra to what nontrivial and loop means. Thus, we triangulate the space to get a simplicial approximation of the space, and instead of looking at bona fide loops, we look at cycles. These are like loops in that neither have nontrivial boundaries  the loops don't have nontrivial boundaries because of their geometry, the cycles don't by the way we define cycles: namely as things that are in the kernel of the boundary operator. (drawing pictures of simplicial 1cycles at this stage helps understand why these definitions give us the geometric results we want to approximate by the algebraic approach) Similarily, we want to capture homotopic loops as somehow the same. Specifically, this means we should be able to wiggle our loops around as long as they stay in the space. Once we go to the simplicial side, the wiggles have to jump across an entire simplex in one go, changing an edge to the other two edges of a triangle, say. The upshot of all this is that in order for homotopic things to be identified in homology, we need to identify anything that differs by the action of pulling a cycle across a higherdimensional simplex. Which is, once the pictures are drawn and the arguments you'd find in any introduction to algebraic topology are made, the same as taking the factor group by the image of the boundary operator. In the end, to compute $H_1(X)$, what you really compute is a complete enumeration of all possible cycles, under the condition that things you get by wiggling a cycle a little bit should be considered the same. Now, the next question would be Why do we care about homotopic functions? which is a very different question that I won't start answering here. 

