LOI, LOO

[GoogleCodeExporter]

Functions to perform leave-one-out, leave-one-in, and retrospecive analyses. 
Functions should return an FLSAMs object.

LOI and LOO can be implemented relatively simply.

There already exists code created by Anders to perform a retro - this is a nice 
little trick, as it reuses the previous assessment to provide initial 
conditions. We should take advantage of this. LOI and LOO could also apply 
similar tricks, based on what we learn from retro

Original issue reported on code.google.com by markpayn...@gmail.com on 2 Nov 2011 at 2:16

[GoogleCodeExporter]

Original comment by markpayn...@gmail.com on 2 Nov 2011 at 2:17

• Added labels: Priority-Medium

[GoogleCodeExporter]

e.g. LOO(<stck>,<tun>,<ctrl>)
the function code would first get the list of index names, then remove the 
corresponding survey from the tun and ctrl objects. ctrl would be updated. Then 
the assessment would be performed as normal. The functon would return an FLSAMs 
object that can be analysised using plot(<FLSAMs>) the susan is developing, and 
also on top of the otolith plot.

Original comment by markpayn...@gmail.com on 2 Nov 2011 at 2:18

[GoogleCodeExporter]

Original comment by markpayn...@gmail.com on 2 Nov 2011 at 2:53

• Added labels: FLSAM

[GoogleCodeExporter]

LOI and LOO implemented as 'looi'. Retro gets its own issue

Original comment by Niels.Hintzen on 3 Nov 2011 at 9:46

• Changed title: LOI, LOO

[GoogleCodeExporter]

Original comment by Niels.Hintzen on 3 Nov 2011 at 9:47

• Changed state: Done

[GoogleCodeExporter]

Original comment by markpayn...@gmail.com on 4 Nov 2011 at 8:07