How to cite us¶
If you use dolfin-adjoint in your research, the developers would be grateful if you would cite the relevant publications.
If you use dolfin-adjoint 2018.1 or newer, please cite:
Sebastian K. Mitusch, Simon W. Funke, and Jørgen S. Dokken (2019). dolfin-adjoint 2018.1: automated adjoints for FEniCS and Firedrake, Journal of Open Source Software, 4(38), 1292, doi:10.21105/joss.01292.
If you use dolfin-adjoint to compute shape sensitivities or perform shape optimization, please also cite:
Jørgen S. Dokken, Sebastian K. Mitusch and Simon W. Funke (2020). Automatic shape derivatives for transient PDEs in FEniCS and Firedrake, arXiv:2001.10058 [math.OC].
If you use an older version of dolfin-adjoint, please cite:
Patrick E. Farrell, David A. Ham, Simon W. Funke and Marie E. Rognes (2013). Automated derivation of the adjoint of high-level transient finite element programs, SIAM Journal on Scientific Computing 35.4, pp. C369-C393. doi:10.1137/120873558. arXiv:1204.5577 [cs.MS]. [PDF].
If you use the optimisation framework of dolfin-adjoint, please also cite the optimisation paper:
Simon W. Funke and Patrick E. Farrell (2013). A framework for automated PDE-constrained optimisation, submitted. arXiv:1302.3894 [cs.MS] [PDF].
If you use checkpointing, you should also cite the paper by the authors of the revolve library:
Andreas Griewank and Andrea Walther (2000). Algorithm 799: revolve: an implementation of checkpointing for the reverse or adjoint mode of computational differentiation, ACM Transactions on Mathematical Software, 26, pp. 19–45. [link].
If you use dolfin-adjoint to perform a generalised stability analysis, please also cite the generalised stability analysis paper:
Patrick E. Farrell, Colin J. Cotter and Simon W. Funke (2014). A framework for the automation of generalised stability theory, SIAM Journal on Scientific Computing 36.1, pp. C25–C48. doi:10.1137/120900745. arXiv:1211.6989 [cs.MS]. [PDF].