Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Software priorities for paper #321

Closed
40 of 46 tasks
MichaelClerx opened this issue Apr 3, 2018 · 6 comments
Closed
40 of 46 tasks

Software priorities for paper #321

MichaelClerx opened this issue Apr 3, 2018 · 6 comments

Comments

@MichaelClerx
Copy link
Member

MichaelClerx commented Apr 3, 2018

Hi all!

Just talking to @ben18785 about the things we really need to do for the paper. Thought it'd be good to make an overview ticket.

MCMC Methods

Nested methods

Particle-based methods

Likelihood-free methods

  • ABC --> Leaving this for paper 3, Would be a good student project too

Toy problems #119

Features

Functional tests

Unit tests

Documentation

  • Notebooks are so slow they keep failing the daily test

Infra

Comparison

@MichaelClerx MichaelClerx changed the title Priorities for paper Software priorities for paper Apr 3, 2018
@MichaelClerx
Copy link
Member Author

MichaelClerx commented Apr 3, 2018

Questions:

@martinjrobins
Copy link
Member

martinjrobins commented Apr 4, 2018

Should we talk about software design, or leave that for a separate paper?

I'm guessing we'll need a separate paper for this, to concentrate on it fully, although we should describe the ask-and-tell interface in broad terms and point to a hierarchical MCMC example (which I still need to do) as an example of its utility.

@MichaelClerx
Copy link
Member Author

Should we add MALA to the MCMC list for the paper? @sanmitraghosh @ben18785 ?

@sanmitraghosh
Copy link
Contributor

Yes MALA, needs L'(p) and smMALA, needs L''(p)

@sanmitraghosh
Copy link
Contributor

sanmitraghosh commented Apr 17, 2018

@MichaelClerx @martinjrobins @ben18785 I just want to touch up on this point that we should test all single chain MCMC methods with the FN model and particle ones with GW model. I think this is extremely important at this points or else we might run into the scenario that we have many algorithms (and associated infrastructures) that are not suited for complex ODE models. There is no point in collecting algorithms that can solve the logistic problem.

I think any algorithm that has not been published (and hopefully cited) with a working non-linear ODE example in the originating paper should be subjected to the aforementioned models FN/GW (performance on the logistic model is absolutely irrelevant for our chosen endeavour) before even implementing within PINTS. This will save us a lot of time and hassle.

@mirams mirams self-assigned this Jul 17, 2018
@MichaelClerx
Copy link
Member Author

Closing this issue now, as it has been replaced by a GitHub Project!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants