Normal forms: Difference between revisions
Cmloegcmluin (talk | contribs) remove partially incorrect and no longer relevant statement about IRREF |
Cmloegcmluin (talk | contribs) →Canonical form: bring in part about not removing trailing dimensions |
||
| Line 34: | Line 34: | ||
# First, [[defactor]] it<ref>Historically, this step was not explicitly recognized as necessary for normal forms. It is quite likely that the vast majority of normal forms found on the wiki are not enfactored, but specifically defining canonical form to include this requirement is an important step toward ensuring that, which will prevent redundant temperaments from being catalogued. In various domains, normal forms are often required to be unique, however, canonical forms are required to be unique even more often that normal forms are; according to [https://en.wikipedia.org/wiki/Canonical_form the Wikipedia page for canonical form], 'the distinction between "canonical" and "normal" forms varies from subfield to subfield. In most fields, a canonical form specifies a unique representation for every object, while a normal form simply specifies its form, without the requirement of uniqueness.' This is the rationale behind defining "canonical" as opposed to merely "normal". To be more specific, The HNF does provide a unique representation of ''matrices'', i.e. from a perspective of pure mathematics, and so you will certainly find throughout mathematical literature that HNF is described as providing a unique representation, and this is correct. However, when applied to the RTT domain, i.e. to ''mappings'', the HNF sometimes fails to identify equivalent mappings as such. | # First, [[defactor]] it<ref>Historically, this step was not explicitly recognized as necessary for normal forms. It is quite likely that the vast majority of normal forms found on the wiki are not enfactored, but specifically defining canonical form to include this requirement is an important step toward ensuring that, which will prevent redundant temperaments from being catalogued. In various domains, normal forms are often required to be unique, however, canonical forms are required to be unique even more often that normal forms are; according to [https://en.wikipedia.org/wiki/Canonical_form the Wikipedia page for canonical form], 'the distinction between "canonical" and "normal" forms varies from subfield to subfield. In most fields, a canonical form specifies a unique representation for every object, while a normal form simply specifies its form, without the requirement of uniqueness.' This is the rationale behind defining "canonical" as opposed to merely "normal". To be more specific, The HNF does provide a unique representation of ''matrices'', i.e. from a perspective of pure mathematics, and so you will certainly find throughout mathematical literature that HNF is described as providing a unique representation, and this is correct. However, when applied to the RTT domain, i.e. to ''mappings'', the HNF sometimes fails to identify equivalent mappings as such. | ||
And the critical flaw with HNF is its failure to defactor matrices, and this is because dividing rows is not a permitted elementary row operation when computing the HNF. See: https://math.stackexchange.com/a/685922 The canonical form as described here ''does'' defactor matrices, and therefore it delivers a truly canonical result.<br><br>There is also a rarely mentioned Hermite Canonical Form, or HCF, described here: http://home.iitk.ac.in/~rksr/html/03CANONICALFACTORIZATIONS.htm, which sort of combines the HNF's normalization constraint and the [[Matrix_echelon_forms#RREF|RREF]]'s reduced constraint (all pivots equal 1, all other entries in pivot columns are 0, both above and below the pivot), but we didn't find it useful because due to its constraint that all pivots be 1, it does not preserve periods that are genuinely unit fractions of an octave (at first glance, when a pivot is not equal to 1, it might trigger you to think that the mapping is enfactored. But temperaments can legitimately have generators that divide primes evenly, such as 5-limit Blackwood, {{ket|{{map|5 8 0}} {{map|0 0 1}}}}, which divides the octave into 5 parts. So any form that enforces pivots all be 1's, such as HCF and RREF, would fail this criteria.) It also doesn't qualify as an echelon form, which becomes apparent only when you use it on rank-deficient matrices, because it doesn't require the rows of all zeros to be at the bottom; instead it (bizarrely, though maybe it's related to how the SNF requires all pivots exactly along the main diagonal) requires the rows to be sorted so that all the pivots fall on the main diagonal.</ref>. Note that if the matrix was not [https://en.wikipedia.org/wiki/Rank_(linear_algebra)#Main_definitions full-rank], this will result in the elimination of some rows. We now have an <span><math>r×d</math></span> matrix, with <span><math>r</math></span> rows where <span><math>r</math></span> is the ''rank''. | And the critical flaw with HNF is its failure to defactor matrices, and this is because dividing rows is not a permitted elementary row operation when computing the HNF. See: https://math.stackexchange.com/a/685922 The canonical form as described here ''does'' defactor matrices, and therefore it delivers a truly canonical result.<br><br>There is also a rarely mentioned Hermite Canonical Form, or HCF, described here: http://home.iitk.ac.in/~rksr/html/03CANONICALFACTORIZATIONS.htm, which sort of combines the HNF's normalization constraint and the [[Matrix_echelon_forms#RREF|RREF]]'s reduced constraint (all pivots equal 1, all other entries in pivot columns are 0, both above and below the pivot), but we didn't find it useful because due to its constraint that all pivots be 1, it does not preserve periods that are genuinely unit fractions of an octave (at first glance, when a pivot is not equal to 1, it might trigger you to think that the mapping is enfactored. But temperaments can legitimately have generators that divide primes evenly, such as 5-limit Blackwood, {{ket|{{map|5 8 0}} {{map|0 0 1}}}}, which divides the octave into 5 parts. So any form that enforces pivots all be 1's, such as HCF and RREF, would fail this criteria.) It also doesn't qualify as an echelon form, which becomes apparent only when you use it on rank-deficient matrices, because it doesn't require the rows of all zeros to be at the bottom; instead it (bizarrely, though maybe it's related to how the SNF requires all pivots exactly along the main diagonal) requires the rows to be sorted so that all the pivots fall on the main diagonal.</ref>. Note that if the matrix was not [https://en.wikipedia.org/wiki/Rank_(linear_algebra)#Main_definitions full-rank], this will result in the elimination of some rows<ref>Note that canonicalizing a mapping does not remove trailing ''dimensions'' with only zeros.<br><br>In the case of a mapping, this would take the form of an extra column of all zeros to the right of any non-zero entries, or in other words, an unmapped prime higher than other mapped prime. For example you could have {{ket|{{map|1 0 -4 0}} {{map|0 1 4 0}}}} which is just 5-limit meantone but represented in the 7-limit even though prime 7 is not used.<br><br>And for a comma-basis the form this would take is rotated 90 degrees: a row of all zeros below all other nonzero entries, e.g. {{bra|{{vector|4 -4 1 0}}}}.<br><br>The reason these additional zeros should be preserved and these temperaments be treated as different from their untrimmed counterparts is made clear when we consider the difference in the duals. For a comma-basis, the extra dimension implies the presence of extra generators that are unbound to the other generators. For example, a basis for the anti-null-space of {{bra|{{vector|4 -4 1}}}}, or in other words its mapping, as we know well is {{ket|{{map|1 0 -4}} {{map|0 1 4}}}}. But that is not a basis for the anti-null-space of {{bra|{{vector|4 -4 1 <span><math>\color{red}0</math></span>}}}}; the mapping for that comma-basis would have to be {{ket|{{map|1 0 -4 <span><math>\color{red}0</math></span>}} {{map|0 1 4 <span><math>\color{red}0</math></span>}} {{map|<span><math>\color{red}0</math></span> <span><math>\color{red}0</math></span> <span><math>\color{red}0</math></span> <span><math>\color{red}1</math></span>}}}}.</ref>. We now have an <span><math>r×d</math></span> matrix, with <span><math>r</math></span> rows where <span><math>r</math></span> is the ''rank''. | ||
# Then, put this result into HNF. | # Then, put this result into HNF. | ||