OEWG 20110517: Difference between revisions
Jump to navigation
Jump to search
Line 37: | Line 37: | ||
* Changed wording of messages in OE and in installer about the fact that memory allocation is limited to 1860M unless you have a 64-bit JVM. | * Changed wording of messages in OE and in installer about the fact that memory allocation is limited to 1860M unless you have a 64-bit JVM. | ||
** No way to change installer to conditionally allow >1860M if JVM is 64-bit, but at least wording now explains why there's a limit and how you can get around it. | ** No way to change installer to conditionally allow >1860M if JVM is 64-bit, but at least wording now explains why there's a limit and how you can get around it. | ||
[[File:memory-message.png]] | |||
===Next bugs to work on=== | ===Next bugs to work on=== |
Revision as of 14:24, 16 May 2011
OBO-Edit Working Group Meeting: Tuesday, May 17, 2011, 8:30am PDT
Conference call numbers:
US: 1 866 953 9688
UK: 0808 238 6001
PIN: 801561
Agenda/Chair: Nomi Harris
Minutes:
Attendees:
Bug and Feature Trackers
Discussion items
Fixed since last meeting
Can't restrict ancestor search by relation type in 2.1b12 (same bug)
- If you have the reasoner on and select "ancestor" or "descendant" as the search aspect, it's supposed to add a list of relations and the label "can be reached via", but that stopped happening in 2.1-b11 or 12
- Fixed in 2.1-b13
- Search for children is missing some (unless reasoner on)
- This was an old bug. Turned out that when links to children were being collected, the code erroneously took the PARENT of each link instead of the child. (But when the reasoner was on, there was a different loop, which is why the child search worked ok with the reasoner on.)
- Fixed in 2.1-b13
- Filtered save with "child" aspect throws exception
- Fixed in 2.1-b13
- As suggested by OEWG, all search aspects are once again available in search aspect menu. If user selects an aspect (Ancestor or Descendant) that requires reasoning and the reasoner isn't on, they get a pop-up error message:
- (The previous solution--leaving Ancestor and Descendant out of the aspect menu when reasoner was off--confused users.)
- Also, you can (once again) do filtered saves with Ancestor and Descendant even when the reasoner is off, because the filtered save method can start a reasoner.
- Some users complained that these filtered saves that silently invoked the reasoner took so long they thought OE had crashed. Now the Progress window says "This filtered save requires the reasoner--please be patient." (Note that the progress string is limited in length--if you make it longer than that it gets cut off.)
- Add verification check for single intersection_of tag
- Changed wording of messages in OE and in installer about the fact that memory allocation is limited to 1860M unless you have a 64-bit JVM.
- No way to change installer to conditionally allow >1860M if JVM is 64-bit, but at least wording now explains why there's a limit and how you can get around it.
Next bugs to work on
- Is_a closure broken
- Filtered save with "is_a closure" checked doesn't save all the terms it should.
- Still working on this
- Bad handling of unrecognized relation (text editor et al.)
- I looked into this some--will not be simple to fix. Has to do with how dangling objects (e.g., unrecognized relations) are handled in different components.
- Bugs with priority 6, Features with priority 6-7
- Let's talk about which of these I should look at next.