def questions_slug_poll_responses_clean_tsv_get(slug, opts = {})
      data, _status_code, _headers = questions_slug_poll_responses_clean_tsv_get_with_http_info(slug, opts)
      return data
    end
def questions_slug_poll_responses_clean_tsv_get(slug, opts = {})
      data, _status_code, _headers = questions_slug_poll_responses_clean_tsv_get_with_http_info(slug, opts)
      return data
    end
One row of response values per PollQuestion+Subpopulation concerning the given Question
 We include one TSV column per response label. See `questions/{slug}` for the Question's list of response labels, which are chosen by Pollster editors. Each row represents a single PollQuestion+Subpopulation. The value for each label column is the sum of the PollQuestion+Subpopulation responses that map to that `pollster_label`. For instance, on a hypothetical row, the `Approve` column might be the sum of that poll's `Strongly Approve` and `Somewhat Approve`. After the first TSV columns -- which are always response labels -- the next column will be `poll_slug`. `poll_slug` and subsequent columns are described in this API documentation. During the lifetime of a Question, Pollster editors may add, rename or reorder response labels. Such edits will change the TSV column headers. Column headers after `poll_slug` are never reordered or edited (but we may add new column headers). Sometimes a Poll may ask the same Question twice, leading to two similar rows with different values. Those rows will differ by `question_text` or by the set of response labels that have values.
 @param slug Unique Question identifier. For example: &#x60;00c -Pres (44) Obama - Job Approval - National&#x60;. (Remember to URL-encode this parameter when querying.)
 @param [Hash] opts the optional parameters
 @return [QuestionPollResponsesClean]