Repository navigation
Citation
Thank you for citing OMRFlow. Citation is what lets other people find the project, and it is the clearest signal that the work is worth continuing.
https://doi.org/10.5281/zenodo.22943575
Every OMRFlow release is archived on Zenodo, which assigns it a permanent identifier. The DOI above is the concept DOI: it identifies OMRFlow as a project rather than any single release, and always resolves to the most recent archived version. Cite it unless you have a specific reason not to — it stays correct as new versions appear, so a paper citing it will not go stale.
Each individual release also receives its own DOI, listed on the Zenodo record. Use that one when reproducibility depends on the exact version you ran, and state the version in your text.
If you use OMRFlow in research, teaching, academic work, software, or another project, please cite the software using the Zenodo DOI.
Choudhury, S. M. (2026). OMRFlow [Computer software]. Zenodo.
https://doi.org/10.5281/zenodo.22943575
@software{choudhury_omrflow,
author = {Choudhury, Sajid Muhaimin},
title = {OMRFlow},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.22943575},
url = {https://doi.org/10.5281/zenodo.22943575}
}The repository carries a
CITATION.cff
file, so GitHub's Cite this repository button — on the right-hand side of
the repository page — generates APA
and BibTeX entries for you, with the DOI already filled in.
OMRFlow is research and teaching software, not a published paper. There is no accompanying article to cite instead; the Zenodo archive is the citable artefact, which is why it carries a DOI of its own.
The metadata behind these entries — author, affiliation, title, licence,
version and release date — comes from CITATION.cff in the repository and
from the Zenodo record, and the two are kept in step by the release process.
- Release History — what each version changed
- Known Limitations — what has and has not been validated, which is worth reading before relying on results in published work
- Licence — MIT