Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 1 removed)
  • image-20230721151330-2.png
  • launch.png

Details

Page properties

Content

...	...	@@ -4,18 +4,17 @@
4	4	== **Purpose** ==
5	5
6	6
7		-It is composed of two separate Jupyter Widgets(PSE Launcher and PSE Visualizer) intended for the visualization of launching custom simulations. The launcher works locally and on HPC.
	7	+It is composed of two separate Jupyter Widgets(PSE Launcher and PSE Visualizer) intended for the visualization of launching custom simulations. The launcher works locally for now, but in the future a HPC launch will be available.
8	8
9	9	The simulation can be customized by:
10	10
11		-* Getting a list of connectivities and an HPC configuration given as APIs
	11	+* Getting a list of connectivities given as API
12	12	* Setting up parameters and ranges
13	13	* Selecting multiple metrics
14		-* Observing the progress of the launch by a monitor progress bar
15	15
16	16	== **Inputs** ==
17	17
18		-* PSELauncher(Simulator, List of Connectivities, HPC Configuration)
	17	+* PSELauncher(Simulator, List_of_Connectivities)
19	19	* PSEVisualizer(Filename), the file will contain all the customized parameters from the launcher
20	20
21	21	== **Requirements and installation** ==
...	...	@@ -57,28 +57,15 @@
57	57	from tvb.simulator.lab import *
58	58	)))
59	59
60		- The launcher widget can be initialized with more parameters: a simulator, a list of connectivities and an HPC configuration (only the simulator being a required argument). For HPC launch, besides the configuration part, an EBrains token needs to be stored. A custom initialization, which includes the HPC launch, is shown below:
	59	+ The launcher widget can be initialized with the required parameters (simulator and the list of connectivities) as it shows below:
61	61
62	62	(% class="box" %)
63	63	(((
64		-os.environ['CLB_AUTH'] = 'PUT YOUR EBRAINS TOKEN HERE IF YOU WANT HPC RUNS'
65		-
66		-from pyunicore.helpers.jobs import Resources
67		-res = Resources(cpus_per_node=4)
68		-
69		- # !! Pay attention to env name and dir you might need to change if in conflict on the SAME project with another colleague of yours!!
70		-
71		-hpc_config = HPCConfig(site="JUSUF", project="icei-hbp-2021-0007",
72		- env_dir="tvb_widget", env_name="venv_tvb", n_threads=None, resources=res)
73		-)))
74		-
75		-(% class="box" %)
76		-(((
77	77	sim = simulator.Simulator(connectivity = connectivity.Connectivity.from_file())
78	78	conn_66 = connectivity.Connectivity.from_file("connectivity_66.zip")
79	79	conn_68 = connectivity.Connectivity.from_file("connectivity_68.zip")
80	80	conn_76 = connectivity.Connectivity.from_file()
81		-launch = PSELauncher(sim, [conn_66, conn_68, conn_76], hpc_config)
	67	+launch = PSELauncher(sim, [conn_66, conn_68, conn_76])
82	82	)))
83	83
84	84	The outcome will be something like in the image bellow.
...	...	@@ -86,26 +86,12 @@
86	86
87	87	[[image:setup_parameters.png||alt="setup_parameters" style="float:left"]]
88	88
89		-
90		-
91		-
92		-
93		-
94		-
95		-
96		-
97		-
98		-
99	99	Then, a file name has to be inserted in the indicated box(for storing the data) and as a last set-up, a launch type has to be chosen.
100	100
	77	+[[image:launch.png||alt="launch" style="float:left"]]
101	101
102		-The progress of the launch can be monitored by a progress bar, as shown below:
	79	+A file with the name you specified will be generated.
103	103
104		-(% style="text-align:center" %)
105		-[[image:image-20230721150554-1.png]]
106		-
107		-A file with the name you specified will be generated in both approaches, HPC or local launch.
108		-
109	109	Then, the PSEVisualizer can be called with the required parameter(file_name) as it shows below:
110	110
111	111	(% class="box" %)

image-20230721151330-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.teodoramisan

Size

...	...	@@ -1,1 +1,0 @@
1		-21.4 KB

Content

launch.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.teodoramisan

Size

...	...	@@ -1,0 +1,1 @@
	1	+236.9 KB

Content