lyse.__main__.FileBox

class lyse.__main__.FileBox(container, exp_config, to_singleshot, from_singleshot, to_multishot, from_multishot)

Bases: object

__init__(container, exp_config, to_singleshot, from_singleshot, to_multishot, from_multishot)

Methods

__init__(container, exp_config, ...)
analysis_loop()
connect_signals()
do_multishot_analysis()
do_singleshot_analysis(filepath)
incoming_buffer_loop()	We use a queue as a buffer for incoming shots.
on_add_shot_files_clicked()
on_analysis_running_toggled(pressed)
on_columns_changed()
on_edit_columns_clicked()
on_mark_selection_not_done_clicked()
on_run_multishot_analysis_clicked()
pause_analysis()
set_add_shots_progress(completed, total, message)
set_columns_visible(columns_visible)

analysis_loop()

connect_signals()

do_multishot_analysis()

do_singleshot_analysis(filepath)

incoming_buffer_loop()

We use a queue as a buffer for incoming shots. We don’t want to hang and not respond to a client submitting shots, so we just let shots pile up here until we can get to them. The downside to this is that we can’t return errors to the client if the shot cannot be added, but the suggested workflow is to handle errors here anyway. A client running shots shouldn’t stop the experiment on account of errors from the analyis stage, so what’s the point of passing errors to it? We’ll just raise errors here and the user can decide what to do with them.

on_add_shot_files_clicked()

on_analysis_running_toggled(pressed)

on_columns_changed()

on_edit_columns_clicked()

on_mark_selection_not_done_clicked()

on_run_multishot_analysis_clicked()

pause_analysis()

set_add_shots_progress(completed, total, message)

set_columns_visible(columns_visible)