Giter Club home page Giter Club logo

daisie's People

Contributors

hhildenbrandt avatar joshwlambert avatar luislvalente avatar neves-p avatar rscherrer avatar rsetienne avatar xieshu95 avatar yangshen0325 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

daisie's Issues

Roxygenize NAMESPACE

NAMESPACE should be created using roxygen2.
This requires adding :: before function calls from other package, see f63027a.
I will convert to a new namespace to prevent having to juggle exported functions manually, and because the current namespace breaks pedro-ontogeny

DAISIE_format_IW fails when island empty

If ran:

set.seed(1)
DAISIE::DAISIE_sim(
  time = 10,
  M = 1000,
  pars = c(1.0e+00, 4.0e-01, 1.5e+01, 1.0e-04, 2.0e-01),
  replicates = 100,
  divdepmodel = "IW"
)

on any branch develop or above format IW fails due to btimes being empty.

Is the cladogenesis rate correctly calculated?

While working on #11, I noticed the following:
The cladogenesis calculation in get_clado_rate is different than the one in loglik_CS_time.

In the loglik_CS_time rhs function, it is computed this way:
lacvec <- pmax(rep(0, lnn), lac0 * (1 - nn / (area * K0)))

while in get_clado_rate it is computed like this:

clado_rate <- max(c( N * lac * island_area(timeval, Apars, island_ontogeny) * (1 - N / (island_area( timeval, Apars, island_ontogeny) * K)), 0), na.rm = T) where island_area evaluates to area as in above.

The question is: should the nn vector be included in the calculation (missing in the first example)? I added this vector in 9c72df4, which makes the null-ontogeny and ontogeny likelihoods (last test of DAISIE_test.R) be different, implying the change is incorrect. Is the N * term in get_clado_rate incorrect, then?
Asking @rsetienne for help, please!

DAISIE_ML1

  • Lint
  • Document
  • Increase coverage
  • Merge

Less verbose Travis output

I see in e.g. Josh's Travis build that Travis produces 10k lines of output. Due to this, one cannot read the reason why a build fails.

I suggest to follow the UNIX Golden Rule of Silence: if everything works, no output should be produced. In our contexts: tests should not produce output (unless you test them to have output, which is very rare).

I will try to assign @Neves-P to do this, he's perfectly able to let another team member fix this, as this is a rather easy Issue 👍

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.