A description of the first MAIA stage and the configurable parameters.
The first stage of a MAIA job processes all images of a volume with an unsupervised novelty detection method. The novelty detection method attempts to find "interesting" objects or regions in the images, which are called "training proposals". The novelty detection acts without any prior knowledge of what is actually defined as interesting by you or anyone who wants to explore the images. Hence, the quality or meaningfulness of the training proposals may vary dramatically, depending on the images themselves and on what you are looking for.
To make the novelty detection as flexible as possible, there are many parameters that can be configured before a new MAIA job is submitted. You might have to try out a few parameter combinations before the novelty detection produces meaningful training proposals. In cases where the novelty detection produces too few meaningful training proposals or does not work at all, you can augment the training proposals with your own annotations or skip the novelty detection altogether.
Once the novelty detection is finished for a MAIA job, it will continue to the training proposals stage.
By default only the two parameters for the novelty detection are shown, that are the most likely to be modified for each new job. To show all configurable parameters, click on the button below the form.
This parameter specifies the number of different kinds of images tha you expect. Images are of the same kind if they have similar lighting conditions or show similar patterns (e.g. sea floor, habitat types). Increase this number if you expect many different kinds of images. Lower the number to 1 if you have very few images and/or the content is largely uniform.
If your novelty detection results in many large training proposals for very dark, bright or otherwise unusual images, consider to increase the number of image clusters and run the novelty detection again in a new MAIA job.
The number of image clusters is denoted as K in the MAIA paper .
This parameter specifies the size in pixels of the image patches used determine the training proposals. Increase the size if the images contain larger objects of interest, decrease the size if the objects are smaller. Larger patch sizes take longer to compute. Must be an odd number.
The size of objects or regions of interest is relative to the image and directly depends on the distance between the objects and the camera (e.g. the sea floor and the camera). If the camera is close to the objects, choose a larger patch size, if the camera is farther away, choose a smaller patch size.
The patch size is denoted as re in the MAIA paper .
This is the percentile of pixel saliency values used to determine the saliency threshold. Lower this value to get more training proposals. The default value should be fine for most cases.
The threshold percentile is denoted as P99 in the MAIA paper . The 99 is the parameter that you can configure here.
The learning capability used to determine training proposals. Increase this number to ignore more complex "uninteresting" objects and patterns.
The latent layer size is denoted as the compression factor in s = [0.1r] in the MAIA paper . The 0.1 is the parameter that you can configure here.
The number of training image patches used to determine training proposals. You can increase this number for a large volume but it will take longer to compute.
The number of training patches is the number of samples that is used to train an autoencoder network for one cluster of images Uk as described in the MAIA paper .
This parameter specifies the time spent on training of an autoencoder network when determining the training proposals. The more time is spent on training, the more complex "uninteresting" objects or patterns can be ignored.
The number of training epochs is the number of epochs that each autoencoder network is trained for one cluster of images Uk as described in the MAIA paper .
A higher stride increases the speed of the novelty detection but reduces the sensitivity to small regions or objects. Set the stride to 1 to disable the speed optimization and process the images in their original resolution. In the MAIA paper , we found that a stride of 2 does not reduce the performance of the novelty detection. You might be able to use an even higher stride than that.
The stride is used for the "convolution operation" in which each DBMk is applied to the images of a cluster Uk as described in the MAIA paper .
Integer greater than or equal to
Ignore training proposals or annotation candidates which have a radius smaller or equal than this parameter in pixels. You can use this to filter out training proposals that have a smaller size than the objects or regions of interest that you expect. Fewer training proposals mean a lower workload for you in the training proposals stage of MAIA. The default value of 5 pixels is sensible because it is unlikely that smaller objects can be accurately identified.
In the MAIA paper  no training proposals were ignored which is equivalent to an ignore radius of 0.
If you already have existing annotations for the volume or the novelty detection does not produce (enough) meaningful training proposals, you can select the checkbox "Use existing annotations" before you submit a new MAIA job. When this checkbox is checked, the existing annotations are also presented as training proposals in the second MAIA stage.
If the checkbox is selected, a new input appears that allows you to limit the used existing annotations to one or more labels. This way you can select only those annotations that make sense as training proposals. If you do not choose any label, all existing annotations are used as training proposals.
If you chose to use existing annotations as training proposals, a new checkbox to "Skip novelty detection" appears. Select this checkbox if you do not want to run the novelty detection at all and only want to use the existing annotations as training proposals.
Please note that the new MAIA job is shown as "running novelty detection" in the job overview page even if you chose to skip novelty detection. Just refresh the job overview page after a few seconds and the job should have proceeded to the second MAIA stage.