32.3 Table to Ordered Pairs
Converting a table of values into ordered pairs involves pairing each input with its corresponding output to represent relationships in coordinate form.
Table to Ordered Pairs is the procedure for converting an input-output table into a list of ordered pairs by extracting the input and output values from each row and combining them into a single coordinate pair, then collecting every resulting pair into a complete list. This procedure moves a function's information from the row-and-column layout of a table into the more compact ordered pair list format discussed under ordered pair list, without changing any of the underlying input-output associations the table originally recorded.
Because each row of a table already contains exactly the information needed to form one ordered pair, this conversion is largely a matter of careful extraction and combination rather than any new calculation, making accuracy in reading the table correctly the central concern throughout the procedure.
Table Row Input Extraction
Locating the Input Value in Each Row
For every row of the table, the input value is located in the column or position designated for inputs, matching the layout conventions described under the structure of an input-output table.
Extracting Inputs One Row at a Time
Input extraction proceeds row by row, reading only the input value from each row before moving on to the next, keeping the process organized and reducing the chance of mixing up values from different rows.
Recording Extracted Inputs Accurately
Each extracted input value is recorded exactly as it appears in the table, preserving its sign and any fractional or decimal form, since an inaccurately transcribed input would misrepresent the row it was taken from.
Table Row Output Extraction
Locating the Output Value in Each Row
For every row of the table, the output value is located in the column or position designated for outputs, taken from the same row as the input value extracted in the previous step.
Extracting Outputs One Row at a Time
Output extraction follows the same row-by-row approach as input extraction, working through the table systematically so that no row's output value is accidentally skipped or duplicated.
Recording Extracted Outputs Accurately
Each extracted output value is recorded exactly as it appears in the table, with the same care given to sign and numerical form as described for input extraction, since the accuracy of the eventual ordered pair depends on both of its coordinates being correctly transcribed.
Coordinate Pair Formation
Combining an Input and Output Into a Pair
Once an input and its corresponding output have both been extracted from the same row, they are combined into a single ordered pair, written with the input as the first coordinate and the output as the second coordinate, consistent with the input-first convention described under function notation structure.
Preserving Correct Order Within the Pair
Because an ordered pair's meaning depends on which coordinate comes first, the input must always be placed first and the output second, since reversing this order would misrepresent the row as a different relationship than the one the table actually recorded.
An Example of Coordinate Pair Formation
A table row listing input and output is combined into the ordered pair , directly reflecting the pairing shown in that row.
Pair Collection from All Rows
Repeating the Process for Every Row
Coordinate pair formation is repeated for every row present in the table, producing one ordered pair for each row rather than stopping after only the first few rows have been converted.
Assembling the Pairs Into a Single List
As each ordered pair is formed, it is added to a running list, ultimately assembling every pair from the table into a single collection that together represents the entire function shown by that table.
Maintaining Consistent Ordering in the Collected List
Assembling the pairs in the same order the rows appeared in the original table produces a collected list that mirrors the table's own organization, though the final list remains a valid representation of the same relation regardless of the order in which its pairs are listed.
Table and Pair Count Agreement
Comparing the Number of Rows and Pairs
Once the collection is complete, the total number of ordered pairs produced should be compared against the total number of rows in the original table, since a correctly performed conversion produces exactly one pair for every row.
Why Count Agreement Confirms Completeness
Count agreement provides a straightforward check that no row was skipped and no extra pair was accidentally introduced during the conversion, since any mismatch between the two totals indicates that something went wrong somewhere in the extraction or formation process.
Resolving a Count Mismatch
If the counts do not agree, the table and the collected list are compared side by side, row by row, until the specific row responsible for the discrepancy is located and the missing or extra pair is corrected.
Missing Table Row Detection
Recognizing When a Row Has Been Skipped
A missing row is detected when the final collected list of ordered pairs contains fewer entries than the table has rows, or when a specific input value known to be in the table cannot be found among the first coordinates of the collected pairs.
Tracing Back to the Source of the Omission
Once a missing row is suspected, the original table is reviewed row by row against the collected list to identify exactly which row's input and output were never extracted and converted into a pair.
Correcting a Detected Omission
Correcting a detected omission involves extracting the input and output from the missed row, forming the corresponding ordered pair following the same coordinate pair formation process used for every other row, and adding it to the collected list in its proper place.