Iterative analysis

[anwarfg]

Is this the right issue type?

• Yes, I'm planning work for this project team.

Summary

Some analyses have to be done in an iterative manner. These include some common analyses like cox regression. This is also critical if we are to entertain the idea of machine learning.
This means that the system has to be able to support this type of workflow, and that it has to be benchmarked and optimised, for this type of workflow. In particular, bottlenecks have to be reduced or removed entirely. Egress must become automatic, and communication overhead minimised. Aggregation must become automatic within this workflow (e.g., by SACRO or equivalent), and criteria must be checked to stop and egress. We have to consider whether this can be done by the researcher, or by a TRE/aggregator within the network.

Acceptance Criteria

• Automatic disclosure checking for iterative workflow.
• Minimised latency for communication of this type of workflow (e.g., polling times or methods).
• Iterative workflow supported.
• Automatic aggregation and resubmission
• Iteration stops on predetermined criteria
• Final results egressed
• Tests pass.
• Documentation added.

Confirm creation

• Ready to create this feature?