-
Notifications
You must be signed in to change notification settings - Fork 5
4 July 2019
Ilektra Christidi edited this page Jul 4, 2019
·
5 revisions
- Introductions and project walkthrough
- Requirements capture: minimum, preferable, "would like".
- Cleaning the repo: clarification
- (Ideally) User stories. Who is going to be the user?...
- Plan of future meetings, when, how often, what's expected...
- Discuss way of working eg:
- when and who can approve/merge PRs
- communication channels - slack room?
- CI to use and from which organisation: at UCL we have the advantage of admin so we can add people, services, etc., as well as paid Travis
- where to keep information that's not exactly documentation (eg. the wiki and issues)
- Development branch
- Requirements:
- Release of current stuff (once smoothn works) - end of July:
- pip/conda installable, only linux, unit tests, documentation
- identify possible places to gain performance, put in issues
- Lots of data: parallel processing. Already run something similar with dask on cluster.
- Future: add second step of spatial refinement, computational challenges will be there (scipy's minimize function applied on all pixels, and is computationally intensive, scales with image size)
- Release of current stuff (once smoothn works) - end of July:
- It's supposed to be a library, move
__main__'s to tests and/or examples - TODO: invite Jose to the slack channel, get Feng's info as well to invite to slack, meetings, etc.
- TODO: book meetings: 1 day/week work at Jose's, progress meeting biweekly. Mid-week preferable.