ScenarioProxy
Object to simplify scenario creation, configuration and run. This can be used in a Jupyter Notebook
:raises Exception: [description] :return: [description] :rtype: [type]
This create a scenario in the database with the provided Task or Protocol
type[gws_core.protocol.protocol.Protocol] | Nonegws_core.folder.space_folder.SpaceFolder | Nonestr - ''ScenarioCreationType - ScenarioCreationType.AUTOstr | NoneTaglistScenariostrretrieve the main protocol of the scenario
ProtocolProxystrboolboolboolScenarioProxyReset the scenario to draft and delete all logs and progress
ScenarioProxyReset all processes in error of the scenario
ScenarioProxyexecute the scenario, after that the resource should be generated and can be retrieve by process
bool - FalseRun the scenario in a separate CLI process but don't wait for it to finish.
Uses a CLI subprocess (like the queue runner) instead of fork to avoid inheriting the parent's server socket and event loop state, which can block other HTTP requests.
ScenarioWaiterBasicStop the scenario or remove it from the queue depending on its current status.
- If the scenario is running in an external lab, stop all running importing scenarios.
- If the scenario is running locally, stop it.
- If the scenario is in queue, remove it from the queue.
ScenarioProxyCreate a ScenarioProxy from an existing scenario
strScenarioProxy