Wiki source code of Extension tvb-ext-xircuits

Version 54.1 by paulapopa on 2023/03/08 17:06

Show last authors
1 Source code: [[https:~~/~~/github.com/the-virtual-brain/tvb-ext-xircuits>>https://github.com/the-virtual-brain/tvb-ext-xircuits]]
2
3 Release on Pypi: [[https:~~/~~/pypi.org/project/tvb-ext-xircuits/>>https://pypi.org/project/tvb-ext-xircuits/]]
4
5 == Jupyter Lab Extension for building and executing TVB Workflows on EBRAINS ==
6
7 == Purpose ==
8
9 This is a Jupyter Lab extension that offers graphical support for TVB workflows. It is already available in the EBRAINS Lab and it allows users to configure and execute TVB simulations directly from a GUI, while drastically reducing the complexity of configuring them inside a Jupyter Lab notebook.
10
11 == Acknowledgements ==
12
13 This extension is build on top of the [[Xircuits Jupyter extension>>https://xircuits.io/]], but it also comes with custom functionalities, specifically designed for TVB and EBRAINS. These functionalities are detailed in a section below.
14
15 == Installation ==
16
17 The extension can be installed using the official PyPi distribution ([[https:~~/~~/pypi.org/project/tvb-ext-xircuits/>>https://pypi.org/project/tvb-ext-xircuits/]]):
18
19 (% class="box" %)
20 (((
21 pip install tvb-ext-xircuits
22 )))
23
24 After installing the extension and opening a Jupyter Lab session, you should be able to see in the left panel of Jupyter Lab a new icon, which represents the Xircuits components tray:
25
26 [[image:side.png]]
27
28 == **Usage** ==
29
30 === **Step 1. Create a new Xircuits workflow** ===
31
32 From the Jupyter Lab launcher, click on the **Xircuits File** icon, as in the screenshot below.
33
34 [[image:newxircs.png]]
35
36 A new file with the .xircuits extension will be generated under your current working directory. This is where you can start building the workflow diagram interactively.
37
38 [[image:newfile.png]]
39
40 You will notice that 2 components are already placed inside the workflow: the __Start__ and the __Finish__ components. They cannot be modified or deleted, and they represent the starting and finishing point of the workflow.
41
42 === **Step 2.  Drag components into the workflow area** ===
43
44 Open the components tray, from the left-side bar icon highlighted below.
45
46 [[image:tray.png]]
47
48 Now, you can browse through the components, select the one you wish to use, then drag and drop it into the workflow area.
49
50 [[image:components.png]]
51
52 === **Step 3. Configure the components** ===
53
54 The components that are provided in this extensions are configurable, meaning you can set some parameters on almost every component. Some of the parameters are literals, while some parameters are results of other components.
55
56 In case of primitives you need to open the //General// tab from the components tray and drag the appropriate //literal//: float, int, string, dict, etc.
57
58 The parameters need to be linked to the inputs of the component by dragging and dropping a connection from the output port of a literal/component towards the corresponding input port of the other component (e.g. the gray connections in the screenshot below).
59
60 [[image:diagr.png]]
61
62 === **Step 4. Make connections** ===
63
64 After dragging all your desired components/literals in the workflow area, it's time to connect the components.
65
66 First, link the __Start__ node to the first component of your workflow. Then make the connections between all your components. The last component should be linked to the __Finish__ node, to indicate the end of your workflow (e.g. the blue connections in the screenshot below). These connections will dictate the order of execution of the components in your workflow.
67
68 [[image:diagram.png]]
69
70 === **Step 5. Run the workflow** ===
71
72 After connecting everything, you need to run the workflow to actually see its results.
73
74 There are 2 ways to run the workflow in EBRAINS Lab:
75
76 ~1. Locally:
77
78 * For this you can click on the Run button (▶), which will also implicitly compile the workflow. Make sure that __Local Run__ is selected near the Run button.
79
80 [[image:run.png]]
81
82
83 2. Remotely on HPC (only if you have access to HPC resources)
84
85 * First choose the __Remote Run__ in the select box and then click the Run button (▶), which will also implicitly compile the workflow.
86
87 [[image:remote.png]]
88
89 * A dialog will open to request the HPC connection details:
90 ** which __HPC Site__ to use
91 ** the name of the __HPC Project/Account__ you have access to
92 ** one checkbox to choose whether you want the __HPC Monitoring__ to be opened up automatically (via tvb-ext-unicore GUI). This can also be opened up manually using the __Monitor HPC__ button or the __U__ icon from the left side-bar.
93 ** one checkbox to choose whether you want the results to be __staged out__ automatically or not. If checked, the workflow waits for the HPC jobs to finish and then performs the stage out. If unchecked, the results can be manually downloaded later on by using the GUI of the tvb-ext-unicore.
94
95 [[image:rem.png]]
96
97 * The HPC monitoring is done via the GUI of tvb-ext-unicore which is a separate package we have documented under this Wiki. But it can be nicely used together with tvb-ext-xircuits:
98
99 [[image:uni.png]]
100
101
102 After clicking on Run, a new Jupyter Output window should appear in the bottom of your Jupyter Lab environment. Here you will see the output of your workflow, such as logs, static plots, etc.
103
104 [[image:out.png]]
105
106 === **Step 6. Share your work*** ===
107
108 This step is, of course, optional, but it is worth mentioning that sharing your workflows with others is extremely easy. By just saving and sharing your workflow (*.xircuits) file, anyone can access the entire workflow, see the exact connections that you made and receive the same configuration for the components.
109
110
111 == Custom functionalities ==
112
113 As mentioned before, besides all the core functionalities provided by Xircuits, some other functionalities were added to better suit the needs of the EBRAINS users.
114
115 === 1. Configure TVB models using the Phase Plane widget ===
116
117 This functionality was added to make it easier for users to provide the correct parameters to TVB models, using the Phase Plane widget.
118
119 To use this functionality, drag any model from the **TVB_MODELS** (inside the components tray) into the workflow area. Then right click on the model and select the **Open Viewer** option:
120
121
122 (% style="text-align:center" %)
123 [[image:image-20221116125354-2.png||height="800" width="1130"]]
124
125
126 A new Jupyter tab should open, which contains a read-only Jupyter notebook. After following the instructions provided there, you should be able to see the Phase Plane widget associated with this particular model.
127
128 (% style="text-align:center" %)
129 [[image:image-20221116125822-1.png||height="800" width="821"]]
130
131 After configuring the parameters with the desired values, go to the Exports tab of the widget and click on **Export model configuration**. Now all you have to do is to go back to the tab where your workflow is and you will see that the model will have values set for all the parameters that you modified in the Phase Plane widget (that is all the parameters there were assigned values different than the default ones).
132
133 (% style="text-align:center" %)
134 [[image:image-20221116130425-1.png||height="900" width="1069"]]
135
136
137 === 2. Visualize time series resulted from simulations ===
138
139
140 [[image:view.png]]
141
142 (% class="wikigeneratedid" %)
143 === ===
144
145 [[image:view2.png]]
146
147
148
149 [[image:view3.png]]
150
151 (% class="wikigeneratedid" %)
152 == ==
153
154 == Workflow examples ==
155
156 (((
157 === 1. Full TVB Simulation workflow ===
158 )))
159
160 Contains all TVB components necessary for running a TVB simulation (i.e. connectivity, coupling, model, integrator, monitor, simulator).
161
162 {{html}}
163 <iframe src="https://drive.google.com/file/d/14sVjWXmtfZB-Zt7i3MA26-MiNWwv3jZI/preview" width="1280" height="720" allow="autoplay"></iframe>
164 {{/html}}
165
166
167 === 2. Configuring model parameters using the PhasePlaneWidget: ===
168
169 Same workflow as before, but the parameter for the model used in simulation are set using the PhasePlaneWidget.
170
171 {{html}}
172 <iframe src="https://drive.google.com/file/d/1Puoi4-Ej4BhVwtdRzciPD_qNKMF0HvGT/preview" width="1280" height="720" allow="autoplay"></iframe>
173 {{/html}}
174
175
176 === 3. Using siibra to retrieve connectivities from the EBRAINS KG ===
177
178 A simulation workflow where **siibra **is used to retrieve a connectivity from the EBRAINS KG. That connectivity is fed into a TVB Simulator, where the rest of the parameters (coupling, model, etc.) are set to default values.
179
180 {{html}}
181 <iframe src="https://drive.google.com/file/d/1bakH6ZD96eMHnYSw1aasF_gNXt8sBS7D/preview" width="1280" height="720" allow="autoplay"></iframe>
182 {{/html}}
183
184
185 === 4. Run a workflow inside an HPB job ===
186
187 A workflow simulation which is run remotely, by submitting a job to an HPC site and getting back the results (TimeSeries object).
188
189 {{html}}<iframe src="https://drive.google.com/file/d/1rvcj_9lGtR069iXlL3Rm1czMNdA3qmGM/preview" width="1280" height="720" allow="autoplay"></iframe>{{/html}}
190
Public

TVB Widgets