Configuration (Normal mode)
Whether you are planning to run jobs in Normal Mode to process raw data, or whether you plan to use Viewer Mode to run tasks on processed data, the Batch Processor module always runs in Normal Mode.
To configure the batch processor, start PAMGuard in normal mode with a new / blank configuration and add two modules: a database and the batch processor module.
No other modules should be added to the configuration, except perhaps a User Input module which would allow you to make notes about what you’ve been doing with the batch processor.
On no account should you add any Sound Processing, or Detection, Classification, or Localisation modules to this configuration which should now look something like the image below.
Select Operation Mode
In the top left “Job Control” panel select “Raw data processing (normal mode)”.
Detector Configuration
The detectors and other sound processing you want to perform on your data are all controlled from the Configuration panel at the top of the display. Here, you select the configuration file that you want to use to process all of your different batch jobs with exactly the same settings.
The most common thing to do, is to take a configuration file that you are already happy with, and have tested on some of the data, and select that configuration using the Browse button, however, you can also use the Browse button to create an empty configuration to work with and then add the modules you require.
To view or modify the configuration, press “Launch Configuration”. This will open the configuration in a separate PAMGuard window where you can view and modify any of the sound processing and detector settings.
Don’t worry about which folder of sound files, database, and binary store are set in the configuration. These will all be overwritten with new values for each job when it runs.
Remember to save the configuration when you’ve made modification, or the changes may not get used when you come to process new data
Calibration Data
Even if you’ve deployed near identical instruments, you may have slightly different calibration data for each one, or perhaps hydrophone spacing changed slightly in towed arrays used in different years. Once you’ve added jobs you can set calibration data individually for each dataset. Changes to the hydrophones are the only differences you’ll be able to make between the configuration running on each of your datasets.