From f1f7af44d5f596c15ad5346d9a462224f570b9b2 Mon Sep 17 00:00:00 2001 From: Graeme Winter Date: Tue, 2 May 2023 14:55:31 +0100 Subject: [PATCH 1/2] Empty roadmap --- README.md | 2 ++ ROADMAP.md | 0 2 files changed, 2 insertions(+) create mode 100644 ROADMAP.md diff --git a/README.md b/README.md index bbedd2c..3de84e3 100644 --- a/README.md +++ b/README.md @@ -15,3 +15,5 @@ files in directory | go into Meeting minutes are written collaboratively in the [HackMD DIALS team](https://hackmd.io/@dials) and can be directly pushed from there into this repository. + +[Roadmap - proposal](ROADMAP.md) diff --git a/ROADMAP.md b/ROADMAP.md new file mode 100644 index 0000000..e69de29 From b18778e6302a0c9b97dfe387402508285260b1be Mon Sep 17 00:00:00 2001 From: Graeme Winter Date: Tue, 2 May 2023 15:53:46 +0100 Subject: [PATCH 2/2] dials.integrate --- ROADMAP.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/ROADMAP.md b/ROADMAP.md index e69de29..966dbf5 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -0,0 +1,26 @@ +# Roadmap + +## Introduction + +In team meeting 2023-05-02 the need for a clear roadmap for where we want to take DIALS was identified, at least in terms of starting to tackle the backlog of issues and work out where we want to take the project. + +## Proposal + +Discuss the roadmap through a series of PRs against the `roadmap` branch with the conclusion being a functional plan. This needs to identify the path we take and the goals we want to achieve. + +## Immediate issues + +Propose the following issues to address: + +- memory use in `dials.integrate` + +This is a rather egregious and evergreen issue, cast into sharp relief every time I teach at a workshop. + +## Possible solutions + +`dials.integrate` memory footprint: + +- revisit structure of `dials.integrate` +- consider reimplementation against existing API, perhaps as a straight binary + +Could form part of a "little dials" project, perhaps?