Meeting Authorization

Meeting Information

  • Project No. and Title: NC1034 - Impact Analyses and Decision Strategies for Agricultural Research
  • Dates: 03/30/2023 to 03/31/2023
  • Contacts: [Gregory Graff]

This authorizes the annual meeting: .
The meeting will be held on 03/30/2023 at Arlington, VA. :

Admin Advisor: Tala Awada (tawada2@unl.edu)

Additional Info

note: The Holiday Inn Arlington at Ballston is close to the meeting place<br /> <br /> Dear NC1034 colleagues,<br /> An exciting opportunity has come together for NC1034 to meet on March 30-31 2023 in the Washington DC area in conjunction with a workshop on "Agricultural Productivity Growth: Measurement, Drivers, and Climatic Effects" March 29-30, organized by USDA-ERS, Farm Foundation, and the GAP Initiative of the College of Agriculture and Life Sciences Global at Virginia Tech. The workshop will be held at the Virginia Tech Executive Briefing Center (EBC) in Arlington VA. Several members of NC1034 are already participating in the workshop, and more detailled information is posted below.<br /> This is a multi-part opportunity exclusive for NC1034 members: <br /> • attend Agricultural Productivity Growth workshop sessions<br /> • NC1034 business meeting followed by NC1034 social hour and dinner evening of Thurs March 30<br /> • NC1034 annual research conference morning of Fri March 31, separate from the Agricultural Productivity Growth workshop.<br /> Of course, you may opt for any subset of these options that work for your schedule. Details regarding registration and accomodations will follow shortly.<br /> NC1034 2023 ANNUAL MEETING CALL FOR PAPERS:<br /> Due to the tight timeline please email abstracts (250 words) or session proposals (750 words, for three or more related papers) by Friday February 16, 2022 to:<br /> Gregory Graff, Professor, Agricultural and Resource Economics, Colorado State
Log Out ?

Are you sure you want to log out?

Press No if you want to continue work. Press Yes to logout current user.

Report a Bug
Report a Bug

Describe your bug clearly, including the steps you used to create it.