Property talk:P2159

From Wikidata
Jump to navigation Jump to search

Documentation

computes solution to
problem that this algorithm or method solves
Data typeItem
Domain
According to this template: algorithm (Q8366)  View with Reasonator View with SQID, maybe other heuristic or non mathematical problem solving methods
According to statements in the property:
algorithm (Q8366) or solver (Q1966904)
When possible, data should only be stored as statements
Allowed valuescomputational problem (Q3435924)  View with Reasonator View with SQID, others ? (note: this should be moved to the property statements)
Example
According to this template: DPLL algorithm (Q2030088)boolean satisfiability problem (Q875276),
⟨ Dijkstra's algorithm (Q8548)  View with Reasonator View with SQID ⟩ solves Search ⟨ 1058754 ⟩
According to statements in the property:
DPLL algorithm (Q2030088)boolean satisfiability problem (Q875276)
image scaling algorithm (Q65949919)image scaling (Q440296)
Broyden–Fletcher–Goldfarb–Shanno algorithm (Q2877013)optimization problem (Q984063)
When possible, data should only be stored as statements
Lists
Proposal discussionProposal discussion
Current uses
Total161
Main statement15797.5% of uses
Qualifier31.9% of uses
Reference10.6% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P2159#Scope, hourly updated report, SPARQL
Type “algorithm (Q8366), solver (Q1966904): item must contain property “instance of (P31), subclass of (P279)” with classes “algorithm (Q8366), solver (Q1966904)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2159#Type Q8366, Q1966904, SPARQL
Value type “computational problem (Q3435924): This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value computational problem (Q3435924) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2159#Value type Q3435924, SPARQL

Label Change[edit]

In the property proposal for a "is solution to" property, we have discussed changing the label of this property to "computes solution to." As I state in that disucssion, the current label of P2159 is ambiguous because we say both "solution x solves problem z" and "method y solves problem z." If you object to relabeling this property, please share it here, otherwise I will make the change in a few days. — The Erinaceous One 🦔 10:06, 30 December 2020 (UTC)[reply]

Extend scope to hardware?[edit]

Application-specific hardware like GPUs, DSP, the new quantum chips (with all the code buried inside them) also compute specific jobs. Shouldn't they also be include here? Retired electrician (talk) 03:13, 19 December 2022 (UTC)[reply]

Could value be also Q1166625?[edit]

It's still something that can be solved. Martinligabue (talk) 14:30, 10 July 2023 (UTC)[reply]

Only specific mathematical problem (Q1166625). --Infovarius (talk) 20:07, 11 July 2023 (UTC)[reply]