Hi Justin, That's exactly the right paper to cite for Firedrake in general. If your work particularly depends on features which have their own publications, then you might also cite those. At this stage, anything using quadrilateral elements or extrusion should cite McRae et al. (2016) and anything which has a particular reliance on kernel performance should cite Luporini et al. (2015). If you say anything about UFL, you should cite Martin Alnæs' paper on the subject, and it's likely that most papers using Firedrake would also want to be citing PETSc and/or one of the packages PETSc provides an interface to (depending on what you are using). One of the things on the vapourware todo list is to provide a PETSc-style citation option to Firedrake to autogenerate the list of citations used in a particular run. Regards, David On Thu, 7 Jan 2016 at 06:17 Justin Chang <jychang48@gmail.com> wrote:
I have used the Firedrake project to produce results in a paper I am hoping to submit very soon, but how exactly do I cite you guys?
Would it be
Firedrake: automating the finite element method by composing abstractions" Rathgeber, F.; Ham, D. A; Mitchell, L.; Lange, M.; Luporini, F.; McRae, A. T.; Bercea, G.; Markall, G. R; and Kelly, P. H. *Submitted to ACM TOMS*, . 2015.
or something else?
Thanks, Justin
On 07/01/16 08:51, David Ham wrote:
Hi Justin,
That's exactly the right paper to cite for Firedrake in general. If your work particularly depends on features which have their own publications, then you might also cite those. At this stage, anything using quadrilateral elements or extrusion should cite McRae et al. (2016)
That's this one: @article{McRae2015, title = {Automated generation and symbolic manipulation of tensor product finite elements}, author = {McRae, Andrew TT and Bercea, Gheorge-Teodor and Mitchell, Lawrence and Ham, David A and Cotter, Colin J}, archivePrefix ="arXiv", journal = {Submitted to SIAM Journal on Scientific Computing}, eprint = {1411.2940}, year = {2015}, url = {http://arxiv.org/abs/1411.2940} }
and anything which has a particular reliance on kernel performance should cite Luporini et al. (2015).
@article{Luporini2015, author = {Luporini, Fabio and Varbanescu, Ana Lucia and Rathgeber, Florian and Bercea, Gheorghe-Teodor and Ramanujam, J. and Ham, David A. and Kelly, Paul H. J.}, title = {Cross-Loop Optimization of Arithmetic Intensity for Finite Element Local Assembly}, journal = {ACM Trans. Archit. Code Optim.}, issue_date = {January 2015}, volume = {11}, number = {4}, month = jan, year = {2015}, issn = {1544-3566}, pages = {57:1--57:25}, articleno = {57}, numpages = {25}, url = {http://doi.acm.org/10.1145/2687415}, doi = {10.1145/2687415}, acmid = {2687415}, publisher = {ACM}, address = {New York, NY, USA}, keywords = {Finite element integration, SIMD vectorization, compilers, local assembly, optimizations}, }
If you say anything about UFL, you should cite Martin Alnæs' paper on the subject, and it's likely that most papers using Firedrake would also want to be citing PETSc and/or one of the packages PETSc provides an interface to (depending on what you are using).
One of the things on the vapourware todo list is to provide a PETSc-style citation option to Firedrake to autogenerate the list of citations used in a particular run.
Running with -citations will do, at least, the PETSc part for now. Lawrence
participants (2)
-
David Ham
-
Lawrence Mitchell