Evaluate OptiMod
with your team.
Research teams and partner organisations can test OptiMod hands-on. Describe your question and dataset, agree the scope with the founders, then examine the scientific reasoning and results yourselves.
From your question to a hands-on review.
Use a case your team understands. A shared question and clear review criteria make it easier to judge where OptiMod fits your workflow.
Define the case.
Describe the analytical question, the intended users and a representative dataset. Include what one row represents and the outcome you want to understand.
Agree scope and access.
With the founders, choose appropriate data, the methods or outputs to examine and who should take part. Agree how your team will access the software and handle the data.
Use OptiMod yourselves.
Run the agreed analysis and inspect the method choice, assumptions, findings and Scientific Report. Record what your reviewers can verify and where they need further explanation.
Discuss the fit.
Compare your observations against the review criteria. Discuss coverage, open questions and the next step for your organisation or product.
Review the reasoning
behind the result.
These four questions give domain specialists and technical reviewers a common basis for assessing the software against the agreed use case.
- Method selection
- Does the selected method fit the analytical question, the outcome and the way the data were collected?
- Assumption checks
- Which assumptions were examined, what did the checks show, and what still needs expert judgement?
- Findings
- Can your team explain the result, its uncertainty and the limits on what can be concluded?
- Scientific Report
- Can a colleague follow the question, data, method, checks and findings from the record of the analysis?
Bring your first question.
Tell us about your organisation, the workflow and what you want to assess. A description of the dataset is enough for the first enquiry. The founding team will discuss suitable data, review criteria and access with you.