OEWG 20090813: Difference between revisions
No edit summary |
No edit summary |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:OBO-Edit working group]] | |||
OBO-Edit Working Group, Thursday August 13th, 2009 8.30 a.m. PST <br> | OBO-Edit Working Group, Thursday August 13th, 2009 8.30 a.m. PST <br> | ||
| Line 6: | Line 7: | ||
pin: 601425<br> | pin: 601425<br> | ||
Agenda/Chair: <br> | Agenda/Chair: Midori<br> | ||
Minutes: <br> | Minutes: Jen<br> | ||
Attendees: | Attendees: Midori, Jen, Chris and Amina | ||
==Action items carried over== | ==Action items carried over== | ||
==Discussion items== | ==Discussion items== | ||
*Would it be possible to make fixing the graph viewer a priority? I'm finding it a bit of a struggle using the graphviz viewer. The SF item is [https://sourceforge.net/tracker/?func=detail&aid=2745699&group_id=36855&atid=418257 here]. | |||
* Graph Viewer Improvements | |||
- Renamed "Succinct" configuration option to "Trim reasoner-generated (implied) links from display".<br> | |||
- Remove reasoner dependency from displaying all-types panels and showing ancestors upto root.<br> | |||
- Make RBR and LPR behave the same way | |||
Amina asks about bug prioritisation. <br> | |||
'''Please can everybody write and tell her about their No. 1 most important bug''', so she can work on those first. This will save everybody from reading right through the tracker. | |||
Graphviewer would take a week of work to fix as it is really a big rewrite to have it work without the reasoner. Is this worth doing? | |||
Yes: Then we have the graphview without installing graphviz. Handy for remote teaching sessions. | |||
Any idea of why graphviewer stopped working? | |||
The code to compile the link database changed. It was not the graphviewer that changed. | |||
But this component was working before. Can it be restored? Amina will look into this. | |||
Jen: put graphviz random term selector in bug report. | |||
Amina will set up cron job to run the JUnit tests. | |||
ActionListener timers are a memory hog. They affect performance. Is this near the top of the list to be fixed? No this is for after the consortium meeting. The reasoner is a higher priority just. | |||
==Action Items== | ==Action Items== | ||
* Working group to email AA a bug/comment on fixes | |||
* Graph Viewer Issues | |||
* consistent behavior for LPR and RBR | |||
* cronjob for JUnit tests | |||
==Links== | ==Links== | ||
[[OBO-Edit_Working_Group_Meeting_Agenda_and_Minutes|Back to OEWG Meeting agenda and minutes List]] | [[OBO-Edit_Working_Group_Meeting_Agenda_and_Minutes|Back to OEWG Meeting agenda and minutes List]] | ||
Latest revision as of 16:56, 30 June 2014
OBO-Edit Working Group, Thursday August 13th, 2009 8.30 a.m. PST
Conference call details:
US: 1-888-727-6732
Outside US: 1-719-867-3417
pin: 601425
Agenda/Chair: Midori
Minutes: Jen
Attendees: Midori, Jen, Chris and Amina
Action items carried over
Discussion items
- Would it be possible to make fixing the graph viewer a priority? I'm finding it a bit of a struggle using the graphviz viewer. The SF item is here.
- Graph Viewer Improvements
- Renamed "Succinct" configuration option to "Trim reasoner-generated (implied) links from display".
- Remove reasoner dependency from displaying all-types panels and showing ancestors upto root.
- Make RBR and LPR behave the same way
Amina asks about bug prioritisation.
Please can everybody write and tell her about their No. 1 most important bug, so she can work on those first. This will save everybody from reading right through the tracker.
Graphviewer would take a week of work to fix as it is really a big rewrite to have it work without the reasoner. Is this worth doing?
Yes: Then we have the graphview without installing graphviz. Handy for remote teaching sessions.
Any idea of why graphviewer stopped working?
The code to compile the link database changed. It was not the graphviewer that changed.
But this component was working before. Can it be restored? Amina will look into this.
Jen: put graphviz random term selector in bug report.
Amina will set up cron job to run the JUnit tests.
ActionListener timers are a memory hog. They affect performance. Is this near the top of the list to be fixed? No this is for after the consortium meeting. The reasoner is a higher priority just.
Action Items
- Working group to email AA a bug/comment on fixes
- Graph Viewer Issues
- consistent behavior for LPR and RBR
- cronjob for JUnit tests