Writing an Abstract
Published in its entirety on: https://nsryan.github.io/blogs/2024-01-06_conference_abs.html
This blog post is a written version of the talk I have given to the UIUC ANS chapter several times now. Hopefully you can gain pertinent advice for your abstracts. The Advanced Reactors and Fuel Cycles (ARFC) Group has a writing checklist that I highly recommend you consult (we worked hard on it).
A conference abstract is a concise summary of a research project or study that is submitted to a conference for consideration. In it, you provide a brief overview of the research problem, methodology, key findings, and conclusions. Your goal should be to highlight the significance and novelty of the research, allowing conference organizers and attendees to evaluate its relevance and potential contribution to the field. You’re wetting their appetite for your work, show them why they should care.
1. Understanding the Requirements
When preparing an abstract for a national conference, you have to familiarize yourself with the official requirements of that event. For example, the American Nuclear Society (ANS) Student Conference typically requires abstracts to be 1–4 pages long and in the ANS template. Ensure your abstract is submitted by the deadline mentioned in the conference’s call for papers. Knowing these before you go to submit will save you all kinds of headaches, trust me.
2. Considerations and Unofficial Requirements
In addition to the official requirements, there are some unofficial considerations for when you are crafting your abstract like which track you submit to. Your work may fit in multiple tracks, but a careful track selection could help your chances of winning a best paper or presentation award. Another aspect to consider is selecting co-authors versus acknowledging contributors. Co-authors should have directly supported your work, but there isn’t a strict rule for this distinction that I know of. If you make someone a co-author, they must have time to review and make any necessary changes or additions to the work before submission. If they are not aware of the abstract by the week of the deadline, you may be too late to include someone as a co-author.
3. Crafting Your Story
Before diving into the details, it’s crucial to identify your central theme or story. Ask yourself what you want to convey to the audience. My primary purpose for presenting at a conference is advertising what I have done work. You want someone to remember your work so you can continue the conversation later and get into the nitty gritty with them. Once you have your story in mind, create an outline that covers the essential elements (we’re not reinventing the wheel here):
- an introduction to the problem,
- background information on its significance,
- and the theoretical basis supporting your work.
If the work has already been completed, you should hint at some conclusions and results.
