Module to interact with pyrvapi
remove_widget() may result in an unexpected unless you put flush() immediately before and immediately after calling them, e.g.:
>>> pyrvapi_flush()
>>> for i in range():
... rvapi_remove_widget(..i..)
>>> rvapi_flush()
This is because chronology of rvapi calls between flushes is not necessarily the same as chronology of making/changing widgets in the page. E.g. in sequence of calls:
>>> rvapi_flush()
>>> rvapi_action1()
>>> rvapi_action2()
>>> rvapi_action3()
>>> rvapi_flush()
>>> rvapi_action4()
>>> rvapi_action5()
>>> rvapi_action6()
>>> rvapi_flush()
it is guaranteed that results of actions 4-6 will appear after results from 1-3, but there is no guarantee that results from 1-3 and 4-6 groups will appear in exactly that order. E.g., the page may perform actions like 3-1-2-5-4-6, but never like 6-4-1-2-3-5.
AmpleOutput(amopt, own_gui=False)[source]¶Bases: object
Display the output of an AMPLE job.
Methods
fix_path(path) |
Ammend path so it’s suitable for the webserver |
rvapi_shutdown(amopt) |
Return any results to jscofe |
| create_log_tab | |
| create_results_tab | |
| create_summary_tab | |
| display_results | |
| ensemble_pdb | |
| fill_table | |
| results_section | |
| setup |