You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@reef.apache.org by "Julia (JIRA)" <ji...@apache.org> on 2017/07/27 00:57:00 UTC

[jira] [Assigned] (REEF-1842) Making IMRU task and input data association deterministic

     [ https://issues.apache.org/jira/browse/REEF-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julia reassigned REEF-1842:
---------------------------

    Assignee: Julia

> Making IMRU task and input data association deterministic
> ---------------------------------------------------------
>
>                 Key: REEF-1842
>                 URL: https://issues.apache.org/jira/browse/REEF-1842
>             Project: REEF
>          Issue Type: Task
>            Reporter: Julia
>            Assignee: Julia
>            Priority: Critical
>
> Currently, the tasks added to the typology on communication group is based on the sequence of contexts received. While the input data assigned to context can be random especially when some evaluators fail and new evaluators/contexts are requested. This makes the training result undeterministic given same input data set. 
> To make the result deterministic for given the input data, we would like to the tasks in the typology keep the same order with the same input data file. To achieve it, the mapping between the context id and partitionDescriptor id should be fixed once assigned. And when adding tasks to the communication group, the order should be based on the sorted id to ensure it is deterministic. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)