GithubHelp home page GithubHelp logo

codyn's People

Contributors

aammd avatar cgries avatar flynn-d avatar gavinsimpson avatar gothub avatar itcarroll avatar jameslamb avatar laurenmh avatar mavolio avatar mbjones avatar sydjones avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

codyn's Issues

meanrank() does not handle non-standard column names

The meanrank() function is supposed to take a data frame and the names of the year, species, and abundance variables as input. But if a data frame is passed in that uses non-standard variables, the mean rank shift calculation results in all values as NaN. It appears no attempt is made to handle the non-standard column names. I will commit a test that reproduces this bug, which can be run with the test() command.

time lag function: goals and inputs

Working through the rate_change code, need to get it to the state where input is longform and there is the opportunity for replication. Happy to help with that but I'm not totally sure what the test statistics should be -- should I be extracting the coefficient and p value for the lag? a/o R squared? I think we'll probably want the output to be a dataframe with the relevant test statistics paired with the replicate, but I'm not totally sure what they should be, will get unwieldy to have it be the full model summary. Thoughts?

create turnover metrics

Turnover metrics

  • appearance, disappearance, both
  • crash metrics
  • Beautify / refactor functions
  • net change between years

tests for variance ratio

Need full tests for variance ratio metrics, including for functions:

  • calVR
  • calVR2
  • getRand
  • calNullVR
  • nullVRCI
  • calVRrealnull
  • VR

review and revise function names

The current function names are good, but might be improved for clarity and intuitiveness. By checking this before the package is released, we will make it easier for people to understand each function and its purpose. We should also check if these function names are already in use in other CRAN packages. The current function names from the NAMESPACE export file to be checked are:

  • VR
  • calVR
  • calVR2
  • calVRrealnull
  • calnullVR
  • genRand
  • meanrank
  • nullVRCI
  • pairwise_turnover
  • timelag
  • synchrony
  • synch_onerep
  • calComDat -> rename to transpose_community()
  • calComTS -> deleted function

Check each off once we have agreement to keep the function name.

standardize argument names

  • timevar -> time
  • year -> time
  • speciesvar -> species
  • abdvar -> abundance
  • data1 -> data
  • rep -> replicate

collins08.csv data cleaning and meanrankshift trouble shooting

The collins08.csv has multiple entries for the species asclvird in all years and replicates, and for the species desmilli in the unburned replicate for years 1994 and 1998. This is causing an indexing error because all our functions require unique abundance values for a species within a year and replicate.

Syd - want to have a look at the collins08.csv and figure out the data cleaning issue? Note that I moved it to the inst/extdata folder

Even when I select years with unique values, this aspect of the meanrank code gives me trouble with collins08.csv but not kn_001d.csv, still trouble shooting:
commonspp <- Map(getintersect, y1, y2, dataname = species)

test: check names

add a check in the wrapper of each function to make sure that the names passed are the names present

tests for synchrony metrics

Need tests for synchrony metrics. I added a stub test file, but the meat of the test needs to be completed.

torus translation functionality

need to shift code from the varianceratio function to the temporal_torus_translation_CI function to make it easy to calculate CI either within or across replicates. If across, need to run each iteration of the null model once, average across replicates, and then repeat.

Fix build errors in time timelag_analysis

Current timelag metrics file doesn't allow the package to build because of missing variables and potentially other issues. Refactor to allow the package to build.

edit vignettes

  • add rate_change example to temporal diversity vignette
  • write codyn overview
  • make figures larger
  • move rank clocks example to temporal diversity indices
  • rename vignettes, delete collins08 once material is moved
  • flush out gross discussion
  • clean up citations

Add function for returning rate change data frame

The current rate_change() returns the slope of the rate change data. Some people have requested the ability to get the lagged data themselves. Implement new functions by refactoring get_slope().

Remove dependency on reshape

Lauren H indictaed that we could remove all dependencies on reshape to simplify the package. Matt agreed to do so.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.