Service overview
Writing support for original research articles across computational, AI and experimental work. This service is part of that division and is scoped individually around what you need to learn, decide or publish.
Computational and simulation papers present evidence generated by models, and readers need to judge how far to trust it. Unlike an experiment, a simulation can always be run again, and the question is whether it is correct, relevant and described well enough to be reproduced. Reviewers of such papers look for verification, validation, convergence evidence, sensitivity analysis and the availability of enough detail to repeat the study.
Many computational manuscripts are rejected not for the quality of the model but for incomplete reporting: missing mesh details, unspecified boundary conditions, no comparison with independent data, or conclusions that extend beyond the tested range. Writing support aims to present the simulation work completely and honestly, with a clear logic from model to claim.
What this service covers
Problems this service can address
- Reviewers questioning mesh independence or validation
- Insufficient model detail for reproducibility
- Results presented without clear comparison to reference data
Methods and analytical approaches
- Model-documentation structure (governing equations, assumptions, parameters)
- Verification and validation reporting
- Presentation of convergence and sensitivity evidence
- Figure design for field results and comparisons
Applications
- CFD and FEA research papers
- Numerical-method development papers
- Multiphysics modelling studies
Relevant engineering disciplines
Scope, inputs and deliverables
Scope of work
- Assessment of your material: data, methods, draft and target venue
- Structuring and drafting or editing strictly from your supplied results and methods
- Consistency and source checks on text, tables, figures and references
- Journal-formatted files and a submission checklist
- Feasibility check on: simulation outputs, mesh and settings details
Typical inputs required from you
- Simulation outputs, mesh and settings details
- Validation data or references
- Draft or outline
Deliverables
- Manuscript with a reproducible methods section
- Validation and convergence reporting suggestions
- Figure and table design
Highly specialised requests are first checked for feasibility from this information. Please do not send confidential data through the public form; describe it first and agree secure transfer afterwards.
Project workflow and method
- 01Enquiry and requirement assessment
- 02Technical scoping and proposal
- 03Execution
- 04Quality review and delivery, with an agreed round of revisions
Read the full project workflow.
In depth: how the work is done
Presenting the model and its assumptions
A computational paper should state the governing equations or algorithm, the assumptions and the domain of validity before describing results. Assumptions should be justified or acknowledged as simplifications. Where established software is used, the version and settings are given, and where custom code is used, the approach to verification and availability is described. We help authors write this section so that a reader can see exactly what was solved.
Verification, validation and convergence
Verification asks whether the equations are solved correctly, shown through mesh and time-step convergence and comparison with analytical solutions. Validation asks whether the model represents reality, shown through comparison with experiments or independent data. We check that the manuscript presents both, with quantitative measures, and that where validation data do not exist the limitation is stated without implying validation.
Sensitivity and uncertainty reporting
Results depend on inputs that are uncertain. Papers that show how conclusions change with parameter variation are more credible than those reporting a single run. We help present sensitivity studies in a compact way, using tornado charts or tables, and ensure that the discussion distinguishes robust findings from those that depend on specific assumptions.
Reproducibility and code or data availability
Journals increasingly expect data-availability statements, and many encourage code sharing. We help authors prepare clear statements, document input files and parameters, and consider repositories with persistent identifiers. Where data cannot be shared, the manuscript explains why and what is provided instead, such as detailed parameter tables.
Choosing figures for simulation results
Contour plots, streamlines and time histories are visually attractive but can mislead without scales and context. We recommend consistent colour maps, colour-blind-safe palettes, quantitative line plots for comparisons and clear marking of the regions of interest. Fields shown should connect to the claims in the text.
Positioning the novelty
Computational novelty may lie in a new method, a new application or new insight from a known method. Each requires a different framing and a different comparison with prior work. We help authors position the paper accordingly and avoid presenting routine application of standard software as methodological innovation.
Quality control and good practice
Quality-control approach
- Every statement, number and reference is checked against your supplied data and the original sources.
- No data, results, citations or author contributions are invented; gaps are flagged to you.
- Authorship and contribution decisions stay with you and your co-authors, and the use of AI tools is disclosed where journals require it.
- Journal guidelines and reporting checklists are followed; acceptance is never promised.
Common pitfalls this service helps avoid
- No convergence evidence. Readers cannot tell whether results are numerical artefacts.
- Validation implied but not shown. Agreement with a different case does not validate the present one.
- Single-run conclusions. Without sensitivity analysis, robustness is unknown.
- Unreported solver settings. Missing details make the study irreproducible.
What good reporting looks like
Support for a computational manuscript is documented through a checklist covering model description, verification, validation, sensitivity, reproducibility statements and figure quality, with each item marked as provided by the authors, requested or not applicable. The deliverable is an author-approved manuscript. We do not run simulations to add results, invent validation data or promise acceptance.
An illustrative scenario
Hypothetical example written for explanation. It is not a client case, a result or a testimonial.
Suppose a researcher submits a CFD study of heat transfer in a new geometry. The draft shows impressive contours but no mesh study. After being asked, the researcher supplies results from three meshes, which are summarised in a table with a convergence index. The validation section is limited to a related geometry, so the paper says so and describes the new geometry's results as predictions awaiting experimental confirmation. The revised manuscript is clearer and more defensible.
Questions to settle before you begin
- What evidence shows my solution is converged?
- What independent data validate the model?
- How do my conclusions change with uncertain inputs?
- Can others reproduce the study from my description?
- Is my novelty a method, an application or an insight?
Key terms
- Verification
- Checking that equations are solved correctly.
- Validation
- Checking that the model represents reality.
- Grid convergence index
- A measure of discretisation uncertainty.
- Sensitivity analysis
- Study of how outputs vary with inputs.
- Data availability statement
- A declaration of where data and code can be accessed.
Working together on Original Research Manuscripts projects
Manuscript engagements begin with an assessment of what you have: results, methods, figures, a draft and the target journals. We ask for the underlying data or analysis outputs, because every statement in the manuscript must trace to them. Drafting and editing proceed in stages, with queries to you whenever a claim, number or reference cannot be verified from the material supplied. Authors review and approve every version. We never invent data, results, citations or contributions, and we do not promise acceptance, which is decided by editors and reviewers.
Frequently asked questions
Do you run the simulations for the paper?
Computation is a separate service (for example CFD or FEA). The manuscript service writes up work that has been done. We do not report simulations that were not performed.
Do you rerun my simulations?
That is a separate analysis service. Manuscript support works from the results you provide.
Can you help with a code-availability statement?
Yes. We help word statements and organise documentation for repositories.
What if I have no experimental validation?
We help state the limitation honestly and use available benchmarks or analytical checks where appropriate.
Can you adapt the paper to a numerical-methods journal?
Yes, by adjusting emphasis towards the method and its verification.
Does ENGRexpert guarantee acceptance in a journal?
No. Editors and reviewers decide. We support the clarity, rigour and fit of your manuscript and never promise an outcome.
How is this service scoped and priced?
After your enquiry we review what you need, ask for missing information and send a written scope and quotation. Price depends on complexity, deliverables and timeline. See the project workflow.