Dave Keenan wrote: ↑Mon Aug 24, 2020 10:16 am
I'd prefer the heading "Scala archive rank" rather than "actual rank". Who's to say what's "actual" or "real" here? And I'd prefer "N2D3P9 rank" rather than 'estimated rank", since there are other ways to estimate the Scala arcive rank (like sopfr), and who knows if estimating the Scala archive rank is even the right thing to do, in the case of less popular ratios.
Yup, totally agree. Done.
While we're at it, how do you feel about "5-Rough Ratio Equivalence Class" for the column title (and section heading)? Or just "5-rough equivalence class"? Anecdotally, I think that if we had mixed the term "equivalence class" in to our discussions more earlier, I might have been less confused and/or not suggested taking the N2D3P9 of commas like I did back
here (and even as recently as my first draft of the Wiki post
here). As you said (
here and
here), each comma only notates one 5-rough ratio equivalence class, but a given 5-rough ratio equivalence class ("FREC"?) may be notated by several commas. It turns out to be at least up to four commas; I found that 35/1 is the single ratio in the Scala archives for which more three Sagittal symbol primary commas notate it (1/35C, 35S, 1/35M, 35L). There could be others. The latter pair are apotome complements, or in other words mirror images across the half apotome mirror (which is also the M|L size category bound); similarly, the former pair are Pythagorean large diesis complements, or in other words mirror images across the half Pythagorean large diesis mirror (which is also the C|S size category bound). Well actually now that I look into it, the middle two are complements too: limma complements, mirror images about the half limma mirror. Hm. There's probably a cool visualization or even interactive widget in this. Pretty much you drop one comma down and you get a hall of mirrors effect, or maybe a kaleidoscope is a better metaphor, but in any case a bunch of other commas follow, as ricocheting reflections.
Can you tell it's my first Monday without a job? Having a bit of a honeymoon period with this
I'm not actually going to build this widget. Well, at least certainly not until muuuch later.
So I'm pretty sure now that this is not the same effect as how the existing spreadsheet calculator returns 2-3 results. I had to go back to the calculator and fool around with it a bit. Almost immediately I was reminded that the calculator doesn't always return exact results. You give it 13/1 and it'll give you a
for the 35L. So that 2-3 result count really has little to do with the exact value of the ratio you're notating and more to do with its cents value and where it falls within the octave and where within that octave the double-apotome ranges emanating from each Pythagorean nominal anchor and how many of them are overlapping in that particular swath.
Now that I see the table, with its 604.5 and 329 Scala archive ranks, I think it would be good to include another column to the right which is "Scala archive occurrences". So people can see they shouldn't take too much notice of such ranks, given that they correspond to 1 or 2 occurrences.
Great idea. Done.
I'm having thoughts about a graph where I plot Scala archive occurrences against N2D3P9 notional occurrences or impled occurrences or something, but as well as not being sure what to call it, I don't know whether it should be proportional to 1/N2D3P91.37 or 1/N2D3P9_rank1.37. Any thortz?
Whoa, interesting idea. I can't figure out the motivation. Maybe I would get it if I saw it. At least, I don't get the purpose well enough to help suggest a graph name.
I
do, though, feel confident enough in suggesting proportioning to 1/N2D3P9
1.37, not 1/N2D3P9_rank
1.37. Since we used Spearman's rank correlation as our selection strategy, the ranks are our real results, and the actual N2D3P9 values are somewhat secondary, no? If you were to proportion to the actual values, I feel it may ever so slightly undercut the message we've got in the text of the article already about correlating by ranks being the proper degree of correlation given the problem.
Of course I wrote the above before you dropped a couple new exciting posts. I see that you did indeed go with 1/N2D3P9
1.37. Good stuff. Both of your charts are just dandy. Really gives the article the pizzazz it deserved!
I suppose we could also say "introducing subset" versus "introducing precision level". Thanks for consistentising that terminology. Sorry I'm still learning it.
No worries. I think "introducing" is a term I started using in my own materials for my own sense of clarity. Let me know if you like it or have a better suggestion. In many situations it can just be dropped and assumed I think.
I think you mean
, not
.
Ha! Actually, I meant
and I know why I made the mistake: because in my codebase I always have to escape backslashes so I'm used to typing it with two of them.
Also added. Last paragraph of the development / discovery section if you want to review it.
The paragraph in question is:
"After deciding upon N2D3P9, the Sagittal forum members checked Sagittal against it, to see how well they'd been served by sopfr. Each symbol in Sagittal's JI notations has a default value, or primary comma, which allows it to exactly notate ratios in a 5-rough ratio equivalence class, and based on N2D3P9, it was found that only a couple of these commas should be changed (these were among the rarest-used symbols in Sagittal). This was as expected; N2D3P9 was developed primarily in order to add new symbols to Sagittal, to enable it to exactly notate even rarer JI pitches than it already does."
The phrase "the Sagittal forum members" strikes me as very odd here, and I'd prefer it was replaced with "we" or "the authors" or "Blumeyer and Keenan".. This also makes me realise we have a mixture of active and passive voice in this article. I think we should choose one and be consistent about it. I am conflicted between the fact that it is a wiki post so in theory anyone can edit, in which case "we" or "the authors" may not be the people who did the research described, and the fact that it is intended to educate, in which case the use of "we" results in a much more engaging story.
Oof, you're right.
It looks like — generally speaking — the stuff I wrote is passive while you opted for active voice.
I expect you may find similar inconsistency in the voice used on my metallic MOS work which I've asked you to scrutinize for me; it's shared on the wiki, but definitely leans more toward a journal article than an encyclopedia entry.
Unlike Wikipedia, the Xen Wiki has a pretty inconsistent and often extremely informal tone; it doesn't struggle as much with misinformation as it does with just really messy and impenetrable information. It seems so unlikely to me that anyone would contribute to this page besides us that I think we should just embrace the storytelling "we".
Though I will point out that many instances of "we" in the article could be interpreted as the type of we acceptable in an encyclopedic setting: the we meaning "me the author, you the reader, and everyone else", often found when working through mathematical or scientific processes.
Yes. I think that while the word "we" occurs throughout the article, it's really only in the Justification section where it's clearly being used in the sense of "we the authors". It looks like it might be a lot of effort to rework the Development/Discovery section. So what I did for now was actually keep the "the Sagittal forum members" phrase, and doubled down on the passive voice in that section by removing the first sentence "How did we come up with that particular 5-rough notational-popularity ranking function?" which, if one's taking the drier and more academic angle rather than the fun & juicy storytelling angle, is basically redundant with the section heading. And then I changed the title of the Justification section to "Authors' Justification" to distinguish it and sort of give it a mandate to use the different voice.
Dave Keenan wrote: ↑Mon Aug 24, 2020 10:32 am
It's nice to have someone other than me or George post things that are Sagittal-related.
Ah, that's a good point. Okay, how about something like this:
-
Over the past couple months, @Dave Keenan and I — along with other members of the Sagittal forum — have developed a function called "N2D3P9" which can estimate the popularity of a pitch ratio. More specifically, it gives an estimated rank among 5-rough ratio equivalence classes such as 5/1, 7/1, or 55/13.
For example, N2D3P9(5/1) = 1.39, because 5/1 is the simplest possible 5-rough ratio equivalence class (besides N2D3P9(1/1) which is defined as 1). For another example, N2D3P9(77/5) = 39.21, suggesting there are approximately 38 other 5-rough pitch ratios more popular than it.
We fit our function to data from the Scala scale archives. The goal was to help choose the best commas to assign to symbols being introduced in a new and higher precision level of Sagittal's JI notation (coming soon!). You can read more on the Xenharmonic Wiki here: https://en.xen.wiki/w/N2D3P9
It would be good to point out that our approach was not able to consider all possible psychoacoustic reasons for a ratio's popularity. For example it was not able to consider whether some member of a 5-rough equivalence class might be very close in pitch to some member of another equivalence class, such as 65/64 being very close to 1/1.
Added (close to verbatim).
But I note that 31 is close to 32 (1/1) and 41 is close to 40 (5/1) etc and yet the difference between N2D3P9 and the Scala archive goes in the other direction for them, compared to what it does in the case of 65.
Oh, good point. I meant to check that but I forgot to before I had to hop in the car.
Perhaps 31 is popular because La Monte Young liked it so much. Whether I'm remembering that specific fact correctly or not, it's certainly the case that historical forces like this may have had observable effects on the scale archives. So even if we added another layer of complexity to the metric to account for such psychoacoustic phenomena as harmonic entropy or whatnot, we still couldn't account for the whole picture of ratio popularity. But perhaps this is starting to get into the territory of "probably no one would expect a notation system designer to fret about such subtleties, so it doesn't even bear mentioning."
Dave Keenan wrote: ↑Mon Aug 24, 2020 10:54 am
Perhaps "checked Sagittal against it, to see how well they'd been served by sopfr." would be better as:
"checked the ratios for the existing Sagittal symbols against it, to see how well they'd been served by the Scala archive stats and the earlier sopfr metric."
I like it. Done.