Re: upcoming board report
On 12. Dec 2019, at 21:04, Marshall Schor wrote: > > The board report reminder message came just 1 day before the due date, so I've > gone ahead and submitted this report +1 Thanks! -- Richard
[jira] [Commented] (UIMA-6160) Single int arg version of select.startAt()?
[ https://issues.apache.org/jira/browse/UIMA-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995419#comment-16995419 ] Richard Eckart de Castilho commented on UIMA-6160: -- I am not sure if having exceptions is necessary even as long as the documentation explains the behavior. Probably I'd not throw exceptions. After all `startAt(x, MAX_VALUE)` is a valid call even if priorities are enabled. > Single int arg version of select.startAt()? > --- > > Key: UIMA-6160 > URL: https://issues.apache.org/jira/browse/UIMA-6160 > Project: UIMA > Issue Type: Improvement > Components: UIMA >Affects Versions: 3.1.1SDK >Reporter: Richard Eckart de Castilho >Priority: Major > > If one wants to start looking for a particular annotation at a given > character position, then I think it would be convenient to be able to say > "select(Token.class).startAt(offset)", instead of having to say > "select(Token.class).startAt(offset, offset)". > What is not clear to me from reading the documentation is whether a Token > which *ends* at offset would be returned or not. > Another special case which is not clear by the documentation is whether a > Token which *starts and ends* at offset would be returned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-6160) Single int arg version of select.startAt()?
[ https://issues.apache.org/jira/browse/UIMA-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995417#comment-16995417 ] Richard Eckart de Castilho commented on UIMA-6160: -- Having `startAt(int)` always behave as if type priorities didn't exist by internally providing `Integer.MAX_VALUE` as the second argument to `startAt(int, int)` sounds like the expected behavior - at least to me ;) > Single int arg version of select.startAt()? > --- > > Key: UIMA-6160 > URL: https://issues.apache.org/jira/browse/UIMA-6160 > Project: UIMA > Issue Type: Improvement > Components: UIMA >Affects Versions: 3.1.1SDK >Reporter: Richard Eckart de Castilho >Priority: Major > > If one wants to start looking for a particular annotation at a given > character position, then I think it would be convenient to be able to say > "select(Token.class).startAt(offset)", instead of having to say > "select(Token.class).startAt(offset, offset)". > What is not clear to me from reading the documentation is whether a Token > which *ends* at offset would be returned or not. > Another special case which is not clear by the documentation is whether a > Token which *starts and ends* at offset would be returned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-6160) Single int arg version of select.startAt()?
[ https://issues.apache.org/jira/browse/UIMA-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995058#comment-16995058 ] Marshall Schor commented on UIMA-6160: -- Another alternative definition, given that startAt(123) is a shorthand, is to be more opinionated around when this form was used, and add additional common-sense requirements. For example, we could require that typePriority not be set, and if it was, we could throw a runtime exception, the logic being that this would much more likely be a user error, than an intent. The infrequent exception (if any) where someone wanted typepriorities used could use the explicit 2 argument form of startAt. Other cases where it would be quite unlikely to have a combination of settings with startAt(123) form, could also be designed to throw exceptions. We would only do this for cases where it was much more likely this was a user error than an intent. > Single int arg version of select.startAt()? > --- > > Key: UIMA-6160 > URL: https://issues.apache.org/jira/browse/UIMA-6160 > Project: UIMA > Issue Type: Improvement > Components: UIMA >Affects Versions: 3.1.1SDK >Reporter: Richard Eckart de Castilho >Priority: Major > > If one wants to start looking for a particular annotation at a given > character position, then I think it would be convenient to be able to say > "select(Token.class).startAt(offset)", instead of having to say > "select(Token.class).startAt(offset, offset)". > What is not clear to me from reading the documentation is whether a Token > which *ends* at offset would be returned or not. > Another special case which is not clear by the documentation is whether a > Token which *starts and ends* at offset would be returned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: upcoming board report
The board report reminder message came just 1 day before the due date, so I've gone ahead and submitted this report: Board report for Apache UIMA, for December 2019. ## Description: Apache UIMA's mission: the creation and maintenance of open-source software related to the analysis of unstructured data, guided by the UIMA Oasis Standard. The software provides frameworks, tools and annotators, facilitating the analysis of unstructured content such as text, audio and video. ## Membership Data: Apache UIMA was founded 2010-03-16 (10 years ago) There are currently 25 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - Viorel Morari was added to the PMC on 2019-11-18 - No new committers. Last addition was Viorel Morari on 2018-09-20. ## Releases: 3 releases in last quarter uimaj-3.1.1 was released on 2019-11-08. UIMA Ruta 2.8.0 was released on 2019-11-28. UIMA Ruta 3.0.0 was released on 2019-12-09. ## Activity: The uimaj-3.1.1 was the first release of uimaj after migrating that project from SVN to GIT. The Ruta 3.0.0 is the first release of Ruta that depends on the newer release stream of core uima version 3. The uima-cpp subproject was (after many years of dormancy) upgraded to current levels of C++ compiler tool chains and associated dependencies; we hope a release will be forthcoming after some more testing, soon. ## Community Health: The community continues to be moderately active. ## Issues: No Board level issues at this time. -Marshall On 12/11/2019 5:34 PM, Marshall Schor wrote: > Please post items for the report. > > I'll mention our new PMC member :-) and the new releases including the first > RUTA release compatible with UIMA v3, the 1st release of uimaj sdk from our > GIT repo, and the refreshing of uimacpp to current levels of compiler > versions and dependencies. > > Anything else? -Marshall >
[jira] [Commented] (UIMA-6161) DUCC facilitate specification of machine list for user submitted work
[ https://issues.apache.org/jira/browse/UIMA-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994763#comment-16994763 ] Lou DeGenaro commented on UIMA-6161: !Screenshot from 2019-12-12 10-01-36.png! > DUCC facilitate specification of machine list for user submitted work > - > > Key: UIMA-6161 > URL: https://issues.apache.org/jira/browse/UIMA-6161 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Affects Versions: 3.0.1-Ducc >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Attachments: Screenshot from 2019-12-12 10-01-36.png > > > Allow users to target one or more specific machines associated with the > scheduling class. > Add new flag --machine_list to the CLI submit commands. > Provide logic in Resource Manager (RM) to only allocate shares on the user > specified machines. If machine_list is not specified, all machines > associated with the scheduling class are eligible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6161) DUCC facilitate specification of machine list for user submitted work
[ https://issues.apache.org/jira/browse/UIMA-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro updated UIMA-6161: --- Attachment: Screenshot from 2019-12-12 10-01-36.png > DUCC facilitate specification of machine list for user submitted work > - > > Key: UIMA-6161 > URL: https://issues.apache.org/jira/browse/UIMA-6161 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Affects Versions: 3.0.1-Ducc >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Attachments: Screenshot from 2019-12-12 10-01-36.png > > > Allow users to target one or more specific machines associated with the > scheduling class. > Add new flag --machine_list to the CLI submit commands. > Provide logic in Resource Manager (RM) to only allocate shares on the user > specified machines. If machine_list is not specified, all machines > associated with the scheduling class are eligible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (UIMA-6161) DUCC facilitate specification of machine list for user submitted work
Lou DeGenaro created UIMA-6161: -- Summary: DUCC facilitate specification of machine list for user submitted work Key: UIMA-6161 URL: https://issues.apache.org/jira/browse/UIMA-6161 Project: UIMA Issue Type: Improvement Components: DUCC Affects Versions: 3.0.1-Ducc Reporter: Lou DeGenaro Assignee: Lou DeGenaro Allow users to target one or more specific machines associated with the scheduling class. Add new flag --machine_list to the CLI submit commands. Provide logic in Resource Manager (RM) to only allocate shares on the user specified machines. If machine_list is not specified, all machines associated with the scheduling class are eligible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
