NSF award 2546694 · Northwestern University at Chicago

CS2: Automatically Extracting High-Level Specifications from Large Scientific Codebases to Enhance Understandability and Correctness

Final report due

28 August 2030

in 1,410 days · The award ends on 30 April 2030.

GrantClerk is a private service. We are not NSF or any government agency.

Dates this award owes

NSF emails you about this too.

Decide about an extension31 Dec 2029in 1170 days
award ending 2030-04-30 · Research.gov
This one is ours, not NSF’s.
Extension request16 Mar 2030in 1245 days
award ending 2030-04-30 · Research.gov
PAPPG 24-1: “at least 45 days prior to the end date”
No-cost extension notice20 Apr 2030in 1280 days
award ending 2030-04-30 · Research.gov
PAPPG 24-1: “at least ten calendar days prior to the end date”
Final report due28 Aug 2030in 1410 days
award ending 2030-04-30 · Research.gov
PAPPG 24-1: “no later than 120-days following the end date of the award”
Project outcomes report due28 Aug 2030in 1410 days
award ending 2030-04-30 · Research.gov
PAPPG 24-1: “no later than 120 days following the end date”
Award is closed out28 Aug 2030in 1410 days
award ending 2030-04-30 · Research.gov
PAPPG 24-1: “financially closed out 120 days after their expiration date”

Annual report dates come from the budget period on your award notice. That date is not public, so it is not shown here.

How we got this date

NSF lists this award's end date as 30 April 2030.
NSF rules say the final report is due no later than 120 days after that.
So the final report is due by 28 August 2030.

Read the rule on Research.gov

Get a note before each report date

Add this award to your desk. We email you before each date and keep the dates in one place.

Renews each year until you cancel. Cancel any time from your account.

Already a member? Sign in

Award card

Award number: 2546694
Period of support: 1 May 2026 – 30 Apr 2030
Amount: $200,000
Awardee: Northwestern University at Chicago, Evanston, IL
Program: Correct SciComp Systems (CS2)
Directorate: CSE

Abstract

Large scientific codebases cost millions of dollars to develop and support the work of countless computational scientists worldwide, so verifying their correctness is just as crucial as ensuring the proper functioning of expensive physical equipment in a "traditional" laboratory setting. However, unlike physical equipment, these codebases are built incrementally over decades, often by hundreds or thousands of…

Is this right?

We copy this from the public NSF award record. Your award notice and NSF always win. If a date looks wrong, check Research.gov.