
Venue Templates
- 878 installs
- 32k repo stars
- Updated July 29, 2026
- k-dense-ai/scientific-agent-skills
venue-templates is a documentation agent skill that generates Cell Press-style Summary, Highlights, and eTOC blurbs meeting exact journal formatting and length rules for developers preparing scientific manuscript submiss
About
venue-templates is a Documentation agent skill in k-dense-ai/scientific-agent-skills that generates Cell Press-specific manuscript elements including Summary abstracts capped at 150 words, Highlights bullet lists, and eTOC blurbs. The skill ships complete worked examples such as a senescence and aging paper showing FOXO4-p53 interactions, giving agents concrete length and tone references before drafting new copy. Developers reach for venue-templates when a Cell Press submission needs venue-accurate Summary, Highlights, and eTOC text instead of generic abstract prose. The skill encodes Cell Press formatting constraints so agents produce submission-ready sections without manually cross-checking author guidelines. Use it alongside broader scientific-writing skills when polishing final journal packages for Cell Press titles.
- Produces Cell Press Summary limited to 150 words
- Generates Highlights at ≤85 characters each
- Creates eTOC-ready short blurbs
- Follows exact journal-specific structural templates
- Delivers ready-to-submit scientific communication artifacts
Venue Templates by the numbers
- 878 all-time installs (skills.sh)
- +41 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #289 of 1,881 Documentation skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/k-dense-ai/scientific-agent-skills --skill venue-templatesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 878 |
|---|---|
| repo stars | ★ 32k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 29, 2026 |
| Repository | k-dense-ai/scientific-agent-skills ↗ |
How do you format Cell Press Summary and Highlights?
Generate Cell Press-style Summary, Highlights, and eTOC blurbs that meet exact journal formatting and length rules.
Who is it for?
Researchers and scientific developers preparing Cell Press journal submissions who need venue-specific Summary, Highlights, and eTOC sections with strict word limits.
Skip if: Non-Cell-Press venues such as IEEE, ACM, or Nature formats that require entirely different abstract and highlight structures.
When should I use this skill?
A developer needs Cell Press Summary, Highlights, or eTOC blurbs generated or revised to meet exact journal length and formatting rules.
What you get
Cell Press Summary text (150 words max), Highlights bullets, and an eTOC blurb ready for journal submission.
- Cell Press Summary
- Highlights list
- eTOC blurb
By the numbers
- Cell Press Summary abstracts are capped at 150 words maximum
- Generates 3 submission elements: Summary, Highlights, and eTOC blurb
Files
Venue Templates
Overview
Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues, academic conferences, research posters, and grant proposals. This skill provides ready-to-use templates and detailed specifications for successful academic submissions across disciplines.
Use this skill when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
When to Use This Skill
This skill should be used when:
- Preparing a manuscript for submission to a specific journal (Nature, Science, PLOS, IEEE, etc.)
- Writing a conference paper with specific formatting requirements (NeurIPS, ICML, CHI, etc.)
- Creating an academic research poster for conferences
- Drafting grant proposals for federal agencies (NSF, NIH, DOE, DARPA) or private foundations
- Checking formatting requirements and page limits for target venues
- Customizing templates with author information and project details
- Verifying document compliance with venue specifications
Visual Enhancement with Scientific Schematics
When creating documents with this skill, always consider adding scientific diagrams and schematics to enhance visual communication.
If your document does not already contain schematics or diagrams:
- Use the scientific-schematics skill to generate AI-powered publication-quality diagrams
- Simply describe your desired diagram in natural language
- Nano Banana Pro will automatically generate, review, and refine the schematic
For new documents: Scientific schematics should be generated by default to visually represent key concepts, workflows, architectures, or relationships described in the text.
How to generate schematics:
python scripts/generate_schematic.py "your diagram description" -o figures/output.pngThe AI will automatically:
- Create publication-quality images with proper formatting
- Review and refine through multiple iterations
- Ensure accessibility (colorblind-friendly, high contrast)
- Save outputs in the figures/ directory
When to add schematics:
- Methodology flowcharts for papers
- Conceptual framework diagrams
- System architecture illustrations
- Data flow diagrams
- Experimental design visualizations
- Research workflow diagrams
- Any complex concept that benefits from visualization
For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.
---
Core Capabilities
1. Journal Article Templates
Access LaTeX templates and formatting guidelines for 50+ major scientific journals across disciplines:
Nature Portfolio:
- Nature, Nature Methods, Nature Biotechnology, Nature Machine Intelligence
- Nature Communications, Nature Protocols
- Scientific Reports
Science Family:
- Science, Science Advances, Science Translational Medicine
- Science Immunology, Science Robotics
PLOS (Public Library of Science):
- PLOS ONE, PLOS Biology, PLOS Computational Biology
- PLOS Medicine, PLOS Genetics
Cell Press:
- Cell, Neuron, Immunity, Cell Reports
- Molecular Cell, Developmental Cell
IEEE Publications:
- IEEE Transactions (various disciplines)
- IEEE Access, IEEE Journal templates
ACM Publications:
- ACM Transactions, Communications of the ACM
- ACM conference proceedings
Other Major Publishers:
- Springer journals (various disciplines)
- Elsevier journals (custom templates)
- Wiley journals
- BMC journals
- Frontiers journals
2. Conference Paper Templates
Conference-specific templates with proper formatting for major academic conferences:
Machine Learning & AI:
- NeurIPS (Neural Information Processing Systems)
- ICML (International Conference on Machine Learning)
- ICLR (International Conference on Learning Representations)
- CVPR (Computer Vision and Pattern Recognition)
- AAAI (Association for the Advancement of Artificial Intelligence)
Computer Science:
- ACM CHI (Human-Computer Interaction)
- SIGKDD (Knowledge Discovery and Data Mining)
- EMNLP (Empirical Methods in Natural Language Processing)
- SIGIR (Information Retrieval)
- USENIX conferences
Biology & Bioinformatics:
- ISMB (Intelligent Systems for Molecular Biology)
- RECOMB (Research in Computational Molecular Biology)
- PSB (Pacific Symposium on Biocomputing)
Engineering:
- IEEE conference templates (various disciplines)
- ASME, AIAA conferences
3. Research Poster Templates
Academic poster templates for conference presentations:
Standard Formats:
- A0 (841 × 1189 mm / 33.1 × 46.8 in)
- A1 (594 × 841 mm / 23.4 × 33.1 in)
- 36" × 48" (914 × 1219 mm) - Common US size
- 42" × 56" (1067 × 1422 mm)
- 48" × 36" (landscape orientation)
Template Packages:
- beamerposter: Classic academic poster template
- tikzposter: Modern, colorful poster design
- baposter: Structured multi-column layout
Design Features:
- Optimal font sizes for readability at distance
- Color schemes (colorblind-safe palettes)
- Grid layouts and column structures
- QR code integration for supplementary materials
4. Grant Proposal Templates
Templates and formatting requirements for major funding agencies:
NSF (National Science Foundation):
- Full proposal template (15-page project description)
- Project Summary (1 page: Overview, Intellectual Merit, Broader Impacts)
- Budget and budget justification
- Biographical sketch (3-page limit)
- Facilities, Equipment, and Other Resources
- Data Management Plan
NIH (National Institutes of Health):
- R01 Research Grant (multi-year)
- R21 Exploratory/Developmental Grant
- K Awards (Career Development)
- Specific Aims Page (1 page, most critical component)
- Research Strategy (Significance, Innovation, Approach)
- Biographical sketches (5-page limit)
DOE (Department of Energy):
- Office of Science proposals
- ARPA-E templates
- Technology Readiness Level (TRL) descriptions
- Commercialization and impact sections
DARPA (Defense Advanced Research Projects Agency):
- BAA (Broad Agency Announcement) responses
- Heilmeier Catechism framework
- Technical approach and milestones
- Transition planning
Private Foundations:
- Gates Foundation
- Wellcome Trust
- Howard Hughes Medical Institute (HHMI)
- Chan Zuckerberg Initiative (CZI)
Workflow: Finding and Using Templates
Step 1: Identify Target Venue
Determine the specific publication venue, conference, or funding agency:
Example queries:
- "I need to submit to Nature"
- "What are the requirements for NeurIPS 2025?"
- "Show me NSF proposal formatting"
- "I'm creating a poster for ISMB"Step 2: Query Template and Requirements
Access venue-specific templates and formatting guidelines:
For Journals:
# Load journal formatting requirements
Reference: references/journals_formatting.md
Search for: "Nature" or specific journal name
# Retrieve template
Template: assets/journals/nature_article.texFor Conferences:
# Load conference formatting
Reference: references/conferences_formatting.md
Search for: "NeurIPS" or specific conference
# Retrieve template
Template: assets/journals/neurips_article.texFor Posters:
# Load poster guidelines
Reference: references/posters_guidelines.md
# Retrieve template
Template: assets/posters/beamerposter_academic.texFor Grants:
# Load grant requirements
Reference: references/grants_requirements.md
Search for: "NSF" or specific agency
# Retrieve template
Template: assets/grants/nsf_proposal_template.texStep 3: Review Formatting Requirements
Check critical specifications before customizing:
Key Requirements to Verify:
- Page limits (varies by venue)
- Font size and family
- Margin specifications
- Line spacing
- Citation style (APA, Vancouver, Nature, etc.)
- Figure/table requirements
- File format (PDF, Word, LaTeX source)
- Anonymization (for double-blind review)
- Supplementary material limits
Step 4: Customize Template
Use helper scripts or manual customization:
Option 1: Helper Script (Recommended):
python scripts/customize_template.py \
--template assets/journals/nature_article.tex \
--title "Your Paper Title" \
--authors "First Author, Second Author" \
--affiliations "University Name" \
--output my_nature_paper.texOption 2: Manual Editing:
- Open template file
- Replace placeholder text (marked with comments)
- Fill in title, authors, affiliations, abstract
- Add your content to each section
Step 5: Validate Format
Check compliance with venue requirements:
python scripts/validate_format.py \
--file my_paper.pdf \
--venue "Nature" \
--check-allValidation Checks:
- Page count within limits
- Font sizes correct
- Margins meet specifications
- References formatted correctly
- Figures meet resolution requirements
Step 6: Compile and Review
Compile LaTeX and review output:
# Compile LaTeX
pdflatex my_paper.tex
bibtex my_paper
pdflatex my_paper.tex
pdflatex my_paper.tex
# Or use latexmk for automated compilation
latexmk -pdf my_paper.texReview checklist:
- [ ] All sections present and properly formatted
- [ ] Citations render correctly
- [ ] Figures appear with proper captions
- [ ] Page count within limits
- [ ] Author guidelines followed
- [ ] Supplementary materials prepared (if needed)
Integration with Other Skills
This skill works seamlessly with other scientific skills:
Scientific Writing
- Use scientific-writing skill for content guidance (IMRaD structure, clarity, precision)
- Apply venue-specific templates from this skill for formatting
- Combine for complete manuscript preparation
Literature Review
- Use literature-review skill for systematic literature search and synthesis
- Apply appropriate citation style from venue requirements
- Format references according to template specifications
Peer Review
- Use peer-review skill to evaluate manuscript quality
- Use this skill to verify formatting compliance
- Ensure adherence to reporting guidelines (CONSORT, STROBE, etc.)
Research Grants
- Cross-reference with research-grants skill for content strategy
- Use this skill for agency-specific templates and formatting
- Combine for comprehensive grant proposal preparation
LaTeX Posters
- This skill provides venue-agnostic poster templates
- Use for conference-specific poster requirements
- Integrate with visualization skills for figure creation
Template Categories
By Document Type
| Category | Template Count | Common Venues |
|---|---|---|
| Journal Articles | 30+ | Nature, Science, PLOS, IEEE, ACM, Cell Press |
| Conference Papers | 20+ | NeurIPS, ICML, CVPR, CHI, ISMB |
| Research Posters | 10+ | A0, A1, 36×48, various packages |
| Grant Proposals | 15+ | NSF, NIH, DOE, DARPA, foundations |
By Discipline
| Discipline | Supported Venues |
|---|---|
| Life Sciences | Nature, Cell Press, PLOS, ISMB, RECOMB |
| Physical Sciences | Science, Physical Review, ACS, APS |
| Engineering | IEEE, ASME, AIAA, ACM |
| Computer Science | ACM, IEEE, NeurIPS, ICML, ICLR |
| Medicine | NEJM, Lancet, JAMA, BMJ |
| Interdisciplinary | PNAS, Nature Communications, Science Advances |
Helper Scripts
query_template.py
Search and retrieve templates by venue name, type, or keywords:
# Find templates for a specific journal
python scripts/query_template.py --venue "Nature" --type "article"
# Search by keyword
python scripts/query_template.py --keyword "machine learning"
# List all available templates
python scripts/query_template.py --list-all
# Get requirements for a venue
python scripts/query_template.py --venue "NeurIPS" --requirementscustomize_template.py
Customize templates with author and project information:
# Basic customization
python scripts/customize_template.py \
--template assets/journals/nature_article.tex \
--output my_paper.tex
# With author information
python scripts/customize_template.py \
--template assets/journals/nature_article.tex \
--title "Novel Approach to Protein Folding" \
--authors "Jane Doe, John Smith, Alice Johnson" \
--affiliations "MIT, Stanford, Harvard" \
--email "[email protected]" \
--output my_paper.tex
# Interactive mode
python scripts/customize_template.py --interactivevalidate_format.py
Check document compliance with venue requirements:
# Validate a compiled PDF
python scripts/validate_format.py \
--file my_paper.pdf \
--venue "Nature" \
--check-all
# Check specific aspects
python scripts/validate_format.py \
--file my_paper.pdf \
--venue "NeurIPS" \
--check page-count,margins,fonts
# Generate validation report
python scripts/validate_format.py \
--file my_paper.pdf \
--venue "Science" \
--report validation_report.txtBest Practices
Template Selection
1. Verify currency: Check template date and compare with latest author guidelines 2. Check official sources: Many journals provide official LaTeX classes 3. Test compilation: Compile template before adding content 4. Read comments: Templates include helpful inline comments
Customization
1. Preserve structure: Don't remove required sections or packages 2. Follow placeholders: Replace marked placeholder text systematically 3. Maintain formatting: Don't override venue-specific formatting 4. Keep backups: Save original template before customization
Compliance
1. Check page limits: Verify before final submission 2. Validate citations: Use correct citation style for venue 3. Test figures: Ensure figures meet resolution requirements 4. Review anonymization: Remove identifying information if required
Submission
1. Follow instructions: Read complete author guidelines 2. Include all files: LaTeX source, figures, bibliography 3. Generate properly: Use recommended compilation method 4. Check output: Verify PDF matches expectations
Common Formatting Requirements
Page Limits (Typical)
| Venue Type | Typical Limit | Notes |
|---|---|---|
| Nature Article | 5 pages | ~3000 words excluding refs |
| Science Report | 5 pages | Figures count toward limit |
| PLOS ONE | No limit | Unlimited length |
| NeurIPS | 8 pages | + unlimited refs/appendix |
| ICML | 8 pages | + unlimited refs/appendix |
| NSF Proposal | 15 pages | Project description only |
| NIH R01 | 12 pages | Research strategy |
Citation Styles by Venue
| Venue | Citation Style | Format |
|---|---|---|
| Nature | Numbered (superscript) | Nature style |
| Science | Numbered (superscript) | Science style |
| PLOS | Numbered (brackets) | Vancouver |
| Cell Press | Author-year | Cell style |
| ACM | Numbered | ACM style |
| IEEE | Numbered (brackets) | IEEE style |
| APA journals | Author-year | APA 7th |
Figure Requirements
| Venue | Resolution | Format | Color |
|---|---|---|---|
| Nature | 300+ dpi | TIFF, EPS, PDF | RGB or CMYK |
| Science | 300+ dpi | TIFF, PDF | RGB |
| PLOS | 300-600 dpi | TIFF, EPS | RGB |
| IEEE | 300+ dpi | EPS, PDF | RGB or Grayscale |
Writing Style Guides
Beyond formatting, this skill provides comprehensive writing style guides that capture how papers should read at different venues—not just how they should look.
Why Style Matters
The same research written for Nature will read very differently than when written for NeurIPS:
- Nature/Science: Accessible to non-specialists, story-driven, broad significance
- Cell Press: Mechanistic depth, comprehensive data, graphical abstract required
- Medical journals: Patient-centered, evidence-graded, structured abstracts
- ML conferences: Contribution bullets, ablation studies, reproducibility focus
- CS conferences: Field-specific conventions, varying evaluation standards
Available Style Guides
| Guide | Covers | Key Topics |
|---|---|---|
venue_writing_styles.md | Master overview | Style spectrum, quick reference |
nature_science_style.md | Nature, Science, PNAS | Accessibility, story-telling, broad impact |
cell_press_style.md | Cell, Neuron, Immunity | Graphical abstracts, eTOC, Highlights |
medical_journal_styles.md | NEJM, Lancet, JAMA, BMJ | Structured abstracts, evidence language |
ml_conference_style.md | NeurIPS, ICML, ICLR, CVPR | Contribution bullets, ablations |
cs_conference_style.md | ACL, EMNLP, CHI, SIGKDD | Field-specific conventions |
reviewer_expectations.md | All venues | What reviewers look for, rebuttal tips |
Writing Examples
Concrete examples are available in assets/examples/:
nature_abstract_examples.md: Flowing paragraph abstracts for high-impact journalsneurips_introduction_example.md: ML conference intro with contribution bulletscell_summary_example.md: Cell Press Summary, Highlights, eTOC formatmedical_structured_abstract.md: NEJM, Lancet, JAMA structured format
Workflow: Adapting to a Venue
1. Identify target venue and load the appropriate style guide 2. Review writing conventions: Tone, voice, abstract format, structure 3. Check examples for section-specific guidance 4. Review expectations: What do reviewers at this venue prioritize? 5. Apply formatting: Use LaTeX template from assets/
---
Resources
Bundled Resources
Writing Style Guides (in references/):
venue_writing_styles.md: Master style overview and comparisonnature_science_style.md: Nature/Science writing conventionscell_press_style.md: Cell Press journal stylemedical_journal_styles.md: Medical journal writing guideml_conference_style.md: ML conference writing conventionscs_conference_style.md: CS conference writing guidereviewer_expectations.md: What reviewers look for by venue
Formatting Requirements (in references/):
journals_formatting.md: Comprehensive journal formatting requirementsconferences_formatting.md: Conference paper specificationsposters_guidelines.md: Research poster design and sizinggrants_requirements.md: Grant proposal requirements by agency
Writing Examples (in assets/examples/):
nature_abstract_examples.md: High-impact journal abstract examplesneurips_introduction_example.md: ML conference introduction formatcell_summary_example.md: Cell Press Summary/Highlights/eTOCmedical_structured_abstract.md: NEJM/Lancet/JAMA abstract format
Templates (in assets/):
journals/: Journal article LaTeX templatesposters/: Research poster templatesgrants/: Grant proposal templates
Scripts (in scripts/):
query_template.py: Search and retrieve templatescustomize_template.py: Customize with author infovalidate_format.py: Check compliance with requirements
External Resources
Journal Author Guidelines:
- Nature: https://www.nature.com/nature/for-authors
- Science: https://www.science.org/content/page/instructions-authors
- PLOS: https://plos.org/resources/for-authors/
- Cell Press: https://www.cell.com/author-guidelines
Conference Formatting:
- NeurIPS: https://neurips.cc/Conferences/2024/CallForPapers
- ICML: https://icml.cc/Conferences/2024/StyleAuthorInstructions
- CVPR: https://cvpr.thecvf.com/Conferences/2024/AuthorGuidelines
Grant Resources:
- NSF PAPPG: https://www.nsf.gov/publications/pub_summ.jsp?ods_key=pappg
- NIH Forms: https://grants.nih.gov/grants/how-to-apply-application-guide.html
- DOE Funding: https://science.osti.gov/grants
Example Usage
Example 1: Nature Article Submission
User: "I need to prepare a manuscript for Nature"
Response:
1. Load Nature formatting requirements (references/journals_formatting.md)
2. Retrieve Nature template (assets/journals/nature_article.tex)
3. Key requirements:
- Length: ~3000 words, ~5 pages
- Format: Single column, 12pt font
- Citations: Numbered superscript (Nature style)
- Figures: 300+ dpi, RGB color
4. Customize template with your title, authors, affiliations
5. Compile and validate against requirementsExample 2: NeurIPS Conference Paper
User: "What are the formatting requirements for NeurIPS?"
Response:
From references/conferences_formatting.md:
- Page limit: 8 pages main text + unlimited references/appendix
- Format: Two-column, 10pt font
- Template: neurips_2024.sty (official style file)
- Anonymization: Required for initial submission
- Citations: Numbered (brackets)
- Figures: High resolution, colorblind-safe recommendedExample 3: NSF Proposal
User: "Help me format an NSF proposal"
Response:
NSF requirements (from references/grants_requirements.md):
- Project Description: 15 pages maximum
- Project Summary: 1 page (Overview, Intellectual Merit, Broader Impacts)
- Budget Justification: 3-5 pages
- Biographical Sketch: 3 pages per senior personnel
- Font: Minimum 10pt, Times Roman or similar
- Margins: 1 inch all sides
Template: assets/grants/nsf_proposal_template.texExample 4: Conference Poster
User: "I need to create a poster for ISMB"
Response:
ISMB poster specifications:
- Size: Typically A0 portrait (33.1 × 46.8 inches)
- Recommended template: beamerposter or tikzposter
- Font sizes: Title 60-85pt, Headers 36-48pt, Body 24-32pt
- Include: QR code for paper/supplementary materials
Available templates:
- assets/posters/beamerposter_academic.texUpdates and Maintenance
Template Currency:
- Templates updated annually or when venues release new guidelines
- Last updated: 2024
- Check official venue sites for most current requirements
Reporting Issues:
- Template compilation errors
- Outdated formatting requirements
- Missing venue templates
- Incorrect specifications
Summary
The venue-templates skill provides comprehensive access to:
1. 50+ publication venue templates across disciplines 2. Detailed formatting requirements for journals, conferences, posters, grants 3. Helper scripts for template discovery, customization, and validation 4. Integration with other scientific writing skills 5. Best practices for successful academic submissions
Use this skill whenever you need venue-specific formatting guidance or templates for academic publishing.
Cell Press Summary, Highlights, and eTOC Examples
Examples of Cell Press-specific elements including Summary (abstract), Highlights, and eTOC blurb.
---
Complete Example 1: Senescence and Aging
Summary (150 words max)
Cellular senescence is a stress response that prevents damaged cell
proliferation but can drive tissue dysfunction through the senescence-
associated secretory phenotype (SASP). How senescent cells resist
apoptosis despite expressing pro-apoptotic p53 has remained unclear.
Here, we identify FOXO4 as a pivotal mediator of senescent cell viability.
FOXO4 is highly expressed in senescent cells and directly interacts with
p53, retaining it in the nucleus and preventing p53-mediated apoptosis.
A cell-permeable peptide that disrupts FOXO4-p53 interaction selectively
induces p53 nuclear exclusion and apoptosis in senescent cells without
affecting proliferating cells. In vivo, this FOXO4 peptide neutralizes
doxorubicin-induced senescent cells and restores fitness, fur density,
and renal function in naturally aged mice. These findings establish
FOXO4-mediated p53 sequestration as a senescence-specific survival
pathway and demonstrate the therapeutic potential of targeted senescent
cell elimination.Highlights (≤85 characters each)
• FOXO4 is selectively upregulated in senescent cells and binds p53
• FOXO4-p53 interaction retains p53 in the nucleus, preventing apoptosis
• A FOXO4-targeting peptide induces apoptosis specifically in senescent cells
• FOXO4 peptide treatment restores fitness and organ function in aged miceeTOC Blurb (30-50 words)
Baar et al. identify FOXO4 as a critical mediator of senescent cell survival
through p53 sequestration. A peptide disrupting FOXO4-p53 interaction
selectively eliminates senescent cells and restores tissue function in
aged mice, establishing proof-of-concept for targeted senolytic therapy.In Brief (1 sentence)
A FOXO4-targeting peptide selectively eliminates senescent cells by
releasing p53, restoring tissue function in aged mice.---
Complete Example 2: Genome Organization
Summary (150 words max)
The three-dimensional organization of chromosomes within the nucleus
influences gene expression, DNA replication, and genome stability.
Phase separation has emerged as a potential mechanism for organizing
nuclear contents, but whether condensates can shape chromosome
structure in vivo remains unknown. Here, we show that the transcriptional
coactivator BRD4 forms liquid-like condensates at super-enhancers that
organize associated chromatin into hub structures. Optogenetic induction
of BRD4 condensates is sufficient to remodel chromosome topology and
activate transcription within minutes. Conversely, disruption of BRD4
condensates with the small molecule JQ1 dissolves chromatin hubs and
rapidly silences super-enhancer-controlled genes. Single-molecule
tracking reveals that condensate formation increases the local
concentration of transcription machinery 100-fold, explaining the
transcriptional potency of super-enhancers. These results establish
phase separation as a mechanism for chromatin organization and
transcriptional control with implications for understanding and
targeting oncogenic super-enhancers.Highlights
• BRD4 forms liquid condensates at super-enhancers in living cells
• BRD4 condensates organize chromatin into transcriptionally active hubs
• Optogenetic condensate induction rapidly remodels chromatin topology
• Condensates concentrate transcription machinery 100-fold locallyeTOC Blurb
Sabari et al. demonstrate that BRD4 forms phase-separated condensates
at super-enhancers that organize chromatin into hub structures and
concentrate transcription machinery. Optogenetic manipulation reveals
that condensate formation directly drives chromatin remodeling and
transcriptional activation.---
Complete Example 3: Metabolism and Immunity
Summary (150 words max)
Immune cells undergo dramatic metabolic reprogramming upon activation,
switching from oxidative phosphorylation to aerobic glycolysis. This
metabolic shift is thought to support the biosynthetic demands of
rapid proliferation, but whether specific metabolites directly regulate
immune cell function remains largely unexplored. Here, we show that
the glycolytic metabolite phosphoenolpyruvate (PEP) sustains T cell
receptor signaling by inhibiting sarco/endoplasmic reticulum Ca²⁺-ATPase
(SERCA) activity. PEP accumulates in activated T cells and directly
binds SERCA, preventing calcium reuptake and prolonging store-operated
calcium entry. Genetic or pharmacological enhancement of PEP levels
augments T cell effector function and anti-tumor immunity in vivo.
Conversely, tumor-derived lactate suppresses PEP levels and impairs
T cell calcium signaling, contributing to tumor immune evasion. These
findings reveal an unexpected signaling role for a glycolytic
intermediate and suggest metabolic strategies to enhance T cell
responses in cancer immunotherapy.Highlights
• Phosphoenolpyruvate (PEP) accumulates during T cell activation
• PEP directly binds and inhibits SERCA to sustain calcium signaling
• Enhancing PEP levels augments anti-tumor T cell immunity
• Tumor lactate suppresses T cell PEP levels and calcium signalingeTOC Blurb
Ho et al. discover that the glycolytic metabolite phosphoenolpyruvate
directly regulates T cell calcium signaling by inhibiting SERCA. This
metabolic-signaling link is exploited by tumors through lactate
secretion and offers new targets for cancer immunotherapy.---
Graphical Abstract Description Examples
For Senescence Paper
"Graphical abstract for Cell paper on FOXO4 and senescence:
Left panel: Senescent cell (enlarged, irregular shape) with FOXO4 (blue
oval) binding p53 (green oval) in nucleus, preventing apoptosis. Label:
'FOXO4 sequesters p53 → Senescent cell survival'
Center panel: Same senescent cell with FOXO4 peptide (red wedge)
disrupting FOXO4-p53 interaction. p53 moves to mitochondria (orange
organelles). Label: 'FOXO4 peptide disrupts interaction'
Right panel: Senescent cell undergoing apoptosis (fragmenting). Label:
'Selective senescent cell death'
Bottom: Aged mouse (grey, hunched) → Treatment arrow → Rejuvenated mouse
(brown, active). Label: 'Restored fitness in aged mice'
Color scheme: Blue for FOXO4, green for p53, red for peptide, grey
background for cells."For Chromatin Paper
"Graphical abstract for Cell paper on BRD4 condensates:
Top row: Diagram showing BRD4 molecules (purple dots) clustering at
super-enhancer (yellow region on DNA strand), forming condensate
(purple droplet). Transcription factors (orange, green, blue small
circles) accumulate inside condensate.
Middle: Chromatin fibers (grey) being pulled into hub structure around
condensate. Arrow showing '100× local concentration increase'
Bottom: Two panels - Left shows 'JQ1' treatment dissolving condensate
and chromatin hub dispersing. Right shows 'Optogenetic activation'
creating new condensate with chromatin reorganization. Gene expression
indicators (up arrow, down arrow) for each condition."---
Writing Tips for Cell Elements
Summary Tips
1. First sentence: Establish the biological context 2. Second sentence: State what was unknown (the gap) 3. "Here, we show/identify/demonstrate": Clear transition to your work 4. Middle sentences: Key findings with mechanism 5. Final sentence: Significance and implications
Highlights Tips
- Start with a noun or verb: "FOXO4 forms..." or "Activation of..."
- One finding per bullet: Don't combine multiple points
- Be specific: Include the protein/gene/pathway name
- Check character count: Strictly ≤85 characters including spaces
- Cover different findings: Don't repeat the same point
eTOC Blurb Tips
- Start with author names: "Smith et al. show that..."
- One or two sentences only: Keep it punchy
- Include the key mechanism: Not just the finding
- End with significance: Why readers should care
---
Character Counting for Highlights
Use this to check your highlights:
• This highlight is exactly 52 characters long including sp
↑ Count: 52 characters ✓ (under 85)
• This highlight is getting close to the maximum allowed character limit
↑ Count: 73 characters ✓ (under 85)
• This highlight demonstrates what happens when you try to include way too much info
↑ Count: 88 characters ✗ (over 85 - need to shorten)---
See Also
cell_press_style.md- Comprehensive Cell Press writing guidenature_abstract_examples.md- Compare with Nature abstract style
Medical Journal Structured Abstract Examples
Examples of structured abstracts for NEJM, Lancet, JAMA, and BMJ showing the labeled section format expected at medical journals.
---
NEJM Style (250 words max)
Example 1: Clinical Trial
BACKGROUND
Sodium-glucose cotransporter 2 (SGLT2) inhibitors reduce cardiovascular
events in patients with type 2 diabetes and established cardiovascular
disease. Whether these benefits extend to patients with heart failure and
reduced ejection fraction, regardless of diabetes status, is unknown.
METHODS
We randomly assigned 4,744 patients with heart failure and an ejection
fraction of 40% or less to receive dapagliflozin (10 mg once daily) or
placebo, in addition to recommended therapy. The primary outcome was a
composite of worsening heart failure (hospitalization or urgent visit
requiring intravenous therapy) or cardiovascular death.
RESULTS
Over a median of 18.2 months, the primary outcome occurred in 386 of
2,373 patients (16.3%) in the dapagliflozin group and in 502 of 2,371
patients (21.2%) in the placebo group (hazard ratio, 0.74; 95% confidence
interval [CI], 0.65 to 0.85; P<0.001). A first worsening heart failure
event occurred in 237 patients (10.0%) in the dapagliflozin group and
in 326 patients (13.7%) in the placebo group (hazard ratio, 0.70; 95%
CI, 0.59 to 0.83). Death from cardiovascular causes occurred in 227
patients (9.6%) and 273 patients (11.5%), respectively (hazard ratio,
0.82; 95% CI, 0.69 to 0.98). Effects were similar in patients with and
without diabetes. Serious adverse events were similar between groups.
CONCLUSIONS
Among patients with heart failure and a reduced ejection fraction,
dapagliflozin reduced the risk of worsening heart failure or
cardiovascular death, regardless of the presence of diabetes.Key Features:
- Four labeled sections (BACKGROUND, METHODS, RESULTS, CONCLUSIONS)
- Background: 2 sentences (problem + gap)
- Methods: Study design, population, intervention, primary outcome
- Results: Primary outcome with HR and 95% CI, key secondary outcomes
- Conclusions: Clear, measured statement of findings
---
Example 2: Observational Study
BACKGROUND
Long-term use of proton-pump inhibitors (PPIs) has been associated with
adverse outcomes in observational studies, but causality remains uncertain.
The relationship between PPI use and chronic kidney disease is unclear.
METHODS
We conducted a prospective cohort study using data from 10,482 participants
in the Atherosclerosis Risk in Communities study who were free of kidney
disease at baseline. PPI use was ascertained at baseline and follow-up
visits. The primary outcome was incident chronic kidney disease, defined
as an estimated glomerular filtration rate less than 60 ml per minute per
1.73 m² of body-surface area.
RESULTS
Over a median follow-up of 13.9 years, incident chronic kidney disease
occurred in 56.0 per 1000 person-years among PPI users and in 42.0 per
1000 person-years among non-users (adjusted hazard ratio, 1.50; 95%
confidence interval [CI], 1.14 to 1.96). The association persisted after
adjustment for potential confounders, including indication for PPI use
and baseline kidney function. Sensitivity analyses using propensity-score
matching yielded similar results. No association was observed for
histamine H2-receptor antagonist use (hazard ratio, 1.08; 95% CI, 0.87
to 1.34).
CONCLUSIONS
PPI use was associated with an increased risk of incident chronic kidney
disease in this community-based cohort. These findings warrant cautious
use of PPIs and further investigation to establish causality.Key Features:
- Appropriate hedging for observational study ("associated with")
- Incidence rates provided (per 1000 person-years)
- Sensitivity analyses mentioned
- Negative control (H2-receptor antagonists)
- Cautious conclusion acknowledging limitation
---
Lancet Style (300 words max)
Example 3: Clinical Trial with Summary Box
BACKGROUND
Dexamethasone has been shown to reduce mortality in hospitalized patients
with COVID-19 requiring respiratory support. We aimed to evaluate whether
higher doses of corticosteroids would provide additional benefit in
patients with severe COVID-19 pneumonia.
METHODS
In this randomized, controlled, open-label trial conducted at 18 hospitals
in Brazil, we assigned patients with moderate-to-severe COVID-19 (PaO2/FiO2
≤200 mm Hg) to receive high-dose dexamethasone (20 mg once daily for 5
days, then 10 mg once daily for 5 days) or standard dexamethasone (6 mg
once daily for 10 days). The primary outcome was ventilator-free days
at 28 days.
FINDINGS
Between June 17, 2020, and September 20, 2021, we enrolled 299 patients
(151 assigned to high-dose dexamethasone and 148 to standard
dexamethasone). The mean number of ventilator-free days at 28 days was
14·2 (SD 10·8) in the high-dose group and 15·5 (SD 10·4) in the standard
group (difference, −1·3 days; 95% CI, −3·9 to 1·3; P=0·32). There was
no significant difference in 28-day mortality (high dose 35·8% vs
standard 31·8%; hazard ratio 1·16; 95% CI, 0·79 to 1·70). Hyperglycemia
requiring insulin was more frequent with high-dose dexamethasone (66·0%
vs 53·4%; P=0·027).
INTERPRETATION
In patients with moderate-to-severe COVID-19 pneumonia, high-dose
dexamethasone did not improve ventilator-free days and was associated
with increased hyperglycemia compared with standard-dose dexamethasone.
These findings do not support the use of high-dose corticosteroids in
COVID-19.
FUNDING
Ministry of Health of Brazil.Key Features:
- Lancet uses "Findings" instead of "Results"
- Lancet uses "Interpretation" instead of "Conclusions"
- Includes funding statement in abstract
- Decimal point (·) instead of period in numbers (Lancet style)
---
JAMA Style (350 words max)
Example 4: Diagnostic Study
IMPORTANCE
Lung cancer screening with low-dose computed tomography (CT) reduces
mortality but identifies many indeterminate pulmonary nodules, leading
to unnecessary invasive procedures. Improved risk prediction could
reduce harms while preserving benefits.
OBJECTIVE
To develop and validate a deep learning model for predicting malignancy
risk of lung nodules detected on screening CT.
DESIGN, SETTING, AND PARTICIPANTS
This retrospective cohort study included 14,851 participants with
lung nodules from the National Lung Screening Trial (NLST) for model
development and 5,402 participants from an independent multi-site
validation cohort (2016-2019). Data analysis was performed from
January to November 2022.
EXPOSURES
Deep learning model prediction of malignancy risk based on CT imaging.
MAIN OUTCOMES AND MEASURES
The primary outcome was lung cancer diagnosis within 2 years. Model
performance was assessed by area under the receiver operating
characteristic curve (AUC), sensitivity, specificity, and comparison
with radiologist assessments.
RESULTS
In the validation cohort (median age, 65 years; 57% male), 312 nodules
(5.8%) were diagnosed as lung cancer within 2 years. The deep learning
model achieved an AUC of 0.94 (95% CI, 0.92-0.96), compared with 0.85
(95% CI, 0.82-0.88) for the Lung-RADS categorization used by radiologists
(P<0.001). At 95% sensitivity, the model achieved 68% specificity compared
with 38% for Lung-RADS, corresponding to a 49% reduction in false-positive
nodules requiring follow-up. The model's performance was consistent across
subgroups defined by nodule size, location, and patient demographics.
CONCLUSIONS AND RELEVANCE
A deep learning model for lung nodule malignancy prediction outperformed
current clinical standards and could substantially reduce false-positive
findings in lung cancer screening, decreasing unnecessary surveillance
and invasive procedures.Key Features:
- JAMA-specific sections (IMPORTANCE, OBJECTIVE, DESIGN...)
- "Importance" section required (2-3 sentences on why this matters)
- Detailed design section
- "Exposures" clearly stated
- "Main Outcomes and Measures" explicit
---
BMJ Style (300 words max)
Example 5: Cohort Study
OBJECTIVE
To examine the association between statin use and risk of Parkinson's
disease in a large population-based cohort.
DESIGN
Prospective cohort study.
SETTING
UK Biobank, 2006-2021.
PARTICIPANTS
402,251 adults aged 40-69 years without Parkinson's disease at baseline.
MAIN OUTCOME MEASURES
Incident Parkinson's disease identified through hospital admissions,
primary care records, and death certificates. Hazard ratios were
estimated using Cox regression, adjusted for age, sex, education,
smoking, alcohol, physical activity, body mass index, and comorbidities.
RESULTS
Over a median follow-up of 12.3 years, 2,841 participants developed
Parkinson's disease (incidence rate 5.7 per 10,000 person-years).
Statin use at baseline was not associated with incident Parkinson's
disease (adjusted hazard ratio 0.95, 95% confidence interval 0.87 to
1.04). Results were consistent across analyses stratified by statin
type (lipophilic vs hydrophilic), dose, and duration of use, and in
sensitivity analyses accounting for reverse causation. No protective
association was observed in analyses restricted to participants with
high cardiovascular risk or in propensity-score matched cohorts.
CONCLUSIONS
In this large prospective cohort, statin use was not associated with
reduced risk of Parkinson's disease, contrary to findings from some
previous observational studies. The null findings were robust across
multiple sensitivity analyses. These results do not support a
neuroprotective effect of statins against Parkinson's disease.
WHAT IS ALREADY KNOWN ON THIS TOPIC
Previous observational studies have yielded inconsistent results
regarding statin use and Parkinson's disease risk.
WHAT THIS STUDY ADDS
This large prospective study with long follow-up found no evidence
that statin use protects against Parkinson's disease.Key Features:
- BMJ uses abbreviated section headers
- Includes "What is already known" and "What this study adds" boxes
- Design, Setting, and Participants as separate sections
- Clear Main Outcome Measures section
---
Key Differences Between Journals
| Element | NEJM | Lancet | JAMA | BMJ |
|---|---|---|---|---|
| Word limit | 250 | 300 | 350 | 300 |
| Results label | RESULTS | FINDINGS | RESULTS | RESULTS |
| Conclusions label | CONCLUSIONS | INTERPRETATION | CONCLUSIONS AND RELEVANCE | CONCLUSIONS |
| Unique sections | — | Funding in abstract | IMPORTANCE | What is known/adds |
| Decimal style | Period (.) | Centered dot (·) | Period (.) | Period (.) |
---
Essential Elements for All Medical Abstracts
Background/Context
- Disease burden or clinical problem (1 sentence)
- Knowledge gap or rationale for study (1 sentence)
Methods
- Study design (RCT, cohort, case-control)
- Setting (number of sites, country/region)
- Participants (N, key inclusion criteria)
- Intervention or exposure
- Primary outcome with definition
Results
- Number enrolled and analyzed
- Primary outcome with effect size and 95% CI
- Key secondary outcomes
- P-values for primary comparisons
- Adverse events (if applicable)
Conclusions
- Clear statement of main finding
- Appropriate hedging based on study design
- Clinical implication (optional, 1 sentence)
---
Common Mistakes in Medical Abstracts
❌ Missing confidence intervals: "HR 0.75, P=0.02" → include 95% CI ❌ Relative risk only: Add absolute risk reduction, NNT ❌ Causal language for observational studies: "PPIs cause kidney disease" ❌ Overstated conclusions: Claims exceeding evidence ❌ Missing sample sizes: Always include N for each group ❌ Vague outcomes: "Improved outcomes" without specific definition
---
See Also
medical_journal_styles.md- Comprehensive medical writing guidevenue_writing_styles.md- Style comparison across venues
Nature/Science Abstract Examples
Examples of well-crafted abstracts for high-impact multidisciplinary journals. These demonstrate the flowing paragraph style with broad accessibility expected at Nature, Science, and related venues.
---
Example 1: Molecular Biology / Cell Biology
Topic: CRISPR gene editing discovery
The ability to precisely edit DNA sequences in living cells has transformed
biological research and holds promise for treating genetic diseases. However,
current genome editing tools can introduce unwanted mutations at off-target
sites, limiting their clinical potential. Here we describe prime editing, a
versatile and precise genome editing method that directly writes new genetic
information into a specified DNA site using a reverse transcriptase fused to a
CRISPR nickase. Prime editing can make all 12 types of point mutations, as
well as small insertions and deletions, with minimal off-target editing and
without requiring double-strand breaks or donor DNA templates. In human cells,
we used prime editing to correct the primary genetic causes of sickle cell
disease and Tay-Sachs disease, and to install protective mutations that
reduce risk of prion disease. Prime editing expands the scope and capabilities
of genome editing and may address approximately 89% of known human genetic
disease variants.Why this works:
- Opens with broad significance (genetic disease treatment)
- States the problem clearly (off-target mutations)
- Describes the approach accessibly ("writes new genetic information")
- Includes specific results (all 12 point mutations, specific diseases)
- Ends with quantified impact (89% of variants)
---
Example 2: Neuroscience
Topic: Memory consolidation mechanism
Sleep is essential for memory consolidation, yet how the sleeping brain
transforms labile memories into stable long-term representations remains
poorly understood. We used multi-site electrophysiology in freely behaving
mice to record the activity of thousands of neurons across hippocampus and
cortex during learning and subsequent sleep. We discovered that specific
neurons that encode a newly learned memory reactivate in precisely timed
sequences during slow-wave sleep, with hippocampal reactivation preceding
cortical reactivation by 10-15 milliseconds. Optogenetic disruption of this
temporal coordination impaired memory retention by 78%, whereas artificial
enhancement of the temporal relationship strengthened memories beyond normal
levels. These results reveal that the temporal ordering of hippocampal-cortical
replay is not merely correlative but causally necessary for memory
consolidation. Our findings suggest new therapeutic approaches for memory
disorders based on optimizing the temporal dynamics of sleep.Why this works:
- Connects to well-known phenomenon (sleep and memory)
- States what was unknown
- Describes approach (multi-site recordings)
- Key finding with specific number (10-15 ms)
- Causal evidence (disruption and enhancement experiments)
- Broader implications (therapeutic approaches)
---
Example 3: Climate Science
Topic: Carbon cycle feedback
Arctic permafrost contains approximately 1,500 billion tonnes of organic
carbon—twice the amount currently in the atmosphere. As the Arctic warms,
this carbon may be released to the atmosphere, accelerating global warming
through a positive feedback loop. However, the magnitude and timing of this
feedback remain highly uncertain because microbial decomposition rates in
thawing permafrost are poorly constrained. Here we present a 15-year
field experiment across 25 sites spanning the Arctic, tracking carbon
fluxes in warming permafrost under natural conditions. We find that
microbial respiration increases exponentially with temperature until soils
reach 3°C, then plateaus due to substrate limitation—a threshold effect
not captured by current Earth system models. Our results suggest that
permafrost carbon feedback will be 30-50% lower than current projections
during this century, providing more time to limit warming, but will
accelerate dramatically if deep permafrost begins to thaw.Why this works:
- Opens with striking number (1,500 billion tonnes)
- Clear problem statement (feedback uncertainty)
- Specific methodology (15 years, 25 sites)
- Novel finding (threshold at 3°C)
- Implications both reassuring and cautionary
---
Example 4: Physics / Materials Science
Topic: Room-temperature superconductivity
Superconductivity—the flow of electricity without resistance—has been
confined to extremely low temperatures since its discovery over a century
ago, limiting practical applications. The recent demonstration of
superconductivity in hydrogen-rich materials at high pressure has raised
hopes for higher transition temperatures, but achieving room-temperature
superconductivity at ambient pressure has remained elusive. Here we report
superconductivity at 21°C (294 K) in a nitrogen-doped lutetium hydride
(Lu-N-H) compound at pressures of approximately 1 GPa—nearly ambient
conditions. Electrical resistance drops to zero below the transition
temperature with a sharp transition width of 2 K, and we observe the Meissner
effect confirming bulk superconductivity. Density functional theory
calculations suggest that nitrogen incorporation stabilizes the high-symmetry
structure that enables strong electron-phonon coupling. These results
establish a pathway toward practical room-temperature superconductors.Why this works:
- Opens with accessible explanation of significance
- Historical context (century-old limitation)
- Precise results (21°C, 1 GPa, 2 K transition width)
- Multiple lines of evidence (resistance + Meissner effect)
- Theoretical explanation briefly included
- Forward-looking conclusion
---
Example 5: Evolution / Ecology
Topic: Rapid evolution in response to climate
Climate change is driving rapid shifts in the geographic distributions of
species, but whether organisms can adapt quickly enough to keep pace with
warming remains a critical question for biodiversity conservation. Here we
document real-time evolution in wild populations of a widespread forest tree,
Scots pine, along a 1,000 km latitudinal gradient in Scandinavia. By combining
whole-genome sequencing with phenotypic measurements across 25 common gardens,
we detect signatures of selection at 47 loci associated with cold tolerance,
phenology, and drought resistance over just 50 years—approximately
five tree generations. Alleles conferring warmer-adapted phenotypes have
increased in frequency by 4-12% across northern populations, matching
predictions from models of climate-driven selection. However, migration of
warm-adapted genotypes from the south appears limited by geographic barriers.
These results demonstrate that trees can evolve rapidly in response to
climate change but suggest that assisted gene flow may be necessary to
prevent local maladaptation.Why this works:
- Opens with pressing question (climate adaptation)
- Specific system (Scots pine) and scale (1,000 km)
- Methods described briefly (genomics + common gardens)
- Quantitative results (47 loci, 4-12% frequency shift, 5 generations)
- Mechanism identified (limited migration)
- Conservation implications stated
---
Common Elements Across Examples
Structure (Implicit)
1. Hook: Why this matters broadly (1-2 sentences) 2. Gap: What was unknown or problematic (1 sentence) 3. Approach: What was done (1 sentence) 4. Findings: Key results with numbers (2-3 sentences) 5. Significance: Why this matters going forward (1 sentence)
Style Features
- Active voice: "We discovered," "We find," "We report"
- Specific numbers: Exact values, not vague quantities
- Accessible language: Minimal jargon, explained when needed
- Compelling opening: Broad hook before technical details
- Strong close: Implications or future directions
Word Count
- Nature: 150-200 words (examples above: 185-210 words)
- Science: ≤125 words (would need tightening)
---
What to Avoid
❌ Too technical opening:
"The CRISPR-Cas9 system with guide RNA targeting PAM sequences..."
✅ Better opening:
"The ability to precisely edit DNA in living cells..."
---
❌ Vague results:
"Our method significantly outperformed existing approaches..."
✅ Better results:
"Our method reduced off-target editing by 78% compared to standard Cas9..."
---
❌ Weak significance statement:
"These findings may have implications for the field..."
✅ Better significance:
"These findings suggest new therapeutic approaches for memory disorders..."
---
See Also
nature_science_style.md- Comprehensive Nature/Science writing guidevenue_writing_styles.md- Style comparison across venues
NeurIPS/ICML Introduction Example
This example demonstrates the distinctive ML conference introduction structure with numbered contributions and technical precision.
---
Full Introduction Example
Paper Topic: Efficient Long-Context Transformers
---
Paragraph 1: Problem Motivation
Large language models (LLMs) have demonstrated remarkable capabilities in
natural language understanding, code generation, and reasoning tasks [1, 2, 3].
These capabilities scale with both model size and context length—longer
contexts enable processing of entire documents, multi-turn conversations,
and complex reasoning chains that span many steps [4, 5]. However, the
standard Transformer attention mechanism [6] has O(N²) time and memory
complexity with respect to sequence length N, creating a fundamental
bottleneck for processing long sequences. For a context window of 100K
tokens, computing full attention requires 10 billion scalar operations
and 40 GB of memory for the attention matrix alone, making training and
inference prohibitively expensive on current hardware.Key features:
- States why this matters (LLM capabilities)
- Connects to scaling (longer contexts = better performance)
- Specific numbers (O(N²), 100K tokens, 10 billion ops, 40 GB)
- Citations to establish credibility
---
Paragraph 2: Limitations of Existing Approaches
Prior work has addressed attention efficiency through three main approaches.
Sparse attention patterns [7, 8, 9] reduce complexity to O(N√N) or O(N log N)
by restricting attention to local windows, fixed stride patterns, or learned
sparse masks. Linear attention approximations [10, 11, 12] reformulate
attention using kernel feature maps that enable O(N) computation, but
sacrifice the ability to model arbitrary pairwise interactions. Low-rank
factorizations [13, 14] approximate the attention matrix as a product of
smaller matrices, achieving efficiency at the cost of expressivity. While
these methods reduce theoretical complexity, they introduce approximation
errors that compound in deep networks, often resulting in 2-5% accuracy
degradation on long-range modeling benchmarks [15]. Perhaps more importantly,
they fundamentally change the attention mechanism, making it difficult to
apply advances in standard attention (e.g., rotary positional embeddings,
grouped-query attention) to efficient variants.Key features:
- Organized categorization of prior work
- Complexity stated for each approach
- Limitations clearly identified
- Quantified shortcomings (2-5% degradation)
- Deeper issue identified (incompatibility with advances)
---
Paragraph 3: Your Approach (High-Level)
We take a different approach: rather than approximating attention, we
accelerate exact attention by optimizing memory access patterns. Our key
observation is that on modern GPUs, attention is bottlenecked by memory
bandwidth, not compute. Reading and writing the N × N attention matrix to
and from GPU high-bandwidth memory (HBM) dominates runtime, while the GPU's
tensor cores remain underutilized. We propose LongFlash, an IO-aware exact
attention algorithm that computes attention block-by-block in fast on-chip
SRAM, never materializing the full attention matrix in HBM. By carefully
orchestrating the tiling pattern and fusing the softmax computation with
matrix multiplications, LongFlash reduces HBM accesses from O(N²) to
O(N²d/M) where d is the head dimension and M is the SRAM size, achieving
asymptotically optimal IO complexity.Key features:
- Clear differentiation from prior work ("different approach")
- Key insight stated explicitly
- Technical mechanism explained
- Complexity improvement quantified
- Method name introduced
---
Paragraph 4: Contributions (CRITICAL)
Our contributions are as follows:
• We propose LongFlash, an IO-aware exact attention algorithm that achieves
2-4× speedup over FlashAttention [16] and up to 9× over standard PyTorch
attention on sequences from 1K to 128K tokens (Section 3).
• We provide theoretical analysis proving that LongFlash achieves optimal
IO complexity of O(N²d/M) among all algorithms that compute exact
attention, and analyze the regime where our algorithm provides maximum
benefit (Section 3.3).
• We introduce sequence parallelism techniques that enable LongFlash to
scale to sequences of 1M+ tokens across multiple GPUs with near-linear
weak scaling efficiency (Section 4).
• We demonstrate that LongFlash enables training with 8× longer contexts
on the same hardware: we train a 7B parameter model on 128K token
contexts using the same memory that previously limited us to 16K tokens
(Section 5).
• We release optimized CUDA kernels achieving 80% of theoretical peak
FLOPS on A100 and H100 GPUs, along with PyTorch and JAX bindings, at
[anonymous URL] (Section 6).Key features:
- Numbered/bulleted format
- Each contribution is specific and quantified
- Section references for each claim
- Both methodological and empirical contributions
- Code release mentioned
- Self-contained bullets (each makes sense alone)
---
Alternative Opening Paragraphs
For a Methods Paper
Scalable optimization algorithms are fundamental to modern machine learning.
Stochastic gradient descent (SGD) and its variants [1, 2, 3] have enabled
training of models with billions of parameters on massive datasets. However,
these first-order methods exhibit slow convergence on ill-conditioned
problems, often requiring thousands of iterations to converge on tasks
where second-order methods would converge in tens of iterations [4, 5].For an Applications Paper
Drug discovery is a costly and time-consuming process, with the average new
drug requiring 10-15 years and $2.6 billion to develop [1]. Machine learning
offers the potential to accelerate this process by predicting molecular
properties, identifying promising candidates, and optimizing lead compounds
computationally [2, 3]. Recent successes in protein structure prediction [4]
and molecular generation [5] have demonstrated that deep learning can
capture complex chemical patterns, raising hopes for ML-driven drug discovery.For a Theory Paper
Understanding why deep neural networks generalize well despite having more
parameters than training examples remains one of the central puzzles of
modern machine learning [1, 2]. Classical statistical learning theory
predicts that such overparameterized models should overfit dramatically,
yet in practice, large networks trained with SGD achieve excellent test
accuracy [3]. This gap between theory and practice has motivated a rich
literature on implicit regularization [4], neural tangent kernels [5],
and feature learning [6], but a complete theoretical picture remains elusive.---
Contribution Bullet Templates
For a New Method
• We propose [Method Name], a novel [type of method] that [key innovation]
achieving [performance improvement] over [baseline] on [benchmark].For Theoretical Analysis
• We prove that [statement], providing the first [type of result] for
[problem setting]. This resolves an open question from [prior work].For Empirical Study
• We conduct a comprehensive evaluation of [N] methods across [M] datasets,
revealing that [key finding] and identifying [failure mode/best practice].For Code/Data Release
• We release [resource name], a [description] containing [scale/scope],
available at [URL]. This enables [future work/reproducibility].---
Common Mistakes to Avoid
Vague Contributions
❌ Bad:
• We propose a novel method for attention
• We show our method is better than baselines
• We provide theoretical analysis✅ Good:
• We propose LongFlash, achieving 2-4× speedup over FlashAttention
• We prove LongFlash achieves optimal O(N²d/M) IO complexity
• We enable 8× longer context training on fixed hardware budgetMissing Quantification
❌ Bad: "Our method significantly outperforms prior work" ✅ Good: "Our method improves accuracy by 3.2% on GLUE and 4.1% on SuperGLUE"
Overlapping Bullets
❌ Bad:
• We propose a new attention mechanism
• We introduce LongFlash attention
• Our novel attention approach...(These say the same thing three times)
Buried Contributions
❌ Bad: Contribution bullets at the end of page 2 ✅ Good: Contribution bullets clearly visible by end of page 1
---
See Also
ml_conference_style.md- Comprehensive ML conference guidevenue_writing_styles.md- Style comparison across venues
% NIH Specific Aims Page Template
% THE MOST CRITICAL PAGE OF YOUR NIH PROPOSAL
% 1 page maximum - strictly enforced
% Last updated: 2024
\documentclass[11pt,letterpaper]{article}
% Formatting
\usepackage[margin=0.5in]{geometry} % 0.5 inch minimum margins
\usepackage{helvet} % Arial-like font
\renewcommand{\familydefault}{\sfdefault}
\usepackage{setspace}
\usepackage{color}
\usepackage{soul} % For highlighting (remove in final version)
% Remove page numbers (optional)
\pagestyle{empty}
\begin{document}
% Optional: Highlight template text to remind yourself to replace
% Remove \hl{} and color in final version
\definecolor{highlight}{RGB}{255,255,200}
\sethlcolor{highlight}
% ====================
% SPECIFIC AIMS PAGE
% ====================
\begin{center}
\textbf{\large Your Project Title Here: Concise and Descriptive}
\end{center}
\vspace{0.3cm}
% OPENING PARAGRAPH: The Hook and Gap
% 2-3 sentences establishing significance and the knowledge gap
\textbf{[Disease/condition]} affects \textbf{[number]} people worldwide and results in \textbf{[burden: mortality, morbidity, cost]}. \textbf{[Current treatment/understanding]} has improved outcomes, but \textbf{[limitation/gap]} remains a critical barrier to \textbf{[desired outcome]}. Understanding \textbf{[specific mechanism/relationship]} is essential for \textbf{[future advance: therapy, prevention, diagnosis]}.
\vspace{0.2cm}
% LONG-TERM GOAL
% 1 sentence on your overarching research vision
Our \textbf{long-term goal} is to \textbf{[overarching vision: develop cure, understand mechanism, improve treatment]} for \textbf{[disease/population]}.
\vspace{0.2cm}
% OBJECTIVE AND CENTRAL HYPOTHESIS
% 1-2 sentences on what THIS proposal will accomplish
The \textbf{objective} of this proposal is to \textbf{[specific objective for this project]}. Our \textbf{central hypothesis} is that \textbf{[clearly stated, testable hypothesis]}.
\vspace{0.2cm}
% RATIONALE
% 2-3 sentences explaining WHY you expect success (preliminary data!)
This hypothesis is based on our \textbf{preliminary data} showing that \textbf{[key preliminary finding 1]} and \textbf{[key preliminary finding 2]}. These findings suggest that \textbf{[mechanistic explanation or expected outcome]}.
\vspace{0.2cm}
% TRANSITION TO AIMS
% 1 sentence introducing the specific aims
To test this hypothesis and achieve our objective, we will pursue the following \textbf{Specific Aims}:
\vspace{0.3cm}
% ====================
% SPECIFIC AIM 1
% ====================
\noindent\textbf{Specific Aim 1: [Concise, active verb title describing what you'll do].}
\textit{Working Hypothesis:} \hl{State testable hypothesis for this aim.}
We will \textbf{[approach/method]} to determine \textbf{[what you'll learn]}. We will use \textbf{[model system/approach]} to test whether \textbf{[specific prediction]}.
\textbf{Expected Outcome:} We expect to find that \textbf{[predicted result]}. This outcome will demonstrate that \textbf{[significance of finding]} and will be \textbf{[positive/negative/innovative/transformative]} because \textbf{[why it matters]}.
\vspace{0.3cm}
% ====================
% SPECIFIC AIM 2
% ====================
\noindent\textbf{Specific Aim 2: [Title of second aim].}
\textit{Working Hypothesis:} \hl{Testable hypothesis for Aim 2.}
Building on Aim 1, we will \textbf{[approach]} to \textbf{[objective]}. We will employ \textbf{[method/technique]} in \textbf{[model/population]} to test the hypothesis that \textbf{[specific prediction]}.
\textbf{Expected Outcome:} These studies will reveal \textbf{[predicted finding]}. This is significant because \textbf{[impact on field/understanding]}.
\vspace{0.3cm}
% ====================
% SPECIFIC AIM 3 (OPTIONAL)
% ====================
\noindent\textbf{Specific Aim 3: [Title of third aim].}
\textit{Working Hypothesis:} \hl{Testable hypothesis for Aim 3.}
To translate findings from Aims 1-2, we will \textbf{[approach]} to determine \textbf{[translational objective]}. We will \textbf{[method]} using \textbf{[clinically relevant model/patient samples]} to test whether \textbf{[translational prediction]}.
\textbf{Expected Outcome:} We anticipate that \textbf{[result]}, which will provide \textbf{[proof-of-concept/validation/mechanism]} for \textbf{[therapeutic/diagnostic/preventive strategy]}.
\vspace{0.3cm}
% ====================
% PAYOFF PARAGRAPH
% ====================
% 2-3 sentences on IMPACT, INNOVATION, and FUTURE DIRECTIONS
\textbf{Impact and Innovation:} This project is \textbf{innovative} because it \textbf{[novel aspect: new concept, method, approach, application]}. The proposed research is \textbf{significant} because it will \textbf{[advance the field by...]} and will ultimately lead to \textbf{[long-term impact: improved treatment, new therapeutic target, diagnostic tool]}. Upon completion of these studies, we will be positioned to \textbf{[next steps: clinical trial, mechanistic studies, therapeutic development]}.
\vspace{0.5cm}
% ====================
% ALTERNATIVE STRUCTURE (if preferred)
% ====================
% Some successful Specific Aims pages use this alternative structure:
% - Open with hook (same as above)
% - State long-term goal and objective (same)
% - Present central hypothesis with 2-3 supporting pieces of preliminary data
% - Then state: "We will test this hypothesis through three Specific Aims:"
% - List aims more concisely (1-2 sentences each, plus expected outcome)
% - Conclude with payoff paragraph emphasizing innovation, significance, impact
\end{document}
% ====================
% TIPS FOR WRITING SPECIFIC AIMS
% ====================
% 1. START WITH A HOOK
% - Open with the big picture: disease burden, societal cost, mortality
% - Use compelling statistics
% - Make it clear why anyone should care
% 2. IDENTIFY THE GAP
% - What's currently known?
% - What's the critical barrier or unknown?
% - Why does it matter?
% 3. STATE YOUR HYPOTHESIS EXPLICITLY
% - Clear, testable hypothesis
% - Not "We hypothesize that we will study..." (that's not a hypothesis!)
% - "We hypothesize that [mechanism] causes [outcome]"
% 4. SHOW PRELIMINARY DATA
% - Demonstrate feasibility
% - Prove you're not starting from scratch
% - Build confidence in your approach
% 5. THREE AIMS (TYPICALLY)
% - Can be 2 or 4, but 3 is most common
% - Aims should be related but somewhat independent
% - Failure of one aim shouldn't sink the whole project
% - Aims can build on each other (Aim 1 → Aim 2 → Aim 3)
% 6. EACH AIM SHOULD HAVE:
% - Clear title (active verb)
% - Working hypothesis
% - Approach/method
% - Expected outcome
% - Significance/impact
% 7. END WITH PAYOFF
% - Innovation: What's new/different?
% - Significance: Why does it matter?
% - Impact: What will change?
% - Future: Where does this lead?
% 8. COMMON MISTAKES TO AVOID
% - Too much background (this is not a mini-review)
% - Vague hypotheses or objectives
% - Missing expected outcomes
% - No preliminary data mentioned
% - Too ambitious (can't do it all in 5 years)
% - Not addressing innovation and significance
% - Poor logical flow between aims
% - Exceeding 1 page (auto-reject!)
% 9. FORMATTING RULES (STRICTLY ENFORCED)
% - 1 page maximum (including all text, no figures typically)
% - Arial 11pt minimum (or equivalent)
% - 0.5 inch margins minimum
% - Any spacing (single, 1.5, double acceptable)
% - No smaller fonts allowed (even for superscripts/subscripts)
% 10. REVISION STRATEGY
% - Write, get feedback, revise 10+ times
% - Every word must earn its place
% - Test on non-specialist colleagues
% - Read aloud to check flow
% - Have it reviewed by successful R01 holders
% - Mock study section review
% ====================
% EXAMPLES OF STRONG OPENING SENTENCES
% ====================
% DISEASE BURDEN APPROACH:
% "Alzheimer's disease (AD) affects 6.7 million Americans and will cost $345 billion in 2023,
% yet no disease-modifying therapies exist."
% MECHANISTIC GAP APPROACH:
% "Despite decades of research, the molecular mechanisms driving metastasis remain poorly understood,
% limiting our ability to develop effective therapies for the 90% of cancer deaths caused by metastatic disease."
% TRANSLATIONAL APPROACH:
% "Current immunotherapies fail in 70% of patients with melanoma, largely because we cannot predict
% who will respond, highlighting an urgent need for biomarkers of treatment response."
% ====================
% REMEMBER
% ====================
% The Specific Aims page is often the ONLY page reviewers read carefully before
% forming their initial opinion. A weak Specific Aims page can doom an otherwise
% excellent proposal. Invest the time to make it compelling, clear, and concise.
% Get feedback from:
% - Successful R01 awardees in your field
% - Grant writing office at your institution
% - Colleagues who've served on NIH study sections
% - Non-specialists (if they can't understand it, reviewers may struggle too)
% NSF Research Proposal Template
% For NSF Standard Grant Proposals
% Last updated: 2024
% Based on NSF PAPPG (Proposal & Award Policies & Procedures Guide)
\documentclass[11pt,letterpaper]{article}
% Required formatting
\usepackage[margin=1in]{geometry} % 1 inch margins required
\usepackage{times} % Times Roman font (11pt minimum)
\usepackage{graphicx}
\usepackage{amsmath}
\usepackage{amssymb}
\usepackage{cite}
\usepackage{hyperref}
% Single spacing (NSF allows single spacing)
\usepackage{setspace}
\singlespacing
% Page numbers
\usepackage{fancyhdr}
\pagestyle{fancy}
\fancyhf{}
\rhead{\thepage}
\renewcommand{\headrulewidth}{0pt}
\begin{document}
% ====================
% PROJECT SUMMARY (1 page maximum)
% ====================
\section*{Project Summary}
\subsection*{Overview}
Provide a concise 1-2 paragraph description of the proposed research. This should be understandable to a scientifically literate reader who is not a specialist in your field.
\subsection*{Intellectual Merit}
Describe how the project advances knowledge within its field and across different fields. Address:
\begin{itemize}
\item How the project advances understanding in the field
\item Innovative aspects of the research
\item Qualifications of the research team
\item Adequacy of resources
\end{itemize}
\subsection*{Broader Impacts}
Describe the potential benefits to society and contributions to desired societal outcomes. Address one or more of the following:
\begin{itemize}
\item Advancing discovery and understanding while promoting teaching and learning
\item Broadening participation of underrepresented groups in STEM
\item Disseminating broadly to enhance scientific and technological understanding
\item Benefits to society (economic development, health, quality of life, national security, etc.)
\item Developing the scientific workforce and enhancing research infrastructure
\end{itemize}
\newpage
% ====================
% PROJECT DESCRIPTION (15 pages maximum)
% ====================
\section*{Project Description}
\section{Introduction and Background}
\subsection{Current State of Knowledge}
Provide context for your proposed research. Review relevant literature and establish what is currently known in the field.
\subsection{Knowledge Gap}
Clearly identify the gap in current knowledge or understanding that your project will address. Explain why this gap is significant.
\subsection{Preliminary Work and Feasibility}
Describe any preliminary work that demonstrates the feasibility of your approach. Highlight your team's qualifications and prior accomplishments.
\section{Research Objectives and Hypotheses}
\subsection{Overall Goal}
State the overarching long-term goal of your research program.
\subsection{Specific Objectives}
List 2-4 specific, measurable objectives for this project:
\begin{enumerate}
\item \textbf{Objective 1:} Clearly stated objective
\item \textbf{Objective 2:} Second objective
\item \textbf{Objective 3:} Third objective
\end{enumerate}
\subsection{Hypotheses}
State your testable hypotheses explicitly.
\section{Research Plan}
\subsection{Objective 1: [Title]}
\subsubsection{Rationale}
Explain why this objective is important and how it addresses the knowledge gap.
\subsubsection{Approach and Methods}
Describe in detail how you will accomplish this objective. Include:
\begin{itemize}
\item Experimental design or computational approach
\item Methods and procedures
\item Data collection and analysis
\item Controls and validation
\end{itemize}
\subsubsection{Expected Outcomes}
Describe what results you expect and how they will advance the field.
\subsubsection{Potential Challenges and Alternatives}
Identify potential obstacles and describe alternative approaches.
\subsection{Objective 2: [Title]}
[Repeat same structure as Objective 1]
\subsection{Objective 3: [Title]}
[Repeat same structure as Objective 1]
\section{Timeline and Milestones}
Provide a detailed timeline showing when each objective will be addressed:
\begin{center}
\begin{tabular}{|l|p{3cm}|p{3cm}|p{3cm}|}
\hline
\textbf{Activity} & \textbf{Year 1} & \textbf{Year 2} & \textbf{Year 3} \\
\hline
Objective 1 activities & Months 1-6: ... & & \\
\hline
Objective 2 activities & Months 7-12: ... & Months 13-18: ... & \\
\hline
Objective 3 activities & & Months 19-24: ... & Months 25-36: ... \\
\hline
Publications & & Submit paper 1 & Submit papers 2-3 \\
\hline
\end{tabular}
\end{center}
\section{Broader Impacts}
\textit{Note: Broader Impacts must be substantive, not perfunctory. Integrate throughout proposal.}
\subsection{Educational Activities}
Describe specific educational activities integrated with the research:
\begin{itemize}
\item Curriculum development
\item Training of graduate and undergraduate students
\item K-12 outreach programs
\item Public science communication
\end{itemize}
\subsection{Broadening Participation}
Describe concrete efforts to broaden participation of underrepresented groups:
\begin{itemize}
\item Recruitment strategies
\item Mentoring programs
\item Partnerships with minority-serving institutions
\item Measurable outcomes
\end{itemize}
\subsection{Dissemination and Outreach}
Describe plans for broad dissemination:
\begin{itemize}
\item Open-access publications
\item Data and code sharing (repositories, licenses)
\item Conference presentations and workshops
\item Public engagement activities
\end{itemize}
\subsection{Societal Benefits}
Explain potential benefits to society:
\begin{itemize}
\item Economic development
\item Health and quality of life improvements
\item Environmental sustainability
\item National security (if applicable)
\end{itemize}
\subsection{Assessment of Broader Impacts}
Describe how you will measure the success of broader impacts activities. Include specific, measurable outcomes.
\section{Results from Prior NSF Support}
\textit{Required if PI or co-PI has received NSF funding in the past 5 years}
\subsection{Award Title and Number}
Award Number: NSF-XXXXX, Amount: \$XXX,XXX, Period: MM/YY - MM/YY
\subsection{Intellectual Merit}
Summarize research accomplishments and findings from prior award.
\subsection{Broader Impacts}
Describe broader impacts activities and outcomes from prior award.
\subsection{Publications}
List publications resulting from prior NSF support (up to 5 most significant):
\begin{enumerate}
\item Author, A.A., et al. (Year). Title. \textit{Journal}, vol(issue), pages.
\end{enumerate}
\newpage
% ====================
% REFERENCES CITED (No page limit)
% ====================
\section*{References Cited}
\begin{thebibliography}{99}
\bibitem{ref1}
Author, A.A., \& Author, B.B. (2023). Article title. \textit{Journal Name}, \textit{45}(3), 123-145.
\bibitem{ref2}
Author, C.C., Author, D.D., \& Author, E.E. (2022). Book title. Publisher.
\bibitem{ref3}
Author, F.F., et al. (2021). Another article. \textit{Nature}, \textit{590}, 234-238.
% Add more references as needed
\end{thebibliography}
\newpage
% ====================
% BUDGET JUSTIFICATION (3-5 pages typical)
% Note: Budget is submitted separately in NSF's systems
% This justifies the budget requests
% ====================
\section*{Budget Justification}
\subsection*{A. Senior Personnel}
\textbf{PI Name (X\% academic year, Y summer months):} Justify percent effort and role in project. Summer salary calculated as X/9 of academic year salary.
\textbf{Co-PI Name (X\% academic year):} Justify role and effort.
\subsection*{B. Other Personnel}
\textbf{Postdoctoral Researcher (1.0 FTE, Years 1-3):} Justify need for postdoc, qualifications required, and role in project. Salary: \$XX,XXX/year.
\textbf{Graduate Student (2 students, Years 1-3):} Justify need, training opportunities, and project contributions. Stipend: \$XX,XXX/year per student.
\textbf{Undergraduate Researchers (2 students/year):} Describe research training opportunities. Hourly wage: \$XX/hour.
\subsection*{C. Fringe Benefits}
List fringe benefit rates for each personnel category as determined by institution.
\subsection*{D. Equipment (\$5,000+)}
\textbf{Instrument Name (\$XX,XXX):} Justify need, explain why existing equipment inadequate, describe how it enables proposed research.
\subsection*{E. Travel}
\textbf{Domestic Conference Travel (\$X,XXX/year):} Justify conference attendance for dissemination (1-2 conferences/year for PI and students).
\textbf{Field Work Travel (\$X,XXX):} If applicable, justify field site visits.
\subsection*{F. Participant Support Costs}
\textit{If hosting workshop, summer program, etc.}
Stipends, travel, and per diem for XX participants attending [workshop/program name].
\subsection*{G. Other Direct Costs}
\textbf{Materials and Supplies (\$X,XXX/year):} Itemize major categories (e.g., chemicals, consumables, software licenses).
\textbf{Publication Costs (\$X,XXX):} Budget for open-access publication fees (estimate X papers @ \$X,XXX each).
\textbf{Subaward to Partner Institution (\$XX,XXX):} Justify collaboration and subaward amount.
\textbf{Other:} Justify any other costs.
\subsection*{H. Indirect Costs}
Calculated at XX\% of Modified Total Direct Costs (institution's negotiated rate).
\newpage
% ====================
% DATA MANAGEMENT PLAN (2 pages maximum)
% ====================
\section*{Data Management Plan}
\subsection*{Types of Data}
Describe the types of data to be generated by the project:
\begin{itemize}
\item Experimental data (e.g., measurements, observations)
\item Computational data (e.g., simulation results, models)
\item Metadata describing data collection and processing
\end{itemize}
\subsection*{Data and Metadata Standards}
Describe standards to be used for data format and metadata:
\begin{itemize}
\item File formats (e.g., HDF5, NetCDF, CSV)
\item Metadata standards (e.g., Dublin Core, domain-specific standards)
\item Documentation of data collection and processing
\end{itemize}
\subsection*{Policies for Access and Sharing}
Describe how data will be made accessible:
\begin{itemize}
\item Repository for data deposition (e.g., Dryad, Zenodo, domain-specific archive)
\item Timeline for public release (immediately upon publication, or within X months)
\item Access restrictions (if any) and justification
\item Embargo periods (if applicable)
\end{itemize}
\subsection*{Policies for Re-use, Redistribution}
Describe terms for re-use:
\begin{itemize}
\item Licensing (e.g., CC0, CC-BY, specific data use agreement)
\item Attribution requirements
\item Restrictions on commercial use (if any)
\end{itemize}
\subsection*{Plans for Archiving and Preservation}
Describe long-term preservation strategy:
\begin{itemize}
\item Repository selection (long-term, stable repositories)
\item Preservation period (minimum 3-5 years post-project)
\item Data formats for long-term preservation
\item Institutional commitments
\end{itemize}
\subsection*{Roles and Responsibilities}
Identify who is responsible for data management implementation.
\end{document}
% ====================
% ADDITIONAL DOCUMENTS (submitted separately in NSF system)
% ====================
% 1. BIOGRAPHICAL SKETCH (3 pages per person)
% - Use NSF-approved format (SciENcv or NSF template)
% - Professional preparation
% - Appointments
% - Products (up to 5 most relevant, up to 5 other significant)
% - Synergistic activities
% 2. CURRENT AND PENDING SUPPORT
% - All current and pending support for all senior personnel
% - Use NSF format
% - Check for overlap with proposed project
% 3. FACILITIES, EQUIPMENT, AND OTHER RESOURCES
% - Describe available facilities and equipment
% - Computational resources
% - Laboratory space
% - Other resources supporting the project
% ====================
% FORMATTING CHECKLIST
% ====================
% ☐ Margins: 1 inch on all sides
% ☐ Font: Times Roman 11pt or larger (or equivalent)
% ☐ Line spacing: Single spacing acceptable
% ☐ Project Summary: 1 page, includes Overview, Intellectual Merit, Broader Impacts
% ☐ Project Description: 15 pages maximum
% ☐ References Cited: No page limit, consistent formatting
% ☐ Biographical Sketches: 3 pages per person, NSF-approved format
% ☐ Budget Justification: Detailed and reasonable
% ☐ Data Management Plan: 2 pages maximum
% ☐ Current & Pending: Complete and accurate
% ☐ Facilities: Adequate resources described
% ☐ Broader Impacts: Substantive and integrated throughout
% ☐ All required sections included
% ====================
% SUBMISSION NOTES
% ====================
% 1. Submit through Research.gov or Grants.gov
% 2. Follow your institution's internal deadlines (usually 3-5 days before NSF deadline)
% 3. Obtain institutional approval before submission
% 4. Ensure all senior personnel have NSF IDs
% 5. Budget prepared in NSF's system (separate from this document)
% 6. Check program-specific requirements (may differ from standard grant)
% 7. Contact Program Officer for guidance (encouraged but not required)
%%
%% This is file `elsarticle-harv.bst' (Version 2.1),
%%
%% Copyright 2009-2024 Elsevier Ltd
%%
%% This file is part of the 'Elsarticle Bundle'.
%% ---------------------------------------------
%%
%% It may be distributed under the conditions of the LaTeX Project Public
%% License, either version 1.3 of this license or (at your option) any
%% later version. The latest version of this license is in
%% http://www.latex-project.org/lppl.txt
%% and version 1.3 or later is part of all distributions of LaTeX
%% version 1999/12/01 or later.
%%
%% $Id: elsarticle-harv.bst 255 2024-04-06 10:58:47Z rishi $
%%
%% $URL: https://lenova.river-valley.com/svn/elsarticle/trunk/elsarticle-harv.bst $
%%
ENTRY
{ address
archive
author
booktitle
chapter
collaboration
edition
editor
howpublished
institution
journal
key
month
note
number
organization
pages
publisher
school
series
title
type
volume
year
url
doi
eprint
pubmed
}
{}
{ label extra.label sort.label short.list }
INTEGERS { output.state before.all mid.sentence after.sentence after.block }
STRINGS { urlprefix doiprefix eprintprefix pubmedprefix }
FUNCTION {init.web.variables}
{
"\URLprefix " 'urlprefix :=
"\DOIprefix" 'doiprefix :=
"\ArXivprefix " 'eprintprefix :=
"\Pubmedprefix " 'pubmedprefix :=
}
FUNCTION {init.state.consts}
{ #0 'before.all :=
#1 'mid.sentence :=
#2 'after.sentence :=
#3 'after.block :=
}
STRINGS { s t}
FUNCTION {output.comma}
{ ", " * write$}
FUNCTION {output.nonnull}
{ 's :=
output.state mid.sentence =
{ ". " * write$ }
{ output.state after.block =
{ add.period$ write$
newline$
"\newblock " write$
}
{ output.state before.all =
'write$
{ ", " * write$ }
if$
}
if$
mid.sentence 'output.state :=
}
if$
s
}
FUNCTION {output.commanull}
{ 's :=
output.state mid.sentence =
{ ", " * write$ }
{ output.state after.block =
{ ", " * write$
newline$
"\newblock " write$
}
{ output.state before.all =
'write$
{ add.period$ " " * write$ }
if$
}
if$
mid.sentence 'output.state :=
}
if$
s
}
FUNCTION {output}
{ duplicate$ empty$
'pop$
'output.nonnull
if$
}
FUNCTION {output.check}
{ 't :=
duplicate$ empty$
{ pop$ "empty " t * " in " * cite$ * warning$ }
'output.nonnull
if$
}
FUNCTION {output.book.check}
{ 't :=
duplicate$ empty$
{ pop$ "empty " t * " in " * cite$ * warning$ }
'output.nonnull
if$
}
FUNCTION {fin.entry}
{ add.period$
write$
newline$
}
FUNCTION {new.block}
{ output.state before.all =
'skip$
{ after.block 'output.state := }
if$
}
FUNCTION {new.sentence}
{ output.state after.block =
'skip$
{ output.state before.all =
'skip$
{ after.sentence 'output.state := }
if$
}
if$
}
FUNCTION {add.blank}
{ " " * before.all 'output.state :=
}
FUNCTION {date.block}
{
new.block
}
FUNCTION {not}
{ { #0 }
{ #1 }
if$
}
FUNCTION {and}
{ 'skip$
{ pop$ #0 }
if$
}
FUNCTION {or}
{ { pop$ #1 }
'skip$
if$
}
FUNCTION {new.block.checkb}
{ empty$
swap$ empty$
and
'skip$
'new.block
if$
}
FUNCTION {field.or.null}
{ duplicate$ empty$
{ pop$ "" }
'skip$
if$
}
FUNCTION {emphasize}
{ duplicate$ empty$
{ pop$ "" }
{ "\textit{" swap$ * "}" * }
if$
}
FUNCTION {tie.or.space.prefix}
{ duplicate$ text.length$ #3 <
{ "~" }
{ " " }
if$
swap$
}
FUNCTION {capitalize}
{ "u" change.case$ "t" change.case$ }
FUNCTION {space.word}
{ " " swap$ * " " * }
% Here are the language-specific definitions for explicit words.
% Each function has a name bbl.xxx where xxx is the English word.
% The language selected here is ENGLISH
FUNCTION {bbl.and}
{ "and"}
FUNCTION {bbl.etal}
{ "et~al." }
FUNCTION {bbl.editors}
{ "Eds." }
FUNCTION {bbl.editor}
{ "Ed." }
FUNCTION {bbl.edby}
{ "edited by" }
FUNCTION {bbl.edition}
{ "ed." }
FUNCTION {bbl.volume}
{ "volume" }
FUNCTION {bbl.of}
{ "of" }
FUNCTION {bbl.number}
{ "number" }
FUNCTION {bbl.nr}
{ "no." }
FUNCTION {bbl.in}
{ "in" }
FUNCTION {bbl.pages}
{ "pp." }
FUNCTION {bbl.page}
{ "p." }
FUNCTION {bbl.chapter}
{ "chapter" }
FUNCTION {bbl.techrep}
{ "Technical Report" }
FUNCTION {bbl.mthesis}
{ "Master's thesis" }
FUNCTION {bbl.phdthesis}
{ "Ph.D. thesis" }
MACRO {jan} {"January"}
MACRO {feb} {"February"}
MACRO {mar} {"March"}
MACRO {apr} {"April"}
MACRO {may} {"May"}
MACRO {jun} {"June"}
MACRO {jul} {"July"}
MACRO {aug} {"August"}
MACRO {sep} {"September"}
MACRO {oct} {"October"}
MACRO {nov} {"November"}
MACRO {dec} {"December"}
MACRO {acmcs} {"ACM Comput. Surv."}
MACRO {acta} {"Acta Inf."}
MACRO {cacm} {"Commun. ACM"}
MACRO {ibmjrd} {"IBM J. Res. Dev."}
MACRO {ibmsj} {"IBM Syst.~J."}
MACRO {ieeese} {"IEEE Trans. Software Eng."}
MACRO {ieeetc} {"IEEE Trans. Comput."}
MACRO {ieeetcad}
{"IEEE Trans. Comput. Aid. Des."}
MACRO {ipl} {"Inf. Process. Lett."}
MACRO {jacm} {"J.~ACM"}
MACRO {jcss} {"J.~Comput. Syst. Sci."}
MACRO {scp} {"Sci. Comput. Program."}
MACRO {sicomp} {"SIAM J. Comput."}
MACRO {tocs} {"ACM Trans. Comput. Syst."}
MACRO {tods} {"ACM Trans. Database Syst."}
MACRO {tog} {"ACM Trans. Graphic."}
MACRO {toms} {"ACM Trans. Math. Software"}
MACRO {toois} {"ACM Trans. Office Inf. Syst."}
MACRO {toplas} {"ACM Trans. Progr. Lang. Syst."}
MACRO {tcs} {"Theor. Comput. Sci."}
FUNCTION {bibinfo.check}
{ swap$
duplicate$ missing$
{
pop$ pop$
""
}
{ duplicate$ empty$
{
swap$ pop$
}
{ swap$
"\bibinfo{" swap$ * "}{" * swap$ * "}" *
}
if$
}
if$
}
FUNCTION {bibinfo.warn}
{ swap$
duplicate$ missing$
{
swap$ "missing " swap$ * " in " * cite$ * warning$ pop$
""
}
{ duplicate$ empty$
{
swap$ "empty " swap$ * " in " * cite$ * warning$
}
{ swap$
pop$
}
if$
}
if$
}
STRINGS { bibinfo}
INTEGERS { nameptr namesleft numnames }
FUNCTION {format.names}
{ 'bibinfo :=
duplicate$ empty$ 'skip$ {
's :=
"" 't :=
#1 'nameptr :=
s num.names$ 'numnames :=
numnames 'namesleft :=
{ namesleft #0 > }
{ s nameptr
"{vv~}{ll}{, jj}{, f{.}.}"
format.name$
bibinfo bibinfo.check
't :=
nameptr #1 >
{
namesleft #1 >
{ ", " * t * }
{
"," *
s nameptr "{ll}" format.name$ duplicate$ "others" =
{ 't := }
{ pop$ }
if$
t "others" =
{
" " * bbl.etal *
}
{ " " * t * }
if$
}
if$
}
't
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
} if$
}
FUNCTION {format.names.ed}
{
format.names
}
FUNCTION {format.key}
{ empty$
{ key field.or.null }
{ "" }
if$
}
FUNCTION {format.authors}
{ author "author" format.names
duplicate$ empty$ 'skip$
{ collaboration "collaboration" bibinfo.check
duplicate$ empty$ 'skip$
{ " (" swap$ * ")" * }
if$
*
}
if$
}
FUNCTION {get.bbl.editor}
{ editor num.names$ #1 > 'bbl.editors 'bbl.editor if$ }
FUNCTION {format.editors}
{ editor "editor" format.names duplicate$ empty$ 'skip$
{
" " *
get.bbl.editor
capitalize
"(" swap$ * ")" *
*
}
if$
}
FUNCTION {format.note}
{
note empty$
{ "" }
{ note #1 #1 substring$
duplicate$ "{" =
'skip$
{ output.state mid.sentence =
{ "l" }
{ "u" }
if$
change.case$
}
if$
note #2 global.max$ substring$ * "note" bibinfo.check
}
if$
}
FUNCTION {format.title}
{ title
duplicate$ empty$ 'skip$
{ "t" change.case$ }
if$
"title" bibinfo.check
}
FUNCTION {format.full.names}
{'s :=
"" 't :=
#1 'nameptr :=
s num.names$ 'numnames :=
numnames 'namesleft :=
{ namesleft #0 > }
{ s nameptr
"{vv~}{ll}" format.name$
't :=
nameptr #1 >
{
namesleft #1 >
{ ", " * t * }
{
s nameptr "{ll}" format.name$ duplicate$ "others" =
{ 't := }
{ pop$ }
if$
t "others" =
{
" " * bbl.etal *
}
{
bbl.and
space.word * t *
}
if$
}
if$
}
't
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
}
FUNCTION {author.editor.key.full}
{ author empty$
{ editor empty$
{ key empty$
{ cite$ #1 #3 substring$ }
'key
if$
}
{ editor format.full.names }
if$
}
{ author format.full.names }
if$
}
FUNCTION {author.key.full}
{ author empty$
{ key empty$
{ cite$ #1 #3 substring$ }
'key
if$
}
{ author format.full.names }
if$
}
FUNCTION {editor.key.full}
{ editor empty$
{ key empty$
{ cite$ #1 #3 substring$ }
'key
if$
}
{ editor format.full.names }
if$
}
FUNCTION {make.full.names}
{ type$ "book" =
type$ "inbook" =
or
'author.editor.key.full
{ type$ "proceedings" =
'editor.key.full
'author.key.full
if$
}
if$
}
FUNCTION {output.bibitem}
{ newline$
"\bibitem[{" write$
label write$
")" make.full.names duplicate$ short.list =
{ pop$ }
{ * }
if$
"}]{" * write$
cite$ write$
"}" write$
newline$
""
before.all 'output.state :=
}
FUNCTION {n.dashify}
{
't :=
""
{ t empty$ not }
{ t #1 #1 substring$ "-" =
{ t #1 #2 substring$ "--" = not
{ "--" *
t #2 global.max$ substring$ 't :=
}
{ { t #1 #1 substring$ "-" = }
{ "-" *
t #2 global.max$ substring$ 't :=
}
while$
}
if$
}
{ t #1 #1 substring$ *
t #2 global.max$ substring$ 't :=
}
if$
}
while$
}
FUNCTION {word.in}
{ bbl.in %capitalize
":" *
" " * }
FUNCTION {format.date}
{ year "year" bibinfo.check duplicate$ empty$
{
}
'skip$
if$
extra.label *
before.all 'output.state :=
", " swap$ *
}
FUNCTION {format.btitle}
{ title "title" bibinfo.check
duplicate$ empty$ 'skip$
{
}
if$
}
FUNCTION {either.or.check}
{ empty$
'pop$
{ "can't use both " swap$ * " fields in " * cite$ * warning$ }
if$
}
FUNCTION {format.bvolume}
{ volume empty$
{ "" }
{ bbl.volume volume tie.or.space.prefix
"volume" bibinfo.check * *
series "series" bibinfo.check
duplicate$ empty$ 'pop$
{ swap$ bbl.of space.word * swap$
emphasize * }
if$
"volume and number" number either.or.check
}
if$
}
FUNCTION {format.number.series}
{ volume empty$
{ number empty$
{ series field.or.null }
{ series empty$
{ number "number" bibinfo.check }
{ output.state mid.sentence =
{ bbl.number }
{ bbl.number capitalize }
if$
number tie.or.space.prefix "number" bibinfo.check * *
bbl.in space.word *
series "series" bibinfo.check *
}
if$
}
if$
}
{ "" }
if$
}
FUNCTION {format.edition}
{ edition duplicate$ empty$ 'skip$
{
output.state mid.sentence =
{ "l" }
{ "t" }
if$ change.case$
"edition" bibinfo.check
" " * bbl.edition *
}
if$
}
INTEGERS { multiresult }
FUNCTION {multi.page.check}
{ 't :=
#0 'multiresult :=
{ multiresult not
t empty$ not
and
}
{ t #1 #1 substring$
duplicate$ "-" =
swap$ duplicate$ "," =
swap$ "+" =
or or
{ #1 'multiresult := }
{ t #2 global.max$ substring$ 't := }
if$
}
while$
multiresult
}
%FUNCTION {format.pages}
%{ pages duplicate$ empty$ 'skip$
% { duplicate$ multi.page.check
% {
% n.dashify
% }
% {
% }
% if$
% "pages" bibinfo.check
% }
% if$
%}
FUNCTION {format.pages}
{ pages duplicate$ empty$ 'skip$
{ duplicate$ multi.page.check
{
bbl.pages swap$
n.dashify
}
{
bbl.page swap$
}
if$
tie.or.space.prefix
"pages" bibinfo.check
* *
}
if$
}
FUNCTION {format.journal.pages}
{ pages duplicate$ empty$ 'pop$
{ swap$ duplicate$ empty$
{ pop$ pop$ format.pages }
{
", " *
swap$
n.dashify
"pages" bibinfo.check
*
}
if$
}
if$
}
FUNCTION {format.vol.num.pages}
{ volume field.or.null
duplicate$ empty$ 'skip$
{
"volume" bibinfo.check
}
if$
}
FUNCTION {format.chapter.pages}
{ chapter empty$
{ "" }
{ type empty$
{ bbl.chapter }
{ type "l" change.case$
"type" bibinfo.check
}
if$
chapter tie.or.space.prefix
"chapter" bibinfo.check
* *
}
if$
}
FUNCTION {format.booktitle}
{
booktitle "booktitle" bibinfo.check
}
FUNCTION {format.in.ed.booktitle}
{ format.booktitle duplicate$ empty$ 'skip$
{
editor "editor" format.names.ed duplicate$ empty$ 'pop$
{
" " *
get.bbl.editor
capitalize
"(" swap$ * "), " *
* swap$
* }
if$
word.in swap$ *
}
if$
}
FUNCTION {format.thesis.type}
{ type duplicate$ empty$
'pop$
{ swap$ pop$
"t" change.case$ "type" bibinfo.check
}
if$
}
FUNCTION {format.tr.number}
{ number "number" bibinfo.check
type duplicate$ empty$
{ pop$ bbl.techrep }
'skip$
if$
"type" bibinfo.check
swap$ duplicate$ empty$
{ pop$ "t" change.case$ }
{ tie.or.space.prefix * * }
if$
}
FUNCTION {format.article.crossref}
{
word.in
" \cite{" * crossref * "}" *
}
FUNCTION {format.book.crossref}
{ volume duplicate$ empty$
{ "empty volume in " cite$ * "'s crossref of " * crossref * warning$
pop$ word.in
}
{ bbl.volume
capitalize
swap$ tie.or.space.prefix "volume" bibinfo.check * * bbl.of space.word *
}
if$
" \cite{" * crossref * "}" *
}
FUNCTION {format.incoll.inproc.crossref}
{
word.in
" \cite{" * crossref * "}" *
}
FUNCTION {format.org.or.pub}
{ 't :=
""
address empty$ t empty$ and
'skip$
{
t empty$
{ address "address" bibinfo.check *
}
{ t *
address empty$
'skip$
{ ", " * address "address" bibinfo.check * }
if$
}
if$
}
if$
}
FUNCTION {format.publisher.address}
{ publisher "publisher" bibinfo.check format.org.or.pub
}
FUNCTION {format.organization.address}
{ organization "organization" bibinfo.check format.org.or.pub
}
FUNCTION {print.url}
{url duplicate$ empty$
{ pop$ "" }
{ new.sentence
urlprefix "\url{" * swap$ * "}" *
}
if$
}
FUNCTION {print.doi}
{doi duplicate$ empty$
{ pop$ "" }
{ new.sentence
doiprefix "\doi{" * swap$ * "}" *
}
if$
}
FUNCTION {print.eprint}
{eprint duplicate$ empty$
{ pop$ "" }
{ new.sentence
duplicate$ "\href{http://arxiv.org/abs/" swap$ * "}{{\tt arXiv:" * swap$ * "}}" * }
if$
}
FUNCTION {print.pubmed}
{pubmed duplicate$ empty$
{ pop$ "" }
{ new.sentence
pubmedprefix "\Pubmed{" * swap$ * "}" *
}
if$
}
FUNCTION {webpage}
{ "%Type = Webpage" write$
output.bibitem
format.authors "author" output.check
author format.key output
author empty$
{
format.title "title" output.check
new.block
format.date "year" output.check
date.block
}
{
format.date "year" output.check
date.block
format.title "title" output.check
new.block
}
if$
print.url output
fin.entry
}
FUNCTION {article}
{ "%Type = Article" write$
output.bibitem
format.authors "author" output.check
author format.key output
format.date "year" output.check
date.block
format.title "title" output.check
new.block
crossref missing$
{
journal
"journal" bibinfo.check
"journal" output.check
add.blank
format.vol.num.pages output
}
{ format.article.crossref output.nonnull
}
if$
format.journal.pages
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {book}
{ "%Type = Book" write$
output.bibitem
author empty$
{ format.editors "author and editor" output.check
editor format.key output
}
{ format.authors output.nonnull
crossref missing$
{ "author and editor" editor either.or.check }
'skip$
if$
}
if$
format.date "year" output.check
date.block
format.btitle "title" output.check
crossref missing$
{ format.bvolume output
new.block
format.number.series output
format.edition output
new.sentence
format.publisher.address output
}
{
new.block
format.book.crossref output.nonnull
}
if$
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {booklet}
{ "%Type = Booklet" write$
output.bibitem
format.authors output
author format.key output
format.date "year" output.check
date.block
format.title "title" output.check
new.block
howpublished "howpublished" bibinfo.check output
address "address" bibinfo.check output
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {inbook}
{ "%Type = Inbook" write$
output.bibitem
author empty$
{ format.editors "author and editor" output.check
editor format.key output
}
{ format.authors output.nonnull
crossref missing$
{ "author and editor" editor either.or.check }
'skip$
if$
}
if$
format.date "year" output.check
date.block
format.btitle "title" output.check
format.edition output
crossref missing$
{
format.publisher.address output
format.bvolume output
format.chapter.pages "chapter and pages" output.check
new.block
format.number.series output
new.sentence
}
{
format.chapter.pages "chapter and pages" output.check
new.block
format.book.crossref output.nonnull
}
if$
format.pages "pages" output.check
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {incollection}
{ "%Type = Incollection" write$
output.bibitem
format.authors "author" output.check
author format.key output
format.date "year" output.check
date.block
format.title "title" output.book.check
new.sentence
crossref missing$
{ format.in.ed.booktitle "booktitle" output.book.check
format.edition output
format.publisher.address output
format.bvolume output
format.number.series output
format.chapter.pages output
new.sentence
}
{ format.incoll.inproc.crossref output.nonnull
format.chapter.pages output
}
if$
format.pages "pages" output.check
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {inproceedings}
{ "%Type = Inproceedings" write$
output.bibitem
format.authors "author" output.check
author format.key output
format.date "year" output.check
date.block
format.title "title" output.book.check
new.sentence
crossref missing$
{ format.in.ed.booktitle "booktitle" output.check
new.sentence
publisher empty$
{ format.organization.address output }
{ organization "organization" bibinfo.check output
format.publisher.address output
}
if$
% format.bvolume output
% format.number.series output
% format.pages output
}
{ format.incoll.inproc.crossref output.nonnull
format.pages output
}
if$
format.pages "pages" output.check
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {conference} { inproceedings }
FUNCTION {manual}
{ "%Type = Manual" write$
output.bibitem
format.authors output
author format.key output
format.date "year" output.check
date.block
format.btitle "title" output.check
format.edition output
organization address new.block.checkb
organization "organization" bibinfo.check output
address "address" bibinfo.check output
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {mastersthesis}
{ "%Type = Masterthesis" write$
output.bibitem
format.authors "author" output.check
author format.key output
format.date "year" output.check
date.block
format.btitle
"title" output.check
new.block
bbl.mthesis format.thesis.type output.nonnull
school "school" bibinfo.warn output
address "address" bibinfo.check output
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {misc}
{ "%Type = Misc" write$
output.bibitem
format.authors output
author format.key output
format.date "year" output.check
date.block
format.title output
new.block
howpublished "howpublished" bibinfo.check output
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {phdthesis}
{ "%Type = Phdthesis" write$
output.bibitem
format.authors "author" output.check
author format.key output
format.date "year" output.check
date.block
format.btitle
"title" output.check
new.block
bbl.phdthesis format.thesis.type output.nonnull
school "school" bibinfo.warn output
address "address" bibinfo.check output
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {proceedings}
{ "%Type = Proceedings" write$
output.bibitem
format.editors output
editor format.key output
format.date "year" output.check
date.block
format.btitle "title" output.check
format.bvolume output
format.number.series output
new.sentence
publisher empty$
{ format.organization.address output }
{ organization "organization" bibinfo.check output
format.publisher.address output
}
if$
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {techreport}
{ "%Type = Techreport" write$
output.bibitem
format.authors "author" output.check
author format.key output
format.date "year" output.check
date.block
format.btitle
"title" output.check
new.block
format.tr.number output.nonnull
institution "institution" bibinfo.warn output
address "address" bibinfo.check output
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note output
fin.entry
}
FUNCTION {unpublished}
{ "%Type = Unpublished" write$
output.bibitem
format.authors "author" output.check
author format.key output
format.date "year" output.check
date.block
format.title "title" output.check
new.block
print.url output
print.doi output
print.eprint output
print.pubmed output
format.note "note" output.check
fin.entry
}
FUNCTION {default.type} { misc }
READ
FUNCTION {sortify}
{ purify$
"l" change.case$
}
INTEGERS { len }
FUNCTION {chop.word}
{ 's :=
'len :=
s #1 len substring$ =
{ s len #1 + global.max$ substring$ }
's
if$
}
FUNCTION {format.lab.names}
{ 's :=
"" 't :=
s #1 "{vv~}{ll}" format.name$
s num.names$ duplicate$
#2 >
{ pop$
" " * bbl.etal *
}
{ #2 <
'skip$
{ s #2 "{ff }{vv }{ll}{ jj}" format.name$ "others" =
{
" " * bbl.etal *
}
{ bbl.and space.word * s #2 "{vv~}{ll}" format.name$
* }
if$
}
if$
}
if$
}
FUNCTION {author.key.label}
{ author empty$
{ key empty$
{ cite$ #1 #3 substring$ }
'key
if$
}
{ author format.lab.names }
if$
}
FUNCTION {author.editor.key.label}
{ author empty$
{ editor empty$
{ key empty$
{ cite$ #1 #3 substring$ }
'key
if$
}
{ editor format.lab.names }
if$
}
{ author format.lab.names }
if$
}
FUNCTION {editor.key.label}
{ editor empty$
{ key empty$
{ cite$ #1 #3 substring$ }
'key
if$
}
{ editor format.lab.names }
if$
}
FUNCTION {calc.short.authors}
{ type$ "book" =
type$ "inbook" =
or
'author.editor.key.label
{ type$ "proceedings" =
'editor.key.label
'author.key.label
if$
}
if$
'short.list :=
}
FUNCTION {calc.label}
{ calc.short.authors
short.list
"("
*
year duplicate$ empty$
short.list key field.or.null = or
{ pop$ "" }
'skip$
if$
*
'label :=
}
FUNCTION {sort.format.names}
{ 's :=
#1 'nameptr :=
""
s num.names$ 'numnames :=
numnames 'namesleft :=
{ namesleft #0 > }
{ s nameptr
"{ll{ }}{ f{ }}{ jj{ }}"
format.name$ 't :=
nameptr #1 >
{
" " *
namesleft #1 = t "others" = and
{ "zzzzz" * }
{ t sortify * }
if$
}
{ t sortify * }
if$
nameptr #1 + 'nameptr :=
namesleft #1 - 'namesleft :=
}
while$
}
FUNCTION {sort.format.title}
{ 't :=
"A " #2
"An " #3
"The " #4 t chop.word
chop.word
chop.word
sortify
#1 global.max$ substring$
}
FUNCTION {author.sort}
{ author empty$
{ key empty$
{ "to sort, need author or key in " cite$ * warning$
""
}
{ key sortify }
if$
}
{ author sort.format.names }
if$
}
FUNCTION {author.editor.sort}
{ author empty$
{ editor empty$
{ key empty$
{ "to sort, need author, editor, or key in " cite$ * warning$
""
}
{ key sortify }
if$
}
{ editor sort.format.names }
if$
}
{ author sort.format.names }
if$
}
FUNCTION {editor.sort}
{ editor empty$
{ key empty$
{ "to sort, need editor or key in " cite$ * warning$
""
}
{ key sortify }
if$
}
{ editor sort.format.names }
if$
}
FUNCTION {presort}
{ calc.label
label sortify
" "
*
type$ "book" =
type$ "inbook" =
or
'author.editor.sort
{ type$ "proceedings" =
'editor.sort
'author.sort
if$
}
if$
#1 entry.max$ substring$
'sort.label :=
sort.label
*
" "
*
title field.or.null
sort.format.title
*
#1 entry.max$ substring$
'sort.key$ :=
}
ITERATE {presort}
SORT
STRINGS { last.label next.extra }
INTEGERS { last.extra.num number.label }
FUNCTION {initialize.extra.label.stuff}
{ #0 int.to.chr$ 'last.label :=
"" 'next.extra :=
#0 'last.extra.num :=
#0 'number.label :=
}
FUNCTION {forward.pass}
{ last.label label =
{ last.extra.num #1 + 'last.extra.num :=
last.extra.num int.to.chr$ 'extra.label :=
}
{ "a" chr.to.int$ 'last.extra.num :=
"" 'extra.label :=
label 'last.label :=
}
if$
number.label #1 + 'number.label :=
}
FUNCTION {reverse.pass}
{ next.extra "b" =
{ "a" 'extra.label := }
'skip$
if$
extra.label 'next.extra :=
extra.label
duplicate$ empty$
'skip$
% { "{\natexlab{" swap$ * "}}" * }
{ "" swap$ * "" * }
if$
'extra.label :=
label extra.label * 'label :=
}
EXECUTE {initialize.extra.label.stuff}
ITERATE {forward.pass}
REVERSE {reverse.pass}
FUNCTION {bib.sort.order}
{ sort.label
" "
*
year field.or.null sortify
*
" "
*
title field.or.null
sort.format.title
*
#1 entry.max$ substring$
'sort.key$ :=
}
ITERATE {bib.sort.order}
SORT
FUNCTION {begin.bib}
{ preamble$ empty$
'skip$
{ preamble$ write$ newline$ }
if$
"\begin{thebibliography}{" number.label int.to.str$ * "}" *
write$ newline$
"\expandafter\ifx\csname natexlab\endcsname\relax\def\natexlab#1{#1}\fi"
write$ newline$
"\providecommand{\url}[1]{\texttt{#1}}"
write$ newline$
"\providecommand{\href}[2]{#2}"
write$ newline$
"\providecommand{\path}[1]{#1}"
write$ newline$
"\providecommand{\DOIprefix}{doi:}"
write$ newline$
"\providecommand{\ArXivprefix}{arXiv:}"
write$ newline$
"\providecommand{\URLprefix}{URL: }"
write$ newline$
"\providecommand{\Pubmedprefix}{pmid:}"
write$ newline$
"\providecommand{\doi}[1]{\href{http://dx.doi.org/#1}{\path{#1}}}"
write$ newline$
"\providecommand{\Pubmed}[1]{\href{pmid:#1}{\path{#1}}}"
write$ newline$
"\providecommand{\bibinfo}[2]{#2}"
write$ newline$
"\ifx\xfnm\relax \def\xfnm[#1]{\unskip,\space#1}\fi"
write$ newline$
}
EXECUTE {begin.bib}
EXECUTE {init.state.consts}
EXECUTE {init.web.variables}
ITERATE {call.type$}
FUNCTION {end.bib}
{ newline$
"\end{thebibliography}" write$ newline$
}
EXECUTE {end.bib}
%% End of customized bst file
%%
%% End of file `elsarticle-harv.bst'.
%%
%% Change log:
%% -----------
%% 22.04.2011
%%
%% 10.08.2012
%% a. doi, url, eprint, pmid added
%% b. Bibtype `webpage' defined
%%
%% 30.08.2012
%% a. collaboration added.
%%
%%
%% Copyright 2007-2024 Elsevier Ltd
%%
%% This file is part of the 'Elsarticle Bundle'.
%% ---------------------------------------------
%%
%% It may be distributed under the conditions of the LaTeX Project Public
%% License, either version 1.3 of this license or (at your option) any
%% later version. The latest version of this license is in
%% http://www.latex-project.org/lppl.txt
%% and version 1.3 or later is part of all distributions of LaTeX
%% version 1999/12/01 or later.
%%
%% The list of all files belonging to the 'Elsarticle Bundle' is
%% given in the file `manifest.txt'.
%%
%% Template article for Elsevier's document class `elsarticle'
%% with harvard style bibliographic references
\documentclass[preprint,12pt,authoryear]{elsarticle}
%% Use the option review to obtain double line spacing
%% \documentclass[authoryear,preprint,review,12pt]{elsarticle}
%% Use the options 1p,twocolumn; 3p; 3p,twocolumn; 5p; or 5p,twocolumn
%% for a journal layout:
%% \documentclass[final,1p,times,authoryear]{elsarticle}
%% \documentclass[final,1p,times,twocolumn,authoryear]{elsarticle}
%% \documentclass[final,3p,times,authoryear]{elsarticle}
%% \documentclass[final,3p,times,twocolumn,authoryear]{elsarticle}
%% \documentclass[final,5p,times,authoryear]{elsarticle}
%% \documentclass[final,5p,times,twocolumn,authoryear]{elsarticle}
%% For including figures, graphicx.sty has been loaded in
%% elsarticle.cls. If you prefer to use the old commands
%% please give \usepackage{epsfig}
%% The amssymb package provides various useful mathematical symbols
\usepackage{amssymb}
%% The amsmath package provides various useful equation environments.
\usepackage{amsmath}
%% The amsthm package provides extended theorem environments
%% \usepackage{amsthm}
%% The lineno packages adds line numbers. Start line numbering with
%% \begin{linenumbers}, end it with \end{linenumbers}. Or switch it on
%% for the whole article with \linenumbers.
%% \usepackage{lineno}
\journal{Nuclear Physics B}
\begin{document}
\begin{frontmatter}
%% Title, authors and addresses
%% use the tnoteref command within \title for footnotes;
%% use the tnotetext command for theassociated footnote;
%% use the fnref command within \author or \affiliation for footnotes;
%% use the fntext command for theassociated footnote;
%% use the corref command within \author for corresponding author footnotes;
%% use the cortext command for theassociated footnote;
%% use the ead command for the email address,
%% and the form \ead[url] for the home page:
%% \title{Title\tnoteref{label1}}
%% \tnotetext[label1]{}
%% \author{Name\corref{cor1}\fnref{label2}}
%% \ead{email address}
%% \ead[url]{home page}
%% \fntext[label2]{}
%% \cortext[cor1]{}
%% \affiliation{organization={},
%% addressline={},
%% city={},
%% postcode={},
%% state={},
%% country={}}
%% \fntext[label3]{}
\title{} %% Article title
%% use optional labels to link authors explicitly to addresses:
%% \author[label1,label2]{}
%% \affiliation[label1]{organization={},
%% addressline={},
%% city={},
%% postcode={},
%% state={},
%% country={}}
%%
%% \affiliation[label2]{organization={},
%% addressline={},
%% city={},
%% postcode={},
%% state={},
%% country={}}
\author{} %% Author name
%% Author affiliation
\affiliation{organization={},%Department and Organization
addressline={},
city={},
postcode={},
state={},
country={}}
%% Abstract
\begin{abstract}
%% Text of abstract
Abstract text.
\end{abstract}
%%Graphical abstract
\begin{graphicalabstract}
%\includegraphics{grabs}
\end{graphicalabstract}
%%Research highlights
\begin{highlights}
\item Research highlight 1
\item Research highlight 2
\end{highlights}
%% Keywords
\begin{keyword}
%% keywords here, in the form: keyword \sep keyword
%% PACS codes here, in the form: \PACS code \sep code
%% MSC codes here, in the form: \MSC code \sep code
%% or \MSC[2008] code \sep code (2000 is the default)
\end{keyword}
\end{frontmatter}
%% Add \usepackage{lineno} before \begin{document} and uncomment
%% following line to enable line numbers
%% \linenumbers
%% main text
%%
%% Use \section commands to start a section
\section{Example Section}
\label{sec1}
%% Labels are used to cross-reference an item using \ref command.
Section text. See Subsection \ref{subsec1}.
%% Use \subsection commands to start a subsection.
\subsection{Example Subsection}
\label{subsec1}
Subsection text.
%% Use \subsubsection, \paragraph, \subparagraph commands to
%% start 3rd, 4th and 5th level sections.
%% Refer following link for more details.
%% https://en.wikibooks.org/wiki/LaTeX/Document_Structure#Sectioning_commands
\subsubsection{Mathematics}
%% Inline mathematics is tagged between $ symbols.
This is an example for the symbol $\alpha$ tagged as inline mathematics.
%% Displayed equations can be tagged using various environments.
%% Single line equations can be tagged using the equation environment.
\begin{equation}
f(x) = (x+a)(x+b)
\end{equation}
%% Unnumbered equations are tagged using starred versions of the environment.
%% amsmath package needs to be loaded for the starred version of equation environment.
\begin{equation*}
f(x) = (x+a)(x+b)
\end{equation*}
%% align or eqnarray environments can be used for multi line equations.
%% & is used to mark alignment points in equations.
%% \\ is used to end a row in a multiline equation.
\begin{align}
f(x) &= (x+a)(x+b) \\
&= x^2 + (a+b)x + ab
\end{align}
\begin{eqnarray}
f(x) &=& (x+a)(x+b) \nonumber\\ %% If equation numbering is not needed for a row use \nonumber.
&=& x^2 + (a+b)x + ab
\end{eqnarray}
%% Unnumbered versions of align and eqnarray
\begin{align*}
f(x) &= (x+a)(x+b) \\
&= x^2 + (a+b)x + ab
\end{align*}
\begin{eqnarray*}
f(x)&=& (x+a)(x+b) \\
&=& x^2 + (a+b)x + ab
\end{eqnarray*}
%% Refer following link for more details.
%% https://en.wikibooks.org/wiki/LaTeX/Mathematics
%% https://en.wikibooks.org/wiki/LaTeX/Advanced_Mathematics
%% Use a table environment to create tables.
%% Refer following link for more details.
%% https://en.wikibooks.org/wiki/LaTeX/Tables
\begin{table}[t]%% placement specifier
%% Use tabular environment to tag the tabular data.
%% https://en.wikibooks.org/wiki/LaTeX/Tables#The_tabular_environment
\centering%% For centre alignment of tabular.
\begin{tabular}{l c r}%% Table column specifiers
%% Tabular cells are separated by &
1 & 2 & 3 \\ %% A tabular row ends with \\
4 & 5 & 6 \\
7 & 8 & 9 \\
\end{tabular}
%% Use \caption command for table caption and label.
\caption{Table Caption}\label{fig1}
\end{table}
%% Use figure environment to create figures
%% Refer following link for more details.
%% https://en.wikibooks.org/wiki/LaTeX/Floats,_Figures_and_Captions
\begin{figure}[t]%% placement specifier
%% Use \includegraphics command to insert graphic files. Place graphics files in
%% working directory.
\centering%% For centre alignment of image.
\includegraphics{example-image-a}
%% Use \caption command for figure caption and label.
\caption{Figure Caption}\label{fig1}
%% https://en.wikibooks.org/wiki/LaTeX/Importing_Graphics#Importing_external_graphics
\end{figure}
%% The Appendices part is started with the command \appendix;
%% appendix sections are then done as normal sections
\appendix
\section{Example Appendix Section}
\label{app1}
Appendix text.
%% For citations use:
%% \citet{<label>} ==> Lamport (1994)
%% \citep{<label>} ==> (Lamport, 1994)
%%
Example citation, See \citet{lamport94}.
%% If you have bib database file and want bibtex to generate the
%% bibitems, please use
%%
%% \bibliographystyle{elsarticle-harv}
%% \bibliography{<your bibdatabase>}
%% else use the following coding to input the bibitems directly in the
%% TeX file.
%% Refer following link for more details about bibliography and citations.
%% https://en.wikibooks.org/wiki/LaTeX/Bibliography_Management
\begin{thebibliography}{00}
%% For authoryear reference style
%% \bibitem[Author(year)]{label}
%% Text of bibliographic item
\bibitem[Lamport(1994)]{lamport94}
Leslie Lamport,
\textit{\LaTeX: a document preparation system},
Addison Wesley, Massachusetts,
2nd edition,
1994.
\end{thebibliography}
\end{document}
\endinput
%%
%% End of file `elsarticle-template-harv.tex'.
% Nature Journal Article Template
% For submission to Nature family journals
% Last updated: 2024
\documentclass[12pt]{article}
% Packages
\usepackage[margin=2.5cm]{geometry}
\usepackage{times}
\usepackage{graphicx}
\usepackage{amsmath}
\usepackage{amssymb}
\usepackage{hyperref}
\usepackage{lineno} % Line numbers for review
\usepackage[super]{natbib} % Superscript citations
% Line numbering (required for submission)
\linenumbers
% Title and Authors
\title{Insert Your Title Here: Concise and Descriptive}
\author{
First Author\textsuperscript{1}, Second Author\textsuperscript{1,2}, Third Author\textsuperscript{2,*}
}
\date{}
\begin{document}
\maketitle
% Affiliations
\noindent
\textsuperscript{1}Department Name, Institution Name, City, State/Province, Postal Code, Country \\
\textsuperscript{2}Second Department/Institution \\
\textsuperscript{*}Correspondence: [email protected]
% Abstract
\begin{abstract}
\noindent
Write a concise abstract of 150-200 words summarizing the main findings, significance, and conclusions of your work. The abstract should be self-contained and understandable without reading the full paper. Focus on what you did, what you found, and why it matters. Avoid jargon and abbreviations where possible.
\end{abstract}
% Main Text
\section*{Introduction}
% 2-3 paragraphs setting the context
Provide background on the research area, establish the importance of the problem, and identify the knowledge gap your work addresses. Nature papers should emphasize broad significance beyond a narrow specialty.
State your main research question or objective clearly.
Briefly preview your approach and key findings.
\section*{Results}
% Primary results section
% Organize by finding, not by experiment
% Reference figures/tables as you describe results
\subsection*{First major finding}
Describe your first key result. Reference Figure~\ref{fig:example} to support your findings.
\begin{figure}[ht]
\centering
% Include your figure here
% \includegraphics[width=0.7\textwidth]{figure1.pdf}
\caption{{\bf Figure title in bold.} Detailed figure caption explaining what is shown, experimental conditions, sample sizes (n), statistical tests, and significance levels. Panels should be labeled (a), (b), etc. if multiple panels are present.}
\label{fig:example}
\end{figure}
\subsection*{Second major finding}
Describe your second key result objectively, without interpretation.
\subsection*{Third major finding}
Describe additional results as needed.
\section*{Discussion}
% Interpret results, compare to literature, acknowledge limitations
\subsection*{Main findings and interpretation}
Summarize your key findings and explain their significance. How do they advance our understanding?
\subsection*{Comparison to previous work}
Compare and contrast your results with existing literature\cite{example2023}.
\subsection*{Implications}
Discuss the broader implications of your work for the field and beyond.
\subsection*{Limitations and future directions}
Honestly acknowledge limitations and suggest future research directions.
\section*{Conclusions}
Provide a concise conclusion summarizing the main take-home messages of your work.
\section*{Methods}
% Detailed methods allowing reproducibility
% Can be placed after main text in Nature
\subsection*{Experimental design}
Describe overall experimental design, including controls.
\subsection*{Sample preparation}
Detail procedures for sample collection, preparation, and handling.
\subsection*{Data collection}
Describe instrumentation, measurement procedures, and data collection protocols.
\subsection*{Data analysis}
Explain analytical methods, statistical tests, and software used. State sample sizes, replication, and significance thresholds.
\subsection*{Ethical approval}
Include relevant ethical approval statements (human subjects, animal use, biosafety).
\section*{Data availability}
State where data supporting the findings can be accessed (repository, supplementary files, available on request).
\section*{Code availability}
If applicable, provide information on code availability (GitHub, Zenodo, etc.).
\section*{Acknowledgements}
Acknowledge funding sources, technical assistance, and other contributions. List grant numbers.
\section*{Author contributions}
Describe contributions of each author using CRediT taxonomy or similar (conceptualization, methodology, investigation, writing, etc.).
\section*{Competing interests}
Declare any financial or non-financial competing interests. If none, state "The authors declare no competing interests."
% References
\bibliographystyle{naturemag} % Nature bibliography style
\bibliography{references} % Your .bib file
% Alternatively, manually format references:
\begin{thebibliography}{99}
\bibitem{example2023}
Smith, J. D., Jones, M. L. \& Williams, K. R. Groundbreaking discovery in the field. \textit{Nature} \textbf{600}, 123--130 (2023).
\bibitem{author2022}
Author, A. A. \& Coauthor, B. B. Another important paper. \textit{Nat. Methods} \textbf{19}, 456--
460 (2022).
% Add more references as needed
\end{thebibliography}
% Figure Legends (if not included with figures)
\section*{Figure Legends}
\textbf{Figure 1 | Figure title.} Comprehensive figure legend describing all panels, experimental conditions, sample sizes, and statistical analyses.
\textbf{Figure 2 | Second figure title.} Another detailed legend.
% Extended Data Figures (optional - supplementary figures)
\section*{Extended Data}
\textbf{Extended Data Figure 1 | Supplementary data title.} Description of supplementary figure supporting main findings.
\end{document}
% Notes for Authors:
% 1. Nature articles are typically ~3,000 words excluding Methods, References, Figure Legends
% 2. Use superscript numbered citations (1, 2, 3)
% 3. Figures should be high resolution (300+ dpi for photos, 1000 dpi for line art)
% 4. Submit figures as separate files (TIFF, EPS, or PDF)
% 5. Double-space the manuscript for review
% 6. Include line numbers using \linenumbers
% 7. Follow Nature's specific author guidelines for your target journal
% 8. Methods section can be quite detailed and placed after main text
% 9. Check word limits and specific requirements for your Nature family journal
Related skills
How it compares
Pick venue-templates over generic scientific-writing skills when the target journal is Cell Press and Summary, Highlights, and eTOC length rules must be followed exactly.
FAQ
What sections does venue-templates generate for Cell Press?
venue-templates generates three Cell Press submission elements: a Summary abstract capped at 150 words, a Highlights bullet list, and a concise eTOC blurb for the journal table of contents.
What is the word limit for a Cell Press Summary in venue-templates?
venue-templates enforces a 150-word maximum on Cell Press Summary abstracts, matching the venue's author guidelines demonstrated in the bundled senescence and aging example.
Is Venue Templates safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.