Runtime info

[piorus]

Send current operation mode to API endpoint

Operation modes:

• active & incorrect lens setup
• active & detecting
• not active

[dzwiedziu-nkg]

We waiting for APIv2.

[piotrhomola]

While waiting for APIv2 it makes a lot of sense to develop the on-time functionality within the app: 1) define "active & detecting" (right configuration by an unexperienced user is highly non-trivial, autocalibration might be required, and autocalibration is also non-trivial ;) 2) display current operation mode on the "status" page, with clear message like "not yet in the oparation mode - please cover your camera better" 3) there might be more than one sets of parameters good for "active & detecting" ("working range") - for instance with a non-perfect camera coverage one might still think of setting the triggers so that the brightest particle tracks could be identified (there will be fewer hits then but still something that we can analyze), while with camera perfectly covered one might want to work with reduced trigger level to catch also faint particle signals. These operation modes should be saved, so that the user could select a desired mode also by himself. 4) Once the APIv2 is available we send the operating mode info to the server. // So it seems to me there is a lot of work with on-time before APIv2 is available.