Bases: builtins.object
Bases: tvb.interfaces.web.controllers.burst.base_controller.BurstBaseController
Cancel or Remove the burst entity given by burst_id (and all linked entities: op, DTs) :returns True: if the op was successfully.
Stop the operation given by operation_id. If is_group is true stop all the operations from that group.
Load the available burst that are stored in the database at this time. This is one alternative to ‘chrome-back problem’.
Upload Simulator from previously exported ZIP file
Bases: builtins.object
This class gathers the rendering rules for simulator_fragment template. TVB > 2.0 brings a change of UI inside the simulator configuration page. Instead of a pre-loaded huge form with all the configurations, we want to have a wizzard-like page. Thus, the configurations are grouped into fragments and each fragment is rendered as a separate form. Each form provides the user with Next/Previous buttons, and some of them bring some extras:
- model form provides the buttons: setup region model parameters/setup surface model parameters;
- last fragment provides extra Launch/Setup PSE buttons, and a Branch button when it’s the case.
next form. When the Next button is clicked, the current form is made read-only. If the user need to make changes to a previous form that is already read-only, he might use the Previous buttons to get there, make the change, and come back clicking Next again. - from the history list, the user could choose to inspect an existing simulator configuration, by clicking on it. This will load the full configuration as read-only forms, without any buttons. - from the history list, the user also has the option to copy an existing simulator configuration A and edit it, or start a new simulation B using the results from A as initial conditions. This results, in a semi-read-only load of simulator configuration A, because the user will have the options:
- to use the Previous buttons in order to edit configuration A and the Launch/Setup PSE buttons to start a
new simulation. - to use the Branch button in order to start a new simulation B that will use results from A as initial conditions.
So, we need a series of rendering rules, to know when to display/hide each button, and also make fields read-only.
Bases: builtins.object