Replied: Mon, 10 Feb 2003 09:17:11 -0500 Replied: "Yana Teterina" Return-Path: yteterin@indiana.edu Delivery-Date: Mon Feb 10 09:15:41 2003 Return-Path: Received: from plounts.uits.indiana.edu (plounts.uits.indiana.edu [129.79.1.73]) by grids.ucs.indiana.edu (8.10.2+Sun/8.10.2) with ESMTP id h1AEFfN29001 for ; Mon, 10 Feb 2003 09:15:41 -0500 (EST) Received: from logchain.uits.indiana.edu (logchain.uits.indiana.edu [129.79.1.77]) by plounts.uits.indiana.edu (8.12.1/8.12.1/IUPO) with ESMTP id h1AEIN9p016171 for ; Mon, 10 Feb 2003 09:18:23 -0500 (EST) Received: from DC4WJV11 (d-158-122.dhcp-129-79.indiana.edu [129.79.158.122]) by logchain.uits.indiana.edu (8.12.1/8.12.1/IUPO) with ESMTP id h1AEIOHN007429 for ; Mon, 10 Feb 2003 09:18:24 -0500 (EST) From: "Yana Teterina" To: Subject: RE: Proposal 19 Date: Mon, 10 Feb 2003 09:18:24 -0500 Message-ID: <000d01c2d10f$45e0cbf0$7a9e4f81@ads.iu.edu> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C2D0E5.5D0AC3F0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <3E47B343.8020100@grids.ucs.indiana.edu> Content-Length: 12779 This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C2D0E5.5D0AC3F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit The summary cannot exceed 1 page - description below. It seems okay, but could you possibly check to make sure it covers all necessary areas - methods to be employed, etc. We could change the spacing - but I am not sure it will save us any space - I'll check on that. Yana The proposal must contain a summary of the proposed activity suitable for publication, not more than one page in length. It should not be an abstract of the proposal, but rather a self-contained description of the activity that would result if the proposal were funded. The summary should be written in the third person and include a statement of objectives and methods to be employed. It must clearly address in separate statements (within the one-page summary): (1) the intellectual merit of the proposed activity; and (2) the broader impacts resulting from the proposed activity. (See Chapter III for further descriptive information on the NSF merit review criteria.) It should be informative to other persons working in the same or related fields and, insofar as possible, understandable to a scientifically or technically literate lay reader. -----Original Message----- From: Geoffrey Fox [mailto:gcf@grids.ucs.indiana.edu] Sent: Monday, February 10, 2003 9:12 AM To: Yana Teterina Subject: Re: Proposal 19 Maybe we can tweak line spacing on 10 pt Could you check size of "summary" That has some limit I think Thanks Yana Teterina wrote: Dear Dr. Fox, Attached is the latest version of this proposal. We need to update the heading. I've checked on the NSF format requirements and they state that font density cannot exceed 15 characters per 2.5cm - we are okay on that; in addition no more that 6 lines of text must be within a vertical space of 2.5cm - there is a problem with that - we have almost 7 lines per 2.5cm. I guess we can increase text size to 10.5. If we do Arial 10 - we get 16 characters per 2.5cm - again a problem. Thank you for your help. Yana Yana Teterina Administrative Assistant Biocomplexity Institute Department of Physics Indiana University Swain Hall West 157 812-855-1304 812-855-5533 fax -- : : Geoffrey Fox gcf@indiana.edu FAX 8128567972 : Phones Cell 315-254-6387 Home 8123239196 Lab 8128567977 CS 8128553788 ------=_NextPart_000_000E_01C2D0E5.5D0AC3F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The summary cannot exceed 1 page = – description below.  It seems okay, but could you possibly check to = make sure it covers all necessary areas – methods to be employed, = etc.

 

  We could change the spacing = – but I am not sure it will save us any space – I’ll check on that.  Yana

 

The proposal must contain a = summary of the proposed activity suitable for publication, not more than one = page

in length. It should not be = an abstract of the proposal, but rather a self-contained description of the activity that

would result if the = proposal were funded. The summary should be written in the third person and include = a

statement of objectives and = methods to be employed. It must clearly address in separate statements (within = the

one-page summary): (1) the intellectual merit of the proposed activity; and (2) the broader impacts resulting from

the proposed activity. (See = Chapter III for further descriptive information on the NSF merit review = criteria.) It

should be informative to = other persons working in the same or related fields and, insofar as = possible,

understandable to a = scientifically or technically literate lay reader.

 

 

-----Original = Message-----
From: Geoffrey Fox [mailto:gcf@grids.ucs.indiana.edu]
Sent: Monday, February = 10, 2003 9:12 AM
To: Yana Teterina
Subject: Re: Proposal = 19

 

Maybe we can tweak line spacing on 10 pt

Could you  check size of "summary"
That has some limit I think
Thanks

Yana Teterina wrote:

Dear Dr. = Fox,

 

Attached is the latest = version of this proposal.  We need to update the heading.  =

 

I’ve checked on the = NSF format requirements and they state that font density cannot exceed 15 = characters per 2.5cm – we are okay on that; in addition no more that 6 lines of = text must be within a vertical space of 2.5cm – there is a problem with = that – we have almost 7 lines per 2.5cm.  I guess we can increase = text size to 10.5.  If we do Arial 10 – we get 16 characters per = 2.5cm – again a problem.

 

Thank you for your = help.  Yana

 

Yana = Teterina

Administrative = Assistant

Biocomplexity = Institute

Department of = Physics

Indiana University =

Swain Hall West = 157

812-855-1304

812-855-5533 = fax

 



-- 
:
: Geoffrey Fox  gcf@indiana.edu FAX =
8128567972
: Phones Cell 315-254-6387 Home 8123239196 =
Lab 8128567977 CS 8128553788

 

------=_NextPart_000_000E_01C2D0E5.5D0AC3F0--