Difference between revisions of "May 2005 GMOD Meeting"
m |
m (→Presentations) |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 5: | Line 5: | ||
May 16-17, 2005 | May 16-17, 2005 | ||
SRI, Menlo Park, CA | SRI, Menlo Park, CA | ||
+ | |||
+ | ==Presentations== | ||
+ | |||
+ | * [[Media:Apollo.ppt|Apollo.ppt]] | ||
+ | * [[Media:Cain-050516.ppt|Cain-050516.ppt]] - GMOD business and setting up [[ParameciumDB]] | ||
+ | * [[Media:Cmap-050516.pdf|Cmap-050516.pdf]] | ||
+ | * [[Media:Das.ppt|Das.ppt]] | ||
+ | * [[Media:Day-050517.ppt|Day-050517.ppt]] | ||
+ | * [[Media:Faga_050517.pdf|Faga_050517.pdf]] | ||
+ | * [[Media:Gbrowse-050516.ppt|Gbrowse-050516.ppt]] | ||
+ | * [[Media:Just-050516.ppt|Just-050516.ppt]] | ||
+ | * [[Media:Kasprzyk-050516.ppt|Kasprzyk-050516.ppt]] - [[BioMart]] and [[Chado]] | ||
+ | * [[Media:Karp-050516.ppt|Karp-050516.ppt]] | ||
+ | * [[Media:Mungall-050516.ppt|Mungall-050516.ppt]] | ||
+ | * [[Media:Oconnor-050516.ppt|Oconnor-050516.ppt]] | ||
+ | * [[Media:Sgd-050516.ppt|Sgd-050516.ppt]] | ||
+ | * [[Media:Smutniak-050516.ppt|Smutniak-050516.ppt]] | ||
+ | * [[Media:What_next.ppt|What_next.ppt]] | ||
+ | * [[Media:Zhang-050517.ppt|Zhang-050517.ppt]] | ||
==Agenda== | ==Agenda== | ||
Line 82: | Line 101: | ||
Scott Cain</td> | Scott Cain</td> | ||
</tr> | </tr> | ||
− | |||
− | |||
</table> | </table> | ||
Line 95: | Line 112: | ||
Peili Zhang</td> | Peili Zhang</td> | ||
</tr> | </tr> | ||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">9:45</td> | <td valign="top" width="15%">9:45</td> | ||
Line 101: | Line 117: | ||
Samuel Angiuoli</td> | Samuel Angiuoli</td> | ||
</tr> | </tr> | ||
− | |||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">10:30</td> | <td valign="top" width="15%">10:30</td> | ||
Line 108: | Line 122: | ||
</td> | </td> | ||
</tr> | </tr> | ||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">10:45</td> | <td valign="top" width="15%">10:45</td> | ||
− | <td width="85%">apollo.ppt | + | <td width="85%">apollo.ppt Apollo Update<br> |
Nomi Harris and Mark Gibson</td> | Nomi Harris and Mark Gibson</td> | ||
</tr> | </tr> | ||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">10:45</td> | <td valign="top" width="15%">10:45</td> | ||
Line 120: | Line 132: | ||
Frank Smutniak</td> | Frank Smutniak</td> | ||
</tr> | </tr> | ||
− | |||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">12:00</td> | <td valign="top" width="15%">12:00</td> | ||
Line 127: | Line 137: | ||
</td> | </td> | ||
</tr> | </tr> | ||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">1:15</td> | <td valign="top" width="15%">1:15</td> | ||
Line 133: | Line 142: | ||
Todd Harris</td> | Todd Harris</td> | ||
</tr> | </tr> | ||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">2:15</td> | <td valign="top" width="15%">2:15</td> | ||
Line 139: | Line 147: | ||
Ben Faga</td> | Ben Faga</td> | ||
</tr> | </tr> | ||
− | |||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">2:30</td> | <td valign="top" width="15%">2:30</td> | ||
Line 146: | Line 152: | ||
</td> | </td> | ||
</tr> | </tr> | ||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">3:00</td> | <td valign="top" width="15%">3:00</td> | ||
Line 152: | Line 157: | ||
Lincoln Stein</td> | Lincoln Stein</td> | ||
</tr> | </tr> | ||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">3:45</td> | <td valign="top" width="15%">3:45</td> | ||
Line 158: | Line 162: | ||
Allen Day</td> | Allen Day</td> | ||
</tr> | </tr> | ||
− | |||
<tr> | <tr> | ||
<td valign="top" width="15%">4:30</td> | <td valign="top" width="15%">4:30</td> | ||
Line 164: | Line 167: | ||
Lincoln Stein and Scott Cain</td> | Lincoln Stein and Scott Cain</td> | ||
</tr> | </tr> | ||
+ | </table> | ||
==GMOD Architecture Working Group== | ==GMOD Architecture Working Group== | ||
Line 169: | Line 173: | ||
===Goal=== | ===Goal=== | ||
− | The Architecture Working Group will make recommendations to the GMOD consortium on any cross-project policies which can lead to a more cohesive software project. | + | The Architecture Working Group will make recommendations to the GMOD |
+ | consortium on any cross-project policies which can lead to a more | ||
+ | cohesive software project. The group will take into consideration: | ||
* Interoperability with other GMOD components | * Interoperability with other GMOD components | ||
* Performance | * Performance | ||
− | * Platform independence | + | * Platform independence |
− | GMOD will announce the recommendations and provide a repository for the recommendations on the website. Future developers will be pointed to these recommendations. | + | GMOD will announce the recommendations and provide a repository for |
+ | the recommendations on the website. Future developers will be pointed | ||
+ | to these recommendations. | ||
===Workflow=== | ===Workflow=== | ||
+ | The group will discuss which recommendations are needed and decide on | ||
+ | an issue on which to make a recommendation. One or two | ||
+ | recommendations at a time will be chosen to work on. The timeline | ||
+ | will obviously be very different for each recommendation – some will | ||
+ | be short with near consensus early on and will just be a matter of | ||
+ | formalizing. Others will be more contentious and require more work to | ||
+ | gain consensus on. | ||
− | + | ====Timeline of a recommendation==== | |
− | Timeline of a recommendation | + | |
− | + | ||
− | Two weeks: | + | Two to three weeks: Discussion of the current problem, specify |
+ | exactly what the proposals should address. Any use cases are | ||
+ | developed at this time. At the end of this time a request for | ||
+ | proposals will go out. | ||
− | + | Two weeks: Time for members of the working group to generate one or | |
+ | more proposed solutions to a problem. These solutions are formally | ||
+ | written and submitted to the group. | ||
+ | |||
+ | Three weeks: Discuss and iterate on one or more proposals, come to a | ||
+ | consensus. At the end of this time, one person will be delegated to | ||
+ | 'close' the proposal by formalizing any suggested modifications to the | ||
+ | recommendation. After one last review the proposal is formally | ||
+ | submitted to GMOD. | ||
===Communication=== | ===Communication=== | ||
Communication will take place primarily over email on the group list. One conference call per month can be expected and we will work out a time among the group that will be our standard time for a conference call. We will try to limit conference calls to one hour per month per active recommendation. | Communication will take place primarily over email on the group list. One conference call per month can be expected and we will work out a time among the group that will be our standard time for a conference call. We will try to limit conference calls to one hour per month per active recommendation. | ||
− | |||
[[Category:Meetings]] | [[Category:Meetings]] |
Latest revision as of 17:07, 14 March 2008
Generic Model Organism Database Construction Set
Contents
Meeting 6
May 16-17, 2005 SRI, Menlo Park, CA
Presentations
- Apollo.ppt
- Cain-050516.ppt - GMOD business and setting up ParameciumDB
- Cmap-050516.pdf
- Das.ppt
- Day-050517.ppt
- Faga_050517.pdf
- Gbrowse-050516.ppt
- Just-050516.ppt
- Kasprzyk-050516.ppt - BioMart and Chado
- Karp-050516.ppt
- Mungall-050516.ppt
- Oconnor-050516.ppt
- Sgd-050516.ppt
- Smutniak-050516.ppt
- What_next.ppt
- Zhang-050517.ppt
Agenda
9:00am | Introductions Scott Cain, GMOD coordinator |
9:15 | Project updates (short!)
|
10:00 | Break |
10:15 | cain-050516.ppt My trip to France (setting up ParameciumDB) Scott Cain |
10:45 | kenny-050516.ppt Textpresso update Eimear Kenney |
11:15 | karp-050516.ppt Pathway Tools Peter Karp |
12:00 | Lunch |
1:15 | just-050516.ppt Porting CHADO and GMOD Tools to Oracle and Integration with dictyBase Eric Just |
2:00 | mungall-050516.ppt chado design, XSL, XML, XORT Pinglei Zhou and Chris Mungall |
2:45 | Break |
3:00 | kasprzyk-050516.ppt BioMart and chado Arek Kasprzyk |
3:45 | oconnor-050516.ppt Turnkey Brian O'Connor |
4:30 | Wrap up for the day--items to discuss over dinner Scott Cain |
Tuesday, May 17
9:00 | zhang-050517.ppt Comparative genome annotation of D. pseudoobscura and its
implementation in chado |
9:45 | sybil for comparative genomics Samuel Angiuoli |
10:30 | Break |
10:45 | apollo.ppt Apollo Update Nomi Harris and Mark Gibson |
10:45 | smutniak-050516.ppt Transposon Insertions and Transposon Constructs editor Frank Smutniak |
12:00 | Lunch |
1:15 | harris-050517.ppt Bio::GMOD and standard URLs Todd Harris |
2:15 | faga_050517.pdf Interaction Browsers (a presentation prepared at the meeting because the topic came up) Ben Faga |
2:30 | Break |
3:00 | das.ppt Das2 Lincoln Stein |
3:45 | day-050517.ppt Package Management for Bioinformatics Libraries, Applications and Data Allen Day |
4:30 | what_next.ppt Wrap up; next meeting, etc (with notes in the presentation from items discussed) Lincoln Stein and Scott Cain |
GMOD Architecture Working Group
Goal
The Architecture Working Group will make recommendations to the GMOD consortium on any cross-project policies which can lead to a more cohesive software project. The group will take into consideration:
- Interoperability with other GMOD components
- Performance
- Platform independence
GMOD will announce the recommendations and provide a repository for the recommendations on the website. Future developers will be pointed to these recommendations.
Workflow
The group will discuss which recommendations are needed and decide on an issue on which to make a recommendation. One or two recommendations at a time will be chosen to work on. The timeline will obviously be very different for each recommendation – some will be short with near consensus early on and will just be a matter of formalizing. Others will be more contentious and require more work to gain consensus on.
Timeline of a recommendation
Two to three weeks: Discussion of the current problem, specify exactly what the proposals should address. Any use cases are developed at this time. At the end of this time a request for proposals will go out.
Two weeks: Time for members of the working group to generate one or more proposed solutions to a problem. These solutions are formally written and submitted to the group.
Three weeks: Discuss and iterate on one or more proposals, come to a consensus. At the end of this time, one person will be delegated to 'close' the proposal by formalizing any suggested modifications to the recommendation. After one last review the proposal is formally submitted to GMOD.
Communication
Communication will take place primarily over email on the group list. One conference call per month can be expected and we will work out a time among the group that will be our standard time for a conference call. We will try to limit conference calls to one hour per month per active recommendation.