Xenharmonic Wiki talk:Conventions: Difference between revisions

← Older edit

VisualWikitext

@@ Line 1: / Line 1: @@
+{{High priority}}
 == [[List model]] ==
@@ Line 85: / Line 87: @@
 :: I'm starting to think "edo" and "n-edo" represent a good compromise, especially considering [[User:FloraC|FloraC]]'s argument. I'm also thinking of a compromise: presenting "EDO or edo" in that order on the [[EDO]] page to insist on the fact that it's an acronym, but choosing "edo" and "n-edo" as a convention for readability on the Wiki. That might seem contradictory, but it allows one to pass from the full term to the acronym to the anacronym more smoothly, from my point of view. [[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 18:10, 19 July 2021 (UTC)
+== Math conventions ==
+There are currently no real conventions for mathematical notation. Since a lot of math pages involve linear algebra, I propose the following:
+: Open up any introductory linear algebra textbook. Follow the notation that is used there.
+In practice this means:
+* Matrices are uppercase Roman letters: <math>M</math>.
+* Vectors (whether column or row) are usually lowercase Roman letters: <math>u</math>.
+* When there is potential confusion with scalars, they can be made boldface: <math>\mathbf{u}</math>, or get an arrow: <math>\overrightarrow{u}</math>.
+* Inner product can be notated: <math>u^\mathsf{T}v</math> or <math>\left\langle u,v \right\rangle</math>.
+* The p-norm is: <math>\| u \|_p</math>, when no p is given, 2-norm is assumed.
+* When writing a column vector inside text, just transpose it: <math>w =\begin{bmatrix}
+w_1 & w_2 & w_3
+\end{bmatrix}^{\mathsf{T}}</math>.
+The wiki has Mathjax support, use it!
+: EDIT: This also means getting rid of bra-ket notation, by the way. They are used to denote quantum states in complex Hilbert spaces. We are not doing quantum physics here so let's stop pretending.
+- [[User:Sintel|Sintel]] ([[User talk:Sintel|talk]]) 20:00, 18 December 2021 (UTC)
+== 2 or 3 digits ==
+Giving two options for the number of digits isn't really useful if we want consistency... I just changed the [[15edo#Commas]] table's values to 3 digits because I had checked [[17edo#Commas]] and that table used 3 digits, but apparently that one was the exception, not the reverse? Would it make sense to use 3 digits everywhere? Of course it's not urgent, but I'd rather stick to one standard rather than two, so that at least when we're making decisions, they're not arbitrary or random. --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 02:25, 7 July 2023 (UTC)
+: I would be in favour of using 3 digits everywhere. --[[User:BudjarnLambeth|BudjarnLambeth]] ([[User talk:BudjarnLambeth|talk]]) 02:38, 7 July 2023 (UTC)