-
Notifications
You must be signed in to change notification settings - Fork 0
4. Process
Alberto Cottica edited this page Jul 1, 2017
·
1 revision
- We downloaded the data, imported them into Google Refine, checked them for consistency and trimmed the strings.
- We imported them into a Tulip perspective via a Python script, in the form of a bipartite graph (organisations connecting to projects).
- We removed one outlier project (
Implementation of activities described in the Roadmap to Fusion during Horizon 2020 through a Joint programme of the members of the EUROfusion consortium
). With 31 partners and a budget of over 400 million EUR, it was much larger than others. Also, its partnership was probably less subject to competition than most others in Horizon 2020. - The resulting network is a organisations-to-projects network with 16,592 organisations and 11,068 projects, connected by 47,196 edges. The edge from organisation
O
to projectP
encodes the contribution (ecContribution
) allocated toO
underP
, and so represents the value of that participation toO
. The total EU contribution to the project is a property of the nodeP
. - We projected this network onto an organisations-to-organisations partnership network, with 16,592 organisations connected by 1,077,218 edges. Each edge
P1 => P2
encodes the co-participation betweenP1
andP2
in one project, seen from the point of view ofP1
. It encodes theecContribution
property referred to the funding received byP1
. Conversely, there will be an edgeP2 => P1
that encodes the co-participation ofP1
andP2
in the same project, but now seen from the point of view ofP2
. TheecContribution
property now encodes the funding received byP2
. IfP1
andP2
co-participated inn
projects, there aren
P1 => P2
edges andn
P2 => P1
edges - We next calculated a measure of bargaining power by each participant in each project (encoded in each edge), as well as a measure of each participant's bargaining power across the whole of her participation in Horizon 2020 projects. Formulas are provided and discussed in a separate wiki page.
In order to reduce the graph, and so make it more amenable to visual analysis, we:
- "Stacked" edges on top of each other. This means imposing that there is at most one
P1 => P2
edge. IfP1
andP2
co-participated inn
projects, we attribute valuen
to theprojectsTogether
property. This yields a graph with the same 16,592 nodes and 493,014 edges. - Filtered the edges of the stacked graph that encode exactly one project (
projectsTogether = 1
) to obtain a stable partnership graph. Nodes that have no edges in the resulting graph (that is, that have no stable partnership), are next dropped. The resulting graph represents partnerships that have been considered satisfactory enough to be carried through from one project to another. This graph has 3,414 nodes, and 46,632 edges. - Further reduced the stable partnership graph to its largest component. This is a network representation of the Horizon 2020 "scene". This graph has 3,138 nodes and 45,698 edges.