Property talk:P1171
Documentation
method used to approximate a number
Description | approximation algorithm (Q621751): method used to approximate this number. See also determination method or standard (P459). | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Represents | approximation algorithm (Q621751) | ||||||||||||
Data type | Item | ||||||||||||
Domain | According to this template:
number (Q11563), maybe also other mathematical or physical objects ...
When possible, data should only be stored as statements | ||||||||||||
Allowed values | approximation algorithm (Q621751) : algorithm used to compute an approximation of the subject value (note: this should be moved to the property statements) | ||||||||||||
Example | According to this template:
Pi :
According to statements in the property:
When possible, data should only be stored as statementspi (Q167) → Gauss–Legendre algorithm (Q2448949) square root (Q134237) → Heron's method (Q20725439) | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P1171 (Q125145000) | ||||||||||||
See also | determination method or standard (P459) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P1171#Type Q11563, Q11348, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1171#Value type Q621751, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1171#Entity types
List of violations of this constraint: Database reports/Constraint violations/P1171#Scope, SPARQL
P459
edit@TomT0m, Paperoastro, Tobias1984:. Thinking about it, maybe it would make sense to use determination method or standard (P459) for that. If the item is an instance of number and the property value an instance (subclass ?) of algorithm, it should be clear that it means "algorithm giving a value for the number" ? --Zolo (talk) 09:29, 1 March 2014 (UTC)
- @Zolo: I missed that we already have that property. That is something we should think about. --Tobias1984 (talk) 09:54, 1 March 2014 (UTC)
- seems to make sense. We should regroup the usecases and try to model them. One usecase that come to my mind are optimisation algorithms, for which we got exact methods (algorithms) and approximation algorithms (and families of algorithm) such as metaheuristics. Relevant items I can think of includes travelling salesperson problem (Q322212) simplex algorithm (Q134164) , metaheuristic (Q1385229) tabu search (Q1424540) PageRank (Q184316) Eh cool we can drag and drop results from the searchbox suggestion list to the edit zone !. I think determination method or standard (P459) can also be used for experiments in the real world to measure a physical constants, but we could discriminate the methods by the type of the object (I often says algorithms are methods to solve problems in real world, I think we got a case :) ). It could be interesting to think how works such as http://link.springer.com/chapter/10.1007%2F3-540-61422-2_124 fits in this scheme. optical character recognition (Q167555) and automatic classification algorithms (a little bit more complex) ... TomT0m (talk) 11:17, 1 March 2014 (UTC)
- I also missed P459, but the idea of TomT0m likes me. --Paperoastro (talk) 15:22, 1 March 2014 (UTC)
Can This Property be Used on Functions?
editWhile discussing Wikidata:Property proposal/iterative approximation, @Midleading and I tried adding the statement Lambert W function (Q429331)approximation algorithm (P1171)Newton's method (Q374195) because it's possible to approximate the value of the Lambert W function at each point using Newton's method. This statement displays a type constraint, however. Does anybody object to adding function (Q11348) to the list of permitted types for this property? — The Erinaceous One 🦔 18:41, 14 September 2022 (UTC)
- I just broaden the scope to allow functions as well. Midleading (talk) 02:51, 19 November 2022 (UTC)