Skip to content

Commit

Permalink
slight improvements
Browse files Browse the repository at this point in the history
  • Loading branch information
MalteEbner committed Sep 8, 2022
1 parent 58cccb7 commit 3756e66
Showing 1 changed file with 9 additions and 4 deletions.
13 changes: 9 additions & 4 deletions docs/source/docker/getting_started/selection.rst
Expand Up @@ -78,8 +78,12 @@ Each strategy is specified by a :code:`dictionary`, which is always made up of a
.. code-block:: python
{
"input": ...,
"strategy": ...
"input": {
"type": ...
},
"strategy": {
"type": ...
}
},
Expand Down Expand Up @@ -490,14 +494,15 @@ The Lightly optimizer tries to fulfil all strategies as good as possible.
- **Tradeoff between different objectives.**
The optimizer always has to tradeoff between different objectives.
E.g. it may happen that all samples with high WEIGHTS are close together. If you also specified the objective DIVERSITY, then only a few of these high-weight samples
may be chosen. Instead, also other samples that are visually more diverse, but have lower weights, are chosen.
may be chosen. Instead, also other samples that are more diverse, but have lower weights, are chosen.

- **Restrictions in the input dataset.**
This applies especially for BALANCE: E.g. if there are only 10 images of ambulances in the input dataset and a total
of 1000 images are selected, the output can only have a maximum of 1% ambulances. Thus a BALANCE target of having 20% ambulances cannot be fulfilled.

- **Too little samples to choose.**
If the selection algorithm can only choose a small number of samples, it may not be possible to fulfil the objectives. You can solve this by increasing :code:`n_samples`.
If the selection algorithm can only choose a small number of samples, it may not be possible to fulfil the objectives.
You can solve this by increasing :code:`n_samples` or :code:`proportion_samples`.

Selection on object level
-------------------------
Expand Down

0 comments on commit 3756e66

Please sign in to comment.