smartbiotech / devicecontrol Goto Github PK

Data save with precision to seconds, should be changed to miliseconds.

The general format of data provided by DeviceControl has to be documented in Wiki.

Tasks are (usually) related to specific running device(s). Termination of a device should not be allowed before all respective tasks are terminated. Alternatively, upon device termination, all associated tasks should be terminated automatically.

Connect two PSI PBRs to one Neuron and test initialization of both devices in one experiment.

Exceptions are not handled properly during measure all tasks.

Depends on #13

Rename Value's feature channel to attribute.

• In the DB model definition.
• In all references to it.

All functionality have to be covered by unit tests.

Names of attributes of multiple object are over-complicated, e.g. device_id vs id. This includes both object attributes and key names in definition dictionaries (as it is related).

Even though the device was ended successfully. Possible cause: some function returns None instead of bool

There is wrong command used in PSI java PBR class. There should be set-actinic-light-state instead of set-ext-light-state

Since some of the tasks are device-specific, this should be reflected on DeviceControl by assigning possible tasks to devices.

Basic task to periodically measure weight of medium using SICS device. Based on the measurement, remaining amount of medium is approximated and the user is alerted in the case it is running low. For this task, we need a email account which will be used for sending notifications.

Implement measure_all and automatic pumping tasks for Phenometrics PBR.

In current devel version of deployment, we use ubuntu as base for Docker image. However, a smaller base could be used (e.g. alpine), but there are issues with dependencies. In particular, Java package causes problems with path.

Unable to load native library: Error loading shared library libjvm.so

Sometimes this error appears, when working with a Device. The reason is probably that it expires from the session once committed.

A periodic event to simulate day/night regime in PBR.

@JanCervenyy please answer the following questions:

1. What lights should (red/blue/...) be used? Is this device specific task?
   -> consider possibility to parametrise the task by particular command which should be executed
2. Provide examples of possible regimes to have idea what we need to support.
   -> is it just repetition of a pattern or something more complex?

Task for measuring a quantity in specified time intervals.

@JanCervenyy please answer the following questions:

1. Do we want this device-specific or general?
2. Please provide specification for individual quantities how often they should be measured.

The idea is to provide a dictionary 'time_interval: [list of commands] specifying how often should these commands be executed (very generalised version). In addition, type/class of device might also be specified, making the task event more general.

Depends on #11

All commands of devices should return a dict, annotating returning value. Currently, this is not applied to all commands. Needs to be unified.

Use sblmt-cli client to monitor drive/SD status.

DeviceControl should store all information needed for self-recovery. Alternatively, this information can be obtained from the DataServer.

Create and test task for 24 h periodic monitoring of the drive status.

Save the output to DeviceControl DB.

Consider this task as automatic when Swissbit compatible device is detected.

Similar to structure of devices, tasks should be also allowed to be structured.

In previous version, logging was done to a file, which is not the best option for docker. Solution: use normal stdout and use docker logs to inspect it.

The automatic installation process of runner has several minor issues:

• DB access outside of local host could be resolved automatically (just minor modification in /etc/mysql/mariadb.conf.d/50-server.cnf for Neurons)
• running redeploy for the first time sometimes causes error docker: Error response from daemon
• line usermod -aG docker bioarineo in install_docker.sh rises usermod: not found
• after installing docker, the device must be rebooted (acts like the docker is not installed properly, after reboot everything is fine)

Experimental protocol contains specification of class and type of device. This have to be reflected.

Phenometrics PBRs should have their GUIs locked/unlocked when DeviceControl is using the device and when it is not.

The trusted devices will be recognized using fingerprint of the hardware (with additional information such as MAC address). It is necessary to define a reliable approach how to implement such a feature.

We need to get new Java lib that supports MC-1000 commands set.

During registration of client (DeviceControl) to DataServer, the client should provide available devices which were detected automatically. However, this has to be supported by communication software of particular device.