• Add new functionality: selection of fishdayId instead of haulId. Online meeting 22/06/2020.

would be nice if the code would allow graphical view on the impacts of sampling alternatives in terms of

• workload: number of samples obtained / number of fish
• coverage:
  -- species (sprat vs herring)
  -- long vs short trips
  -- vessel size
  -- subdivisions
  -- rectangles
  -- cooperative vs non-cooperative vessels
  -- vessel in vessel-list vs non-vessel list
  Online meeting 17/06/2020.

Would be nice to have confidence intervals for outputs expected from sampling (e.g., 2.5 and 97.5 quantiles of number of samples per subdivision and species). Online meeting 17/06/2020.

Some countries do not have haul-by-haul data. A reasonable approximation to the haulId variable can be created from available min resolution data when number of hauls is available. E.g. by spliting the daysgeararea*rect catch evenly by the number of hauls. Would be nice to have a function for that splitting taking as input the 2019 data call format with an added column "nHauls"

Could be useful to have an option that allows simulation of refusals at vessel level (i.e., one vessel refuses) - could be random or on a target group of vessels. Online meeting 17/06/2020.

• add possibility of taking 1 sample from all trips of the vessel list. Online meeting 22/06/2020.

Check if possibility of % proportion in sample with everything processed (including when <50 fish) is implemented.

would be nice to have a vignette documenting an example run on the testData

Would be nice to have the possibility of haul selection along the rate of quota consumption; and something similar to the Norwegian lottery.

Seems to be reducing the number of hauls

would be nice to have the script for outputs (could be a shiny, could be a pdf) separated from the script that runs the simulations

• add code that runs simulations N times. Online meeting 17/06/2020.

Would be nice to have the the following maps (maybe a function with different inputs)

• samples obtained (number of hauls per rect, number of fishing*days per rectangle)
• samples potentially obtainable (all activity of vessel in the target_list)
• all samples available in fleet (all activity of all vessels, including those outside the target_list)
  Online meeting 22/06/2020.

If algorithm involves next trip even within week - how will the sampling proceed: is the vessel removed from list while pending that next trip? and how will the estimation be done if so?

Currently simulations involve same number of vessels selected each week. Would be useful to add possibility of different vessel numbers per week to accomodate for different number of staff being available to go and collect samples in the different weeks. Online meeting 22/06/2020.

• presently algorithm takes 1st trip next week. would be nice to have the possibility of next trip (even if in the same week).

The function expects a 'none' strata

Presently all hauls are assumed sampled in a trip. would be useful to have the possibility of 1st haul, last haul, random haul too. Online meeting 17/06/2020.