Talk:Relative interval error: Difference between revisions

(One intermediate revision by one other user not shown)

Line 23:

::: I'm not attached to direct, but "val-based mapping" seems really mathy. You have to know what a val is to even begin to understand it. Speaking of terminology, I find "val" to be pretty confusing. IMO terminology should be at least somewhat self-explanatory. Like "edostep", which I coined but never said what it meant. I never had to, I just started using it and everyone got it at once. The literal meaning of val is value, or number, which isn't explanatory at all. That's why I prefer the term edomapping. "Patent val" is also confusing, because patent in the sense of obvious is, well, not obvious. I prefer "nearest edomapping", but you could make a case for "obvious edomapping". Anyway, just my opinions. --[[User:TallKite|TallKite]] ([[User talk:TallKite|talk]]) 05:41, 14 December 2020 (UTC)

:::: It's been quite some time. After trying a couple of different terms in the communication on Discord, I find "direct approximation" and "val mapping" are the least confusing combo. All it takes for a novice is to learn what a val is. Once that's done, no amibiguities could possibly arise. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 15:27, 30 August 2021 (UTC)

Revision as of 08:54, 6 April 2021 view source Mike Battaglia (talk \| contribs) autopatrolled, Bureaucrats, confirmaccount-notify, emailconfirmed, Interface administrators, Sysops 1,399 edits m Mike Battaglia moved page Talk:Relative error to Talk:Relative Interval Error: The term "Relative Error" has been used for a very long time to refer to the TE temperament thing, so I'd like to clarify in the title that this is something new. "Relative Interval Error" seems to fit ← Older edit		Latest revision as of 15:27, 30 August 2021 view source FloraC (talk \| contribs) autopatrolled, Bureaucrats, Interface administrators, Sysops 18,328 edits No edit summary
(One intermediate revision by one other user not shown)
Line 23:		Line 23:

	::: I'm not attached to direct, but "val-based mapping" seems really mathy. You have to know what a val is to even begin to understand it. Speaking of terminology, I find "val" to be pretty confusing. IMO terminology should be at least somewhat self-explanatory. Like "edostep", which I coined but never said what it meant. I never had to, I just started using it and everyone got it at once. The literal meaning of val is value, or number, which isn't explanatory at all. That's why I prefer the term edomapping. "Patent val" is also confusing, because patent in the sense of obvious is, well, not obvious. I prefer "nearest edomapping", but you could make a case for "obvious edomapping". Anyway, just my opinions. --[[User:TallKite\|TallKite]] ([[User talk:TallKite\|talk]]) 05:41, 14 December 2020 (UTC)		::: I'm not attached to direct, but "val-based mapping" seems really mathy. You have to know what a val is to even begin to understand it. Speaking of terminology, I find "val" to be pretty confusing. IMO terminology should be at least somewhat self-explanatory. Like "edostep", which I coined but never said what it meant. I never had to, I just started using it and everyone got it at once. The literal meaning of val is value, or number, which isn't explanatory at all. That's why I prefer the term edomapping. "Patent val" is also confusing, because patent in the sense of obvious is, well, not obvious. I prefer "nearest edomapping", but you could make a case for "obvious edomapping". Anyway, just my opinions. --[[User:TallKite\|TallKite]] ([[User talk:TallKite\|talk]]) 05:41, 14 December 2020 (UTC)

			:::: It's been quite some time. After trying a couple of different terms in the communication on Discord, I find "direct approximation" and "val mapping" are the least confusing combo. All it takes for a novice is to learn what a val is. Once that's done, no amibiguities could possibly arise. [[User:FloraC\|FloraC]] ([[User talk:FloraC\|talk]]) 15:27, 30 August 2021 (UTC)