[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[chrismattmann]

Github user chrismattmann commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-220756830
  
dusted


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JOSHUA-262) Implement all logging as Slf4j over Log4j

[Thamme Gowda (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294664#comment-15294664
 ] 

Thamme Gowda commented on JOSHUA-262:
-

that means:
- 0 for DEBUG. When we set level to INFO, these messages don't show up.
- 1 for INFO. No ambiguities here
- 2+ It seems like DEBUG, although I am not sure

Since log4j allows us to set different levels to specific classes and packages, 
we can tune them. 

I will send any System.err.print*s to ERROR and System.out.print*s to INFO.

Please correct me if this is wrong.





> Implement all logging as Slf4j over Log4j
> -
>
> Key: JOSHUA-262
> URL: https://issues.apache.org/jira/browse/JOSHUA-262
> Project: Joshua
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 6.0.5
>Reporter: Lewis John McGibbney
>Assignee: Thamme Gowda N
> Fix For: 6.1
>
>
> [~hsaputra] suggested that we implement all logging as Slf4j over Log4j. If 
> we use [parameterized logging 
> notation|http://www.slf4j.org/faq.html#logging_performance] we can have good 
> logging in place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JOSHUA-262) Implement all logging as Slf4j over Log4j

[Lewis John McGibbney (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294656#comment-15294656
 ] 

Lewis John McGibbney commented on JOSHUA-262:
-

I honestly have no idea.

> Implement all logging as Slf4j over Log4j
> -
>
> Key: JOSHUA-262
> URL: https://issues.apache.org/jira/browse/JOSHUA-262
> Project: Joshua
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 6.0.5
>Reporter: Lewis John McGibbney
>Assignee: Thamme Gowda N
> Fix For: 6.1
>
>
> [~hsaputra] suggested that we implement all logging as Slf4j over Log4j. If 
> we use [parameterized logging 
> notation|http://www.slf4j.org/faq.html#logging_performance] we can have good 
> logging in place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JOSHUA-262) Implement all logging as Slf4j over Log4j

[Matt Post (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294655#comment-15294655
 ] 

Matt Post commented on JOSHUA-262:
--

It's not very systematic. 

- 0: print nothing. This mostly works, except the flag is not passed to KenLM, 
which sometimes prints something
- 1: print "basic" information, like progress loading models, information about 
each sentence, and so on
- 2+: extended debugging and detail

I think it's useful to have a "silent" model (-v 0), and 1 should probably be 
for INFO. I'm not sure what the standard practice is when you want extra 
debugging output?

> Implement all logging as Slf4j over Log4j
> -
>
> Key: JOSHUA-262
> URL: https://issues.apache.org/jira/browse/JOSHUA-262
> Project: Joshua
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 6.0.5
>Reporter: Lewis John McGibbney
>Assignee: Thamme Gowda N
> Fix For: 6.1
>
>
> [~hsaputra] suggested that we implement all logging as Slf4j over Log4j. If 
> we use [parameterized logging 
> notation|http://www.slf4j.org/faq.html#logging_performance] we can have good 
> logging in place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294648#comment-15294648
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user thammegowda commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-220753345
  
@mjpost Sorry for my previous incomplete comment.
 The problem I see with that line is, now we have new package 
`org.apache.joshua.decoder.ff` instead of old `joshua.decoder.ff`.
Since lewis is currently working on this, I didnt dare to raise a new PR to 
fix a single line :-) 


> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[thammegowda]

Github user thammegowda commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-220753345
  
@mjpost Sorry for my previous incomplete comment.
 The problem I see with that line is, now we have new package 
`org.apache.joshua.decoder.ff` instead of old `joshua.decoder.ff`.
Since lewis is currently working on this, I didnt dare to raise a new PR to 
fix a single line :-) 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294643#comment-15294643
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-220753066
  
What's problematic about that? FYI, that line is part of the code that lets 
feature functions be loaded by reflection, e.g., so you can write a new feature 
function and call it directly from the command line without having to add stub 
code to check for and load it.


> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: May 2016 Newsletter – LDC

[Mattmann, Chris A (3980)]

Thanks Lewis. I’m also an org rep for NASA at LDC, and also via my
USC hat. Good show.

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++










On 5/20/16, 8:45 AM, "Lewis John Mcgibbney"  wrote:

>Hi Folks,
>I've ended up primary JPL organizational rep for the linguistics data
>consortium. They produce monthly newsletters (see below for most
>recent) which I will be forwarding to dev@ Joshua from now on.
>They are pretty cool, especially the new datasets they publish.
>Lewis
>
>-- Forwarded message --
>From: *Mcgibbney, Lewis J (398M)* 
>Date: Friday, May 20, 2016
>Subject: Fwd: May 2016 Newsletter – LDC
>To: "lewis.mcgibb...@gmail.com" 
>
>
>
>
>Sent from my iPhone
>
>Begin forwarded message:
>
>*From:* Linguistic Data Consortium >
>*Date:* May 16, 2016 at 8:20:33 AM PDT
>*To:* Linguistic Data Consortium >
>*Subject:* *May 2016 Newsletter – LDC*
>
>*In this newsletter:*
>
>*LDC at LREC 2016*
>
>
>
>*New publications:*
>
>­­SDP 2014 & 2015: Broad Coverage Semantic Dependency Parsing
><#m_-2915229479963685663_SDP>
>
>
>GALE Phase 4 Chinese Broadcast Conversation Speech
><#m_-2915229479963685663_GALE1>
>
>
>GALE Phase 4 Chinese Broadcast Conversation Transcripts
><#m_-2915229479963685663_GALE2>
>
>
>
>
>
>*LDC at LREC 2016*
>
>
>
>LDC will attend the 10th Language Resource Evaluation Conference
>(LREC2016), hosted by ELRA, the European Language Resource Association. The
>conference will be held in Portorož, Slovenia from May 23-28 and features a
>broad range of sessions on language resources and human language
>technologies research. Seven LDC staff members will be presenting current
>work on topics including trends in HLT research, building language
>resources for autism spectrum disorders, data management plans, rapid
>development of morphological analyzers for typologically diverse languages,
>selection criteria for low resource language programs, multi-language
>speech collection for NIST LRE, novel incentives for collecting data and
>annotation from people, and more.
>
>
>
>Following the conference, LDC’s presented papers and posters will be
>available on LDC’s Papers Page
>.
>
>
>
>
>
>New Corpora
>
>
>
>(1) SDP 2014 & 2015: Broad Coverage Semantic Dependency Parsing
> consists of data, tools, system
>results, and publications associated with the 2014 and 2015 tasks on
>Broad-Coverage Semantic Dependency Parsing (SDP )
>conducted in conjunction with the International Workshop on Semantic
>Evaluation (SemEval ) and was developed
>by the SDP task organizers.
>
>SemEval is an ongoing series of evaluations of computational semantic
>analysis systems intended to explore the nature of meaning in language. It
>evolved from the Senseval  word sense
>disambiguation series to include semantic analysis tasks outside of word
>sense disambiguation.
>
>This release is based on English, Chinese and Czech data from the following
>resources: Treebank-2 LDC95T17 ,
>Proposition Bank I LDC2004T14 ,
>NomBaank v 1.0 LDC2008T23  and
>CCGBank LDC2005T13  (English);
>Chinese Treebank (e.g., Chinese Treebank 8.0 LDC2013T21
>) (Chinese); and Prague
>Dependency Treebank (e.g., Prague Dependency Treebank 2.0, LDC2006T01
>) (Czech).
>
>The results are presented as graphs in three target representations:
>MRS-Derived Semantic Dependencies (DM), Enju Predicate–Argument Structures
>(PAS), and Prague Semantic Dependencies (PSD). As a fourth, additional
>target representation CCGbank was converted to semantic dependency graphs
>(in the subdirectory ‘ccd’).
>
>SDP 2014 & 2015: Broad Coverage Semantic Dependency Parsing is distributed
>via web download.
>
>2016 Subscription Members will automatically receive two copies of this
>corpus. 2016 Standard