Submissions:AlgorithmImplementationExecution
From Odp
(Difference between revisions)
| Line 40: | Line 40: | ||
Task SubClassOf definedOn some Input | Task SubClassOf definedOn some Input | ||
|ReusableOWLBuildingBlock=https://github.com/ML-Schema/core/blob/master/AlgorithmImplementationExecution.owl | |ReusableOWLBuildingBlock=https://github.com/ML-Schema/core/blob/master/AlgorithmImplementationExecution.owl | ||
| - | |Scenario=Consider a scenario in machine learning (ML) domain. The scenario deals with a machine learning task realization and it is based on an example derived from the OpenML portal (http://www.openml.org/). <br> There is an ML Task <code>:task29</code> which is a supervised classification task defined on the dataset <code>:credit-a</code>. This task is realized by the Execution <code>:run100241</code> which executes the Implementation <code>:wekaLogistic</code> of the Algorithm <code>:logisticRegression</code>. <br>The Implementation <code>:wekaLogistic</code> has five hyperparameters (Parameter): <code>:wekaLogisticC</code>, <code>:wekaLogisticDoNotCheckCapabilities</code>, <code>:wekaLogisticM</code>, <code>:wekaLogisticOutputDebugInfo</code>, <code>:wekaLogisticR</code>. The values of two of these hyperparameters are set. The hyper parameter <code>:wekaLogisticM</code> has value set to -1 (expressed via the ParameterSetting <code>:wekaLogisticMSetting29</code>), and the hyper parameter <code>:wekaLogisticR</code> that has its value set to <code>"1.0E-8"^^xsd:float</code> (expressed via the ParameterSetting <code>:wekaLogisticRSetting29</code>). The Execution <code>:run100241</code> has on Input the <code>:credit-a</code> dataset and the parameter settings and its Output is the ML model <code>:wekaLogisticModel100241</code>. | + | |Scenario=Consider a scenario in machine learning (ML) domain. The scenario deals with a machine learning task realization and it is based on an example derived from the OpenML portal (http://www.openml.org/). <br> There is an ML Task <code>:task29</code> which is a supervised classification task defined on the dataset <code>:credit-a</code>. This task is realized by the Execution <code>:run100241</code> which executes the Implementation <code>:wekaLogistic</code> of the Algorithm <code>:logisticRegression</code>. <br>The Implementation <code>:wekaLogistic</code> has five hyperparameters (Parameter): <code>:wekaLogisticC</code>, <code>:wekaLogisticDoNotCheckCapabilities</code>, <code>:wekaLogisticM</code>, <code>:wekaLogisticOutputDebugInfo</code>, <code>:wekaLogisticR</code>. The values of two of these hyperparameters are set. The hyper parameter <code>:wekaLogisticM</code> has value set to -1 (expressed via the ParameterSetting <code>:wekaLogisticMSetting29</code>), and the hyper parameter <code>:wekaLogisticR</code> that has its value set to <code>"1.0E-8"^^xsd:float</code> (expressed via the ParameterSetting <code>:wekaLogisticRSetting29</code>). <br> The Execution <code>:run100241</code> has on Input the <code>:credit-a</code> dataset and the parameter settings and its Output is the ML model <code>:wekaLogisticModel100241</code>. |
| - | |KnownUse=ML Schema, DMOP, | + | |KnownUse=ML Schema, DMOP, Function Ontology, MEX, OBI, OntoDM |
|ReengineeredFrom=ML Schema, https://www.w3.org/community/ml-schema/ | |ReengineeredFrom=ML Schema, https://www.w3.org/community/ml-schema/ | ||
|HasComponent=TimeInterval | |HasComponent=TimeInterval | ||
Revision as of 09:17, 6 July 2016
| If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 12557 |
Graphical representation
Diagram
General description
| Name: | AlgorithmImplementationExecution |
|---|---|
| Submitted by: | AgnieszkaLawrynowicz, DiegoEsteves, PancePanov, SasoDzeroski, TommasoSoru, JoaquinVanschoren |
| Also Known As: | |
| Intent: | To model algorithm specifications, their implementations and executions, together with parameters of implementations, settings of the parameters for the execution, and inputs the execution consumes (e.g., data) and outputs the execution produces (e.g., models, reports). |
| Domains: | |
| Competency Questions: |
|
| Solution description: | Beloit it is provided the formalization of the pattern in the Web Ontology Language (OWL) in Manchester syntax:
Algorithm SubClassOf InformationEntity |
| Reusable OWL Building Block: | https://github.com/ML-Schema/core/blob/master/AlgorithmImplementationExecution.owl (0) |
| Consequences: | |
| Scenarios: | Consider a scenario in machine learning (ML) domain. The scenario deals with a machine learning task realization and it is based on an example derived from the OpenML portal (http://www.openml.org/). There is an ML Task :task29 which is a supervised classification task defined on the dataset :credit-a. This task is realized by the Execution :run100241 which executes the Implementation :wekaLogistic of the Algorithm :logisticRegression. The Implementation :wekaLogistic has five hyperparameters (Parameter): :wekaLogisticC, :wekaLogisticDoNotCheckCapabilities, :wekaLogisticM, :wekaLogisticOutputDebugInfo, :wekaLogisticR. The values of two of these hyperparameters are set. The hyper parameter :wekaLogisticM has value set to -1 (expressed via the ParameterSetting :wekaLogisticMSetting29), and the hyper parameter :wekaLogisticR that has its value set to "1.0E-8"^^xsd:float (expressed via the ParameterSetting :wekaLogisticRSetting29). The Execution :run100241 has on Input the :credit-a dataset and the parameter settings and its Output is the ML model :wekaLogisticModel100241.
|
| Known Uses: | ML Schema, DMOP, Function Ontology, MEX, OBI, OntoDM |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: |
|
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
Elements
The AlgorithmImplementationExecution Content OP locally defines the following ontology elements:
Additional information
Scenarios
Scenarios about AlgorithmImplementationExecution
No scenario is added to this Content OP.
Reviews
Reviews about AlgorithmImplementationExecution
There is no review about this proposal. This revision (revision ID 12557) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
Modeling issues about AlgorithmImplementationExecution
There is no Modeling issue related to this proposal.
References
