Computational Models and Simulations
SciViD
SciViD welcomes original computational and theoretical research, including numerical simulation, analytical modeling and machine-learning models, as well as reviews of models and methods. Video allows authors to show how a model is set up, how it behaves as parameters change, and how its output compares with theory or experiment.
Paper categories
1. Numerical and analytical modeling
Original research in which the authors’ own code or modeling software (for example MATLAB, COMSOL, ANSYS, LAMMPS or custom Python code) produces new results.
Requirements: Describe the model and the numerical method. Report verification (for example convergence and mesh or time-step independence) and validation against analytical solutions or experimental data, where applicable. State the main assumptions and the sensitivity of the results to key parameters. Visuals presented as results must be generated from the simulation data, and all post-processing and rendering steps must be described.
2. Machine-learning and predictive modeling
Original research in which a trained model predicts physical, chemical or biological behavior (for example protein structure, material properties or climate patterns).
Requirements: Describe the datasets and their provenance, the training procedure, how training and test data were separated, the validation metrics, and the comparison with baseline methods. Visuals showing the model’s predictions must be labeled “Model-Predicted Output” and kept distinct from illustrative material.
3. Reviews of models and methods
Educational or review papers that explain existing models or theoretical frameworks.
Requirements: Cite all original sources. Conceptual animations (for example made with Manim or Blender) and visual metaphors are welcome but must be labeled “Conceptual Animation” or “Illustrative Metaphor”.
Prohibited practices
-
Pseudo-simulations: presenting AI-generated or hand-made animations as the output of a scientific solver or trained model.
-
AI-altered output: applying AI upscaling, frame interpolation or generative enhancement to footage labeled as Simulation Output or Model-Predicted Output, since these create frames the model did not compute.
-
Unlabeled or misleading visuals: animations that are not labeled as conceptual, or that suggest behavior not supported by the data or cited theory.
-
Selective presentation: showing only favorable runs, parameter ranges or time windows without disclosing that others were performed.
-
Unattributed work: using code, datasets or visual outputs created by others without citation or permission under their license.
Submission requirements
-
Computational setup: software and versions, governing equations, initial and boundary conditions, numerical method and discretization, solver settings and convergence criteria.
-
Assumptions and limitations: the main simplifications in the model and the range of conditions in which the results are expected to hold.
-
Visual labeling: every segment of the video must carry an on-screen label identifying it as Simulation Output, Model-Predicted Output, Conceptual Animation or Illustrative Metaphor, as applicable. Segments labeled as output must reflect the data accurately, with color scales and units shown.
-
Code and data availability: a statement explaining where the code, input files and data can be obtained, or why they cannot be shared. Deposit in an archived repository with a DOI is strongly encouraged.
-
AI Use Statement: as specified in SciViD’s Integrity Guide, covering any AI-generated or AI-enhanced narration, visuals or animation, included in the submission metadata and the video credits.
-
Narrative walkthrough: the video should explain the purpose of the model, the choice of parameters, and the significance and limitations of the results.
Interactive virtual labs
An interactive lab lets readers change parameters and watch a model respond. A polished interface can look more authoritative than the model behind it, so labs posted with SciViD items must meet the following requirements.
-
Status label: the first screen of the lab carries one of two labels: “Quantitative model: checked against [benchmark]” or “Illustrative model: not validated”. An Illustrative lab may support explanation but not claims about results.
-
Model statement: the governing equations, assumptions, and parameter values with SI units and their sources are given in the manuscript and can be reached from the lab.
-
Benchmark check: a Quantitative lab must reproduce at least one benchmark, such as a limiting case, an analytical solution or a published experimental result, and the manuscript must report the comparison.
-
Range of validity: parameter controls are limited to the range in which the model is expected to hold, or values outside that range are flagged on screen.
-
Authors’ understanding: the authors must be able to explain the model’s equations, assumptions and limitations in their own words, in the video abstract or when asked by the editors. Labs built with AI coding tools are acceptable when that use is disclosed in the AI Use Statement and the authors have checked the model themselves. A lab the authors cannot explain is posted only as an Illustrative model, or is declined.
-
Student authors: for Emerging Scholars submissions, the teacher or mentor confirms in the contribution statement that they have reviewed the benchmark check.
-
Versions: the code of each posted version is preserved unchanged. Errors are corrected in a new version, as set out in section 5 of the Integrity Guide.
Example titles
Illustrative only; not published papers.
-
“Self-Propelled Janus Micromotors Near Walls: A Brownian Dynamics Study”
-
“Droplet Breakup in a Microfluidic T-Junction: Volume-of-Fluid Simulations Across Capillary Numbers”
-
“Accretion Disk Instabilities Around a Black Hole: A Magnetohydrodynamic Simulation”
-
“Predicting the Mechanical Properties of Nanoporous Materials with Machine-Learned Interatomic Potentials”
-
“Molecular Dynamics of Lipid Bilayers: A Visual Review of Methods and Force Fields”
Video lets readers see how a model behaves, not only what it predicts. Combined with transparent methods and shared code, it can make computational work easier to evaluate and to reproduce.
