April 2011 - Esc-team - mailman3.cels.anl.gov

next steps
by Pete Beckman 14 Apr '11

14 Apr '11

Ok, Things are looking quite good indeed for our planning documents. The plan looks nice and it is very comprehensive. Thanks in advance to all the folks who read, corrected, rewrote, and then started all over again. At this point we have all the material together and are just updating figures, graphs, and correcting mistakes. Later today at ANL we will read through the entire plan, end to end, all 192 pages of it, and correct things as we go. We hope to finish up by the evening. The plan is due at high noon, eastern time, on Friday. So that means we will send mail a few minutes before 11:00 central on Friday, and then retire to food and drink. I encourage everyone to follow suit in their timezone. What's next? Well, since the DOE now has a budget, they are quickly deciding how to fund co-design centers, and other things. You may have heard they expect May 23 through 27 to be the site visit times for the co-design centers. I don't know yet what they plan for us, but after Bill Harrod looks through the plan, there will probably be some phone conversations. We hope to have a review at the end of May or beginning of June, so we can start by July 1st. At this point, if you are so inclined, download the PDFs and read them, sending mail to this entire list if you find bugs. On Friday, I'll send out confirmation that the plan was submitted, and then wait for instructions from Bill Harrod. -Pete

1 0

Getting Close
by Pete Beckman 13 Apr '11

13 Apr '11

The materials are getting very close to being ready. Thanks to everyone for their help. Hard to believe our first meeting was Feb 22, 2010 at O'hare. We have come a long way. I've checked in the draft PDF versions into ./esc/review/TotalPackageOutput. The sections still undergoing work.... Narrative: * Intro being tweaked * Last two sections being worked Everything else ready to be proofed. QA: Terri is doing some editing, should be ready for proof reading later today. SoftwareStack: Pretty much done, just double checking things. Ready for proof reading GapAnalysis: Pretty much done, going to double check Kamil's figures, should be ready for proof reading later today The Project management PDF that the PM holds is being edited by Ray and Jason, and will be PDFed shortly and added into the plan. If you want to see what folks have been working on, look through the ToDo.txt list (and previous versions) to see all the goodies. We are up to SVN revision 1010. We even had time to add an easter egg bonus... -Pete

1 0

Budget Pages
by Pete Beckman 12 Apr '11

12 Apr '11

I've been asked by several folks if we need to prepare budget pages. I'm going with no. I think the plan will be reviewed, and if they can spend money in 2011, they will update the current FWPs we have, etc. I don't think we should go to all the trouble to have budget pages created when DOE has to hack on budgets now anyway. The good news, is that the word we got from our DC guy is that in the latest budget deal, only about 2% was shaved off the 2010 budget for Office of Science. Of course, that is the 2010 level, not the increased 2011 numbers. Furthermore, the 2% could get unequally distributed across the Office of Science departments, of which ASCR is only one. However, compared to other areas of the budget, we *seem* (key word) to have done pretty well, since the White House really believed in innovation, research, and energy. -Pete

2 2

Standard Team Names
by Pete Beckman 12 Apr '11

12 Apr '11

We are trying to standardize some things in the documents. The team names for the technical work (in this order) are: Programming Models (PM) Application Programming Tools (TLS) Operating and Run-time Systems (ORS) Linear Algebra and Math Software (LAMS) Data Management and Analysis (DMA) I'll try and correct a bunch tonight, but if you see things in the morning that are not right, please fix them. -Pete

6 9

Current overview, pages 1-18
by Pete Beckman 12 Apr '11

12 Apr '11

Thanks to many people's hard work, the first 1/2 of the overview narrative is mostly complete. The pages are attached, so you can familiarize yourself with the current plan. We have about 5 days left, so please read through all the materials currently drafted and look for ways to improve the material. If there is a small fix/correction to make, just make it. If it is more substantial, please discuss it via Reply All. -Pete

2 6

New Version
by Pete Beckman 11 Apr '11

11 Apr '11

We are making good progress, but with only about 4 days left, we will have to speed up a bit to hit our deadline. Status below: 2_Narrative: Paul completed his introduction, I made a pass all the way through section 3, but failed past that. I believe that the first 17 pages are ready to be first-pass edited. John MC passed along his editing of 2_Narrative, and I will pass them along to the technical editors. We need a volunteer to write the Risk section. 5_SoftwareStack: Improvements were made by several folks this weekend. It now needs a consistency pass and tech editing. What's missing or obtuse? What does not match or has poor grammar? 7_SoftwareAnalysis: Good progress was made, but intro may benefit from a couple references (like what Paul put in the repo for the intro.tex) and pictures. Also, it could use a good read from front to back to see how to make it stronger. It should be ready for technical editors then. More details later. -Pete

2 1

Current Editing Status:
by Pete Beckman 05 Apr '11

05 Apr '11

Current Activities: ---- Pete: Edit qa-support.tex Charlie: Editing mgmt-plan, etc. Terry: Adding tech-series ideas to outreach.tex Kamil, Pavan, Rob, and Kumar: Working on 5_SoftwareStack Paul: Intro and framing Ray: 4_SoftwareDevl, but waiting for pete to finish qa-support.tex Pavan, Hammond: 7_SoftwareAnalysis: editing intro and top-down to match SoftareStack Ready for Tech Editing: * Bios * Consistency of headers, footers, page numbering, index, etc Stuff to add to ThePlan: * Metrics for Success Some items we should complete (even a couple days after we submit) * Guideline for review (charge letter, scoresheet) * Suggested Reviewers ---- Everyone editing should be looking for places to add % ACTIVITY and % MILESTONE Are there places you can help? -Pete

2 1

Ok, update your SVN
by Pete Beckman 04 Apr '11

04 Apr '11

Some simple changes and improvements were made to the repo. Everyone should do an "svn update" immediately. I'll send out status and to-do items later. Section 5 is looking very nice. We still have a long way to go with 2_Narrative and the activities / milestones. Specific requests for help will come. Even if you don't have the full latex set up, you can look in ./esc/review/TotalPackageOutput for current copies of all the PDFs. ESC_Narrative.pdf is still sketchy, but the others are coming along. At this point, please read 5_SoftwareStack, and see if there are mistakes or places where we don't match what we said we would do in the Gap Analysis. I think by Wednesday, we should be able to give 5_SoftwareStack to the editors and then focus all our attention on the other pieces. So, we need everyone to help with 5_SoftwareStack. What's wrong? What's not tied back to related components? If you don't feel comfortable fixing things directly, send issues to this email list. -Pete

1 0

Editors this evening?
by Pete Beckman 03 Apr '11

03 Apr '11

Anyone currently editing sections? I was going to go through and do a little inventory of where we stand, and wanted to make sure I don't collide. -Pete

1 0

Plan ToDo Items
by Pete Beckman 02 Apr '11

02 Apr '11

Please see work items below: * Everyone: When editing any text, if you find something that could be an excellent "activity" or "milestone", and rolled up, please mark it in the LaTeX with a comment. Use this format: % MILESTONE: <description> or % ACTIVITY: <description> This will help us comb through the document and pull out things that can be put on a schedule / plan. Examples: In the section of the GapAnalysis where we are talking about working with the applications and every 6 months updating the Inventory and GapAnalysis that drives the software plan, you might comment: % ACTIVITY: Workshop with all co-design centers to update GapAnalysis and Technical R&D plan Similarly, in some other section, you might have: % MILESTONE: Completed documentation provided to the vendor Yes, the difference between a milestone and activity can be gray, but the idea is that a milestone is something a person holding a clipboard can check off, and mark "completed". An activity might be something that takes weeks or months, and in some (but not all cases) result in something that looks like a milestone that can be checked off. * Catlett, Messina, Beckman: Working on first three sections of Narrative. Integrating Snir's and Kramer's comments * Balaji, Thakur: Working on smoothing and leveling, including intro, of 5_SoftwareStack * Quinn, Bair: Working on 4_SoftwareDevl. Please let me know if there are any images to be integrated * Hammond: Working on 7_SoftwareAnalysis. Writing intro, describing process, linking back to software plan, etc. * Iskra, Balaji: Cover sheets and running header on ESC_BioSketches.pdf, Fix title page for Narrative to be right title, and running header, some way to make a master cover document that describes what's in the entire bundle, gives their document names, page counts, PDF filenames, etc, along with instructions for how to read the whole package. * Barry Smith: Barry is editing the mathlibs plan, making some improvements * Budd & Northrop: They are working on project mgmt pieces When you are done with a section, please send email, passing the baton, so I can push it along to the next editor. -Pete

1 0