scale fix

common/tmate.rst

@@ -62,7 +62,7 @@ Usage
 * Copy the access token (full or read-only)
 
 .. figure:: images/tmate_token.png
-    :scale: 40%
+    :width: 515px
     :alt: tmate tokens
 
 * Press *q* or *Ctrl+C* to start the shared session

eva-mlkit/client/R/index.rst

@@ -6,7 +6,7 @@ installed. If there is no server installed, data is processed on the client
 side.
 
 .. figure:: ./ss/r.png
-    :scale: 20%
+    :width: 765px
     :alt: EVA ICS ML kit R client inside R-studio
 
     EVA ICS ML kit R client inside R-studio

eva-mlkit/client/py/index.rst

@@ -21,7 +21,7 @@ The above command must be typed in the system terminal. If using Anaconda
 Navigator, open a terminal window for an environment:
 
 .. figure:: ./ss/anaconda_install.png
-    :scale: 20%
+    :width: 475px
     :alt: Anaconda terminal
 
 EVA ICS venv

eva-mlkit/index.rst

@@ -16,7 +16,7 @@ The kit contains client modules for Python and R, which can be used without any
 restrictions and a server part which must be purchased separately.
 
 .. figure:: ./images/dataconv.png
-    :scale: 40%
+    :width: 405px
     :alt: Data frame conversions
     :align: right
 

eva-mlkit/learning/regression/predicting.rst

@@ -84,7 +84,7 @@ the real one:
    result['time'] = times
 
 .. figure:: ../ss/plot_predict.png
-    :scale: 80%
+    :width: 605px
     :alt: Prediction chart
 
 If the sensor data is similar to the data which has been used to train the

eva-mlkit/learning/regression/training.rst

@@ -50,7 +50,7 @@ If Jupyter or other graphical environment is used, let us plot the data or its
 part:
 
 .. figure:: ../ss/plot1.png
-    :scale: 60%
+    :width: 630px
     :alt: Data chart
 
 Perform the training

eva-mlkit/server/index.rst

@@ -30,7 +30,7 @@ Supported data formats:
 * CSV (comma-separated values only)
 
 .. figure:: ../schemas/mlsrv.png
-    :scale: 80%
+    :width: 710px
     :alt: ML server
 
 .. toctree::

eva3/cli.rst

@@ -25,7 +25,7 @@ everything, command repeating, batch commands and is the recommended way to
 configure, manage and monitor EVA ICS nodes from command line.
 
 .. figure:: eva-shell.png
-    :scale: 100%
+    :width: 850px
     :alt: EVA shell
 
     with EVA shell, IoT management is a joy

eva3/cloudmanager/cloudmanager.rst

@@ -12,7 +12,7 @@ Dashboard
 =========
 
 .. figure:: cloudmanager.png
-    :scale: 50%
+    :width: 665px
     :alt: Cloud Manager Dashboard
 
 Cloud Manager dashboard displays all resources, available for :doc:`../sfa/sfa`
@@ -29,5 +29,5 @@ entered manually by pressing "edit" button in the controller table. By default,
 the local master key is used.
 
 .. figure:: cloudmanager_edit_controller.png
-    :scale: 50%
+    :width: 670px
     :alt: Cloud Manager Dashboard

eva3/drivers.rst

@@ -100,7 +100,7 @@ to the property with *|driver_id* value, e.g. *|v1.default*.
     logic-specific options as global or for the particular item group.
 
 .. figure:: drivers-action.png
-    :scale: 75%
+    :width: 740px
     :alt: Drivers and actions
 
     How the driver handles action commands
@@ -111,7 +111,7 @@ developed as "universal") without a need to load different drivers for each
 item.
 
 .. figure:: drivers-update.png
-    :scale: 75%
+    :width: 740px
     :alt: Drivers and updates
 
     How the driver handles update commands
@@ -259,7 +259,7 @@ you must connect your equipment to 2 relay ports: one will give power to
 motors, the second will set the direction.
 
 .. figure:: schemas/ac_motor.png
-    :scale: 75%
+    :width: 535px
     :alt: AC motor circiut
 
     AC motor circuit
@@ -276,7 +276,7 @@ Configuration options (set with *eva uc driver load*):
   *dport = 1* for "closing".
 
 .. figure:: schemas/rdc_motor.png
-    :scale: 75%
+    :width: 535px
     :alt: reversible DC motor circuit
 
     Reversible DC motor circiut
@@ -397,7 +397,7 @@ hardware events e.g. react to the alarm sensors or update item state when an
 external event is received.
 
 .. figure:: drivers-event.png
-    :scale: 75%
+    :width: 740px
     :alt: Drivers and events
 
     How the driver handles physical events

eva3/evahi.rst

@@ -12,7 +12,7 @@ You can use official `EVA ICS Control Center client
 :doc:`SFA<sfa/sfa>` UI from Android-based mobile phones.
 
 .. figure:: evacc.png
-    :scale: 50%
+    :width: 110px
     :align: right
 
 The client is evaHI-based application, so it can be `configured in the same way

eva3/integrations/cctv.rst

@@ -89,7 +89,7 @@ our agent and provide camera image (as well as any other resource from network
 **B**) for SFA.
 
 .. figure:: cctv_agent_schema.png
-    :scale: 30%
+    :width: 480px
     :alt: CCTV agent schema
 
 The task we are going to solve is pretty complex but it allows to transfer

eva3/integrations/elk.rst

@@ -31,12 +31,12 @@ Configure ELK
 - On the main Elastic dashboard, press "add data"
 
 .. figure:: elk-images/add-data.png
-    :scale: 50%
+    :width: 410px
 
 - Select "Logstash logs"
 
 .. figure:: elk-images/select-logstash.png
-    :scale: 50%
+    :width: 595px
 
 - Follow the given instructions and setup **filebeat** on all EVA ICS nodes.
 

eva3/integrations/grafana.rst

@@ -5,7 +5,7 @@ Grafana
 analytics and monitoring.
 
 .. figure:: grafana_hmi.jpg
-    :scale: 30%
+    :width: 550px
     :alt: Grafana dashboard
 
 Data

eva3/integrations/lora.rst

@@ -7,7 +7,7 @@ collect metrics from MQTT server or receive direct HTTP push messages with
 state payload.
 
 .. figure:: lora-images/lorawan.png
-    :scale: 75%
+    :width: 680px
     :alt: LoRaWAN network scheme
 
 .. contents::
@@ -45,12 +45,12 @@ Network configuration
 Open *Intrastructure->Network* page and create new LoRa network:
 
 .. figure:: lora-images/network.png
-    :scale: 75%
+    :width: 700px
 
 Open *Intrastructure->Gateways* and append your gateways.
 
 .. figure:: lora-images/gateway.png
-    :scale: 75%
+    :width: 695px
 
 Append EVA ICS back-end
 ~~~~~~~~~~~~~~~~~~~~~~~
@@ -86,20 +86,20 @@ and create "eva" application. Make sure "data" and "deveui" fields are
 selected:
 
 .. figure:: lora-images/handlers.png
-    :scale: 75%
+    :width: 670px
 
 Then open *Backends->Connectors* and create connector to :doc:`EVA UC
 <../uc/uc>`:
 
 .. figure:: lora-images/connector.png
-    :scale: 75%
+    :width: 715px
 
 don't forget to configure connector authentication. EVA ICS API key should have
 either permission to all items or to items with group "phi" and item id
 "A123456789123456" (PHI id we are going to push data in).
 
 .. figure:: lora-images/connector_auth.png
-    :scale: 75%
+    :width: 660px
 
 Append sensor to network server
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -108,12 +108,12 @@ Go to *Devices->Profiles* and create profile for the sensors, don't forget to
 select "eva" as back-end application:
 
 .. figure:: lora-images/profile.png
-    :scale: 75%
+    :width: 645px
 
 Then go to *Devices->Comissioned* and add the sensor:
 
 .. figure:: lora-images/device.png
-    :scale: 75%
+    :width: 660px
 
 .. note::
 

eva3/lm/lm_ei.rst

@@ -14,7 +14,7 @@ port is 8817), enter API key and press Enter to log in or **Remember API key**
 to log in and make your browser remember the key.
 
 .. figure:: ../ei-login.png
-    :scale: 70%
+    :width: 345px
     :alt: Login page
 
 Navigation
@@ -23,7 +23,7 @@ Navigation
 The navigation menu is at the top of the interface.
 
 .. figure:: lm-ei.menu.png
-    :scale: 70%
+    :width: 360px
     :alt: Navigation menu
 
 Use **Save** button to immediately store the runtime data base/configuration to
@@ -33,7 +33,7 @@ System information
 ==================
 
 .. figure:: lm-ei.sysinfo.png
-    :scale: 70%
+    :width: 280px
     :alt: Controller info
 
 System information is at the bottom of the interface. Clicking on the **Debug
@@ -51,7 +51,7 @@ Important: when you create/delete lvars, the interface does not automatically
 display the changes made. Use reload button or refresh the page in browser.
 
 .. figure:: lm-ei.lvars.png
-    :scale: 70%
+    :width: 685px
     :alt: LVars page
 
 Use **SET** button to set status and value of the variable, **RESET** button -
@@ -64,7 +64,7 @@ Macros
 On the :doc:`macros<macros>` page you can review defined macros.
 
 .. figure:: lm-ei.macros.png
-    :scale: 70%
+    :width: 685px
     :alt: Macros page
 
 You can run the macros, enable or disable their execution. As far as macros do
@@ -78,7 +78,7 @@ Decision rules
 The page displays the :doc:`decision-making rules<decision_matrix>`.
 
 .. figure:: lm-ei.rules.png
-    :scale: 70%
+    :width: 690px
     :alt: Rules page
 
 It allows you to add, edit, delete and disable/enable rules of decision-making
@@ -94,7 +94,7 @@ If you set the report level to *DEBUG*, interface automatically prompts you to
 switch the controller to debugging mode.
 
 .. figure:: lm-ei.log.png
-    :scale: 70%
+    :width: 690px
     :alt: Log viewer
 
 Disabling the interface

eva3/msad.rst

@@ -94,14 +94,14 @@ Log into Active Directory domain controller, open *Active Directory Users and
 Computers* and create organizational unit (default - *EVA*)
 
 .. figure:: msad_ou.png
-    :scale: 70%
+    :width: 330px
     :alt: create AD OU
 
 Create security groups inside organizational unit. Group name should match EVA
 ICS API key ID
 
 .. figure:: msad_group.png
-    :scale: 70%
+    :width: 550px
     :alt: create AD group
 
 Assign security group to domain user. If multiple security groups are assigned,

eva3/security.rst

@@ -32,7 +32,7 @@ The recommended enterprise configuration of the system is represented in the
 following scheme:
 
 .. figure:: network.png
-    :scale: 60%
+    :width: 605px
     :alt: secure network design
 
 * **Public network** external network (company's local network); applications

eva3/sfa/sfa.rst

@@ -14,7 +14,7 @@ SFA. Ids of the items should be always specified in oid form (*type:group/id*)
 and be unique in the whole installation.
 
 .. figure:: sfa.png
-    :scale: 100%
+    :width: 550px
     :alt: SCADA Final Aggregator
 
     Example of the controller aggregation with the use of two SFA servers

eva3/uc/uc.rst

@@ -9,7 +9,7 @@ console application.  Additionally, it can be integrated into other subsystems
 and third-party programs using :doc:`uc_api`.
 
 .. figure:: uc.png
-    :scale: 75%
+    :width: 725px
     :alt: Universal Controller subsystem
 
     You may use Universal Controller independently or integrate it with

eva3/uc/uc_ei.rst

@@ -14,7 +14,7 @@ port is 8812), enter API key and press Enter to log in or **Remember API key**
 to log in and make your browser remember the key.
 
 .. figure:: ../ei-login.png
-    :scale: 70%
+    :width: 345px
     :alt: Login page
 
 Navigation
@@ -23,7 +23,7 @@ Navigation
 The navigation menu is at the top of the interface.
 
 .. figure:: uc-ei.menu.png
-    :scale: 70%
+    :width: 290px
     :alt: Navigation menu
 
 Use **Save** button to immediately store the runtime data base/configuration to
@@ -33,7 +33,7 @@ System information
 ==================
 
 .. figure:: uc-ei.sysinfo.png
-    :scale: 70%
+    :width: 305px
     :alt: Controller info
 
 System information is at the bottom of the interface. Clicking on the **Debug
@@ -51,7 +51,7 @@ Important: when you create/delete units, the interface does not automatically
 display the changes made. Use reload button or refresh the page in browser.
 
 .. figure:: uc-ei.units.png
-    :scale: 70%
+    :width: 680px
     :alt: Units page
 
 On the page, you can:
@@ -69,7 +69,7 @@ On the :ref:`sensors<eva3_sensor>` page you can review the current value of
 each sensor, make it enabled or disabled.
 
 .. figure:: uc-ei.sensors.png
-    :scale: 70%
+    :width: 685px
     :alt: Sensors page
 
 Log viewer
@@ -80,7 +80,7 @@ If you set the report level to *DEBUG*, interface automatically prompts you to
 switch the controller to debugging mode.
 
 .. figure:: uc-ei.log.png
-    :scale: 70%
+    :width: 685px
     :alt: Log viewer
 
 Disabling the interface