UCL / UCL/TLOmodel

First Task for ECSA Developers

Open
#1,319 2 comments 0 reactions 1 assignee View on GitHub

@tamuri is already working on this.

Since Jul 1, 2026.

potential project
Dominant language
Python
Stars
35
Forks
17
PR merge metrics
No merged PRs in 30d

Description

The ECSA Developers will be "power-users" of the TLO modelling framework and developers focussed on make the model easy to use applicable in other settings. They will also take the role of trainers / supporters of other using the model.

The on-boarding process will proceed in three phases:

  1. Work on conducting a real analysis. This will entail getting to grips with the codebase and all our systems and processes. It will also help us accomplish an analysis from our analysis planner. This will done collaboratively with other team members, especially those at KUHeS. [See below.]

  2. Write a manual that explains in detail the process of conducting an analysis. This will be a step-by-step "How to" guide that will be suitable for novice users. It will have installation instructions, examples, code snippets etc. etc. It will written-up as code [@tamuri will advise on the best way of doing this] and kept fully up-to-date as advances in the code are made. Where this inspires changes to the code/processes, these will be raised as Issues.

  3. Collect up all the issues that are entitled with making the TLO model easy to use for novice users, and applicable in other settings and develop a roadmap of enhancements that will accomplish this. Use GitHub tools to manage this transparently as a project.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.