Hi HERAtics (especially Gianni, Andrei, Adrian, Jonnie, Dave, and Aaron), Aaron, Adrian, Dave and I met this afternoon and we think the best way forward is is to break the proposal into larger sections and then assign individual collaborators *to make them coherent and consistent, to edit down where appropriate, and to point out (and hopefully fill in) missing arguments or topics.*
Here are the assignments. *Please make your additions and revisions and push them to the github by the Wednesday data-con (9:30am pacific) *so we can continue discussing then: *Me:* - I'll be editing what's currently 1.1 and 1.2 into a short, coherent intro. *Gianni: * - 1.3. Broader Science (that number might change) and 2.5. Broader Scientific Impacts Enabled by HERA. In particular feel free to pull most of the material from 1.3 into 2.5 and then edit 2.5 as appropriate. The bulleted paragraphs in 1.3 should be approximately 1 sentence each. The focus in both 1.3 and 2.5 needs to be on the general philosophy of "HERA is a platform" for future observations and other enabled by new hardware and new analysis efforts. Tie in the public data products too. - Section 6. Aaron wants to reframe this as "Data Products and Community Support." There should be less detail about how we're going to produce the data products (which will come earlier in the proposal) and more detail about exactly what kind of products we will provide, both science results and data products other astronomers might use in their research. The goal here is to sell HERA to outside scientists and get them excited about the possibility of getting involved by using our public data products. *Andrei:* - Sections 2.1 and 2.2. Also, feel free to draw from section 1.2, since I'm trying to cut it down. *Adrian:* - Sections 2.3 and 2.4 *Jonnie:* - Sections 3, 3.1, and 3.2. Additionally, we need you to edit and condense the foregrounds material from sections 4.1, and 4.1.1 (working with Aaron) and bring it into section 3.2 *Dave:* - Sections 3.3, 3.4, and Section 5. *Aaron:* - The rest of Section 4, including the parts of 4.1.1 that Jonnie doesn't move into 3.2. - In particular, we decided that Section 4 needs a new intro with a summary of design principles, motivated by the lessons we've learned about foregrounds and systematics, and how those flow into design requirements. Section 4 needs a discussion of each piece of the system, it's specifications, and a discussion of how well we can demonstrate that we've met those specs. Everyone else can take a break for now. We'll need you later. (We'll wait on Sections 7 and 8 for now.) Thanks so much! Have a great weekend. -Josh
