Merging in split and merge algorithm

[boshek]

The split and merge algorithm is a method to auto-detect layers in the water column. Key considerations/conversations prior to merging:

• Does the wtr_layer() make sense in the context all the other functions in this package? It currently outputs the mix layer depth, a cline (depending on what parameter is chosen) and the segments calculated as a list column. This is a handy was to store data is different [i,j] inside the same dataframe. Consider this example:

  > df1 <- wtr_layer(depth=latesummer$depth, measure = latesummer$temper)
  > df1
  min_depth nseg    mld    cline
  1       2.5    4 7.0565 16.39025
                                                                  segments
  1 2.59800, 7.05650, 25.72400, 98.13900, 17.94060, 17.38405, 5.51445, 4.46375
  > df1$segments
  [[1]]
  segment_depth segment_measure
  1        2.5980        17.94060
  2        7.0565        17.38405
  3       25.7240         5.51445
  4       98.1390         4.46375

• I've added the internal dataset latesummer into the package
• Because I've merged two repos, our commit history will also be merged
• I have a small vignette that I will expand in rmarkdown. Have you ever considered that format for vignettes? Currently checked out of the repo because it is arguing too much with TRAVIS
• FYI: @DougCollinge

Technique and limnological references

• Pavlidis, T., and S. L. Horowitz, 1974: Segmentation of plan curves.IEEE Trans. Comput., C-23, 860–870.
• Thomson, R. and I. Fine. 2003. Estimating Mixed Layer Depth from Oceanic Profile Data. Journal of Atmospheric and Oceanic Technology. 20(2), 319-329.
• Fiedler, Paul C. "Comparison of objective descriptions of the thermocline. Limnology and Oceanography: Methods 8.6 (2010): 313-325.

[lawinslow]

@boshek Awesome contribution. Thanks! I'll review this later today or tomorrow so we can get this in and onto CRAN soon!

[lawinslow]

I have a small vignette that I will expand in rmarkdown. Have you ever considered that format for vignettes? Currently checked out of the repo because it is arguing too much with TRAVIS

Definitely interested in vignettes. Don't care about the format. The only reason we have legacy format documentation is that this is an old package started before those other things were popular (or even existed). It would be great to include.

[boshek]

With respect to vignettes I will have to submit that as a separate pull request because I think having two vignette builders would be a hassle.

[lawinslow]

Separate PR for vignette makes sense. The rest of this looks awesome. Thanks!