Signals Image Artist: Disabling local Batch Analysis submission

It's safe to remove the local Batch Analysis job queues, as long as an external (remote cluster) job queue has been configured - SImA expects at least one available queue. The workflow involves overwriting the existing queue configurations with empty files, which would ensure the local queues are no longer listed via the SImA UI.  
 
The workflow to disable all 3 queues (SImA_default, SImA_quick and SImA_debug) would look like this. 
 
Generate a blank config file for each of the 3 existing job queues:

• At the SImA server command line interface, navigate into the config directory found in the SImA installation directory.
• Create 3 configuration files and give them some content:

$ touch disable-SImA-default.config disable-SImA-quick.config disable-SImA-debug.config

$ echo "#" | tee disable-SImA-default.config disable-SImA-quick.config disable-SImA-debug.config > /dev/null

Pass the empty config files to the batch-analysis container:

Add the following content to the docker-compose-custom.yml file found in the SImA installation directory. 
 

services:
  batch-analysis:
    configs:
      - source: disable-default_queue        
        target: /etc/columbus/SImA-default.config
      - source: disable-quick_queue
        target: /etc/columbus/SImA-quick.config
      - source: disable-debug_queue
        target: /etc/columbus/SImA-debug.config

configs:
  disable-default_queue:
    file: config/disable-SImA-default.config  
  disable-quick_queue:
    file: config/disable-SImA-quick.config
  disable-debug_queue:
    file: config/disable-SImA-debug.config  

Note: If the docker-compose-custom.yml already contains any of the line entries listed above (e.g. the services: or  configs: lines), do not duplicate the entries. Omit the lines from the example above as required, so that the overall yaml structure is maintained. Please consult the Revvity Support team for clarification as required.  

If a given job queue must be reinstated, omit the "source" and "target" lines under the batch-analysis mapping shown above. For example, if the SImA_debug queue should be reinstated, comment the lines as shown below (or remove them completely): 

services:
  batch-analysis:
    configs:
      - source: disable-default_queue        
        target: /etc/columbus/SImA-default.config
      - source: disable-quick_queue
        target: /etc/columbus/SImA-quick.config
#     - source: disable-debug_queue
#       target: /etc/columbus/SImA-debug.config

The SImA stack would need to be redeployed for these changes to take effect.