You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your job is to submit a list of weights for the edges, where the weight of an edge source (dependent) -> target (dependency) represents the portion of the credit for source (dependent) that belongs to target (dependency). The weights coming out of a source node into its target nodes should sum to less than one; the remainder represents the portion of credit that rests with the source node itself.
This implies that graphs should be submitted along the lines of case 1 in the sketch below:
Discussion in the telegram chat suggests ambiguity, however, about which case is being modeled, with some participants looking to submit a single distribution across all nodes collectively (case 2).*
Unless I've mis-read it, the scoring script included here currently only treats the case of a single distribution, which would apply to one project and dependencies in case 1, and an entire graph in case 2. To avoid potential false starts, the scope of the scoring function should be made more explicit.
*It is worth noting that case 1 is a special case of case 2, and that solutions can be converted from case 2 to case 1 by re-normalizing. As such, a case 2 submission could be (equivalently, I believe) scored by the existing script, before being converted to case 1 to determine actual funding.
The text was updated successfully, but these errors were encountered:
The Deep Funding problem statement is given as follows:
This implies that graphs should be submitted along the lines of case 1 in the sketch below:
Discussion in the telegram chat suggests ambiguity, however, about which case is being modeled, with some participants looking to submit a single distribution across all nodes collectively (case 2).*
Unless I've mis-read it, the scoring script included here currently only treats the case of a single distribution, which would apply to one project and dependencies in case 1, and an entire graph in case 2. To avoid potential false starts, the scope of the scoring function should be made more explicit.
*It is worth noting that case 1 is a special case of case 2, and that solutions can be converted from case 2 to case 1 by re-normalizing. As such, a case 2 submission could be (equivalently, I believe) scored by the existing script, before being converted to case 1 to determine actual funding.
The text was updated successfully, but these errors were encountered: