Create a wish list container for all prospective sampling / optimisation methods

[ben18785]

Much more useful than creating an issue for each new method would be to put it into a useful container, which can be visualised to make sense of the work that will be done.

I am thinking it would be displayed on our main Github landing page or elsewhere; ideally as a sort of (collapsable) tree diagram where it is shown how each method relates to others. It would also have clickable links that direct users / developers to the original papers that created the methods. We could colour each node according to whether the method is implemented, in progress, or in the future.

Perhaps, this could be coded in JSON?

[MichaelClerx]

That does sound nice, but would require quite a bit of work and upkeep!

Not saying we shouldn't, but just to point out some possible snags:

• A lot of the feature issues are things we stumble on, so would require a bit of work to figure out where they go. We'd end up needing another place to post "todo: look at method x" issues then
• We'd still need an issue if/when we started implementing each method
• Figuring out the tree structure for optimisation is still an open issue (see Add more optimisers #684)

Perhaps a simpler issue would be to just stick them all in a single issue per class?

[MichaelClerx]

implemented, in progress, or in the future.

We might also want "out of scope" and a politer version of "not interested" ?

[ben18785]

Haha, yep! That's a good idea.

…

On Wed, Jul 31, 2019 at 11:54 PM Michael Clerx ***@***.***> wrote: implemented, in progress, or in the future. We might also want "out of scope" and a politer version of "not interested" ? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#886?email_source=notifications&email_token=ABCILKGTV2CUOGQ26LTQZRLQCIJZDA5CNFSM4IILEWJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IZNDI#issuecomment-517052045>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABCILKDQZTOFPPX7M54IQ33QCIJZDANCNFSM4IILEWJA> .

[MichaelClerx]

Can we consider this one done now, @ben18785 ?

[ben18785]

Yep!

…

On 31 Aug 2019, at 19:28, Michael Clerx ***@***.***> wrote: Can we consider this one done now, @ben18785 ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.