 |
 |
How about more like the table you have for stdhep events, but for slic/readout/reco as well. Also, more! On Jun 13, 2013, at 2:11 PM, Sho Uemura <[log in to unmask]> wrote: > Is this what you want? > > https://confluence.slac.stanford.edu/display/hpsg/Finding+Data > > Not everything is actually processed (e.g. the only ap+beam+tri sample for > which readout has been done is 2.2 GeV/75 MeV), but that can be done in a > day or two (the scripts are already written to run the batch jobs). > > On Thu, 13 Jun 2013, Graham, Mathew Thomas wrote: > >> >> For folks looking to do data analysis primarily with the tracker, this all seems kind of late. But I know we have some samples generated & (processed?) already. Do you have a summary of the samples/numbers of events we have? >> >> On Jun 13, 2013, at 1:34 PM, Sho Uemura <[log in to unmask]> wrote >> >>> Here's a first hack at a schedule. It's very rough, but it'll serve as a >>> starting point. >>> >>> Software subgroups should make sure I haven't missed any tasks. >>> >>> >>> >>> The current milestones: >>> >>> Sim production starts September 20. >>> >>> We are ready to reconstruct data November 29. >>> >>> We are ready to run February 7 (but there will be tasks added that will >>> definitely push this back; see below). >>> >>> >>> >>> Tasks, schedule: >>> http://www.slac.stanford.edu/~meeg/HPS_software_schedule.png >>> >>> People: >>> http://www.slac.stanford.edu/~meeg/HPS_software_resources.png >>> >>> Notes on how this is set up: >>> >>> * Software people have other obligations, so only some fraction of their >>> time is going to be spent on software. I'm representing this using the >>> "Base Calendar" column. Tell me if you think I've overrepresented your >>> availability. >>> >>> * Task durations are estimates based on 100% time, so a task with 1 week >>> duration assigned to someone with 50% time will take 2 weeks on the >>> schedule. >>> >>> * ECal people (Raphael, Andrea, possible grad students/postdocs) are >>> lumped together as a single "person" in lieu of actually assigning tasks. >>> >>> * Analysis tasks aren't listed yet, but should be. >>> >>> * Some tasks with external dependencies (integration with DAQ, testing >>> monitoring at JLab, etc.) aren't listed yet, but should be. >>> >>> Every task is assigned to someone. If I've assigned tasks to you, you >>> should tell me whether the duration is plausible and you're the right >>> person to do it. >>> >>> >>> Thanks in advance for feedback. >>> >>> ######################################################################## >>> Use REPLY-ALL to reply to list >>> >>> To unsubscribe from the HPS-SOFTWARE list, click the following link: >>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1 >> >> >> ######################################################################## >> Use REPLY-ALL to reply to list >> >> To unsubscribe from the HPS-SOFTWARE list, click the following link: >> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1 >> ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the HPS-SOFTWARE list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1