Re: Updating Incubator summary

[lewis john mcgibbney]

Hi Henri,
I just pushed the update to SVN. Should update asynch reasonably soon.

http://incubator.apache.org/projects/joshua.html

Thanks

On Sun, Nov 13, 2016 at 1:22 PM, <
dev-digest-h...@joshua.incubator.apache.org> wrote:

>
> From: Henri Yandell 
> To: dev@joshua.incubator.apache.org
> Cc:
> Date: Sun, 13 Nov 2016 01:17:57 -0800
> Subject: Updating Incubator summary
> Would be useful to update this page:
>
> http://incubator.apache.org/projects/joshua.html
>
>
> Are there any of the checklist items that are still open?
>
>
As far as I am aware no :)

[jira] [Commented] (JOSHUA-315) Thrax keeps all rules

[Matt Post (JIRA)]

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

Matt Post commented on JOSHUA-315:
--

This has been addressed in commit 885389d513b5d0f3f68b59c3b17a776584b3a208. If 
you add the word "count" to the list of thrax features in the thrax config 
file, a sixth field will be extracted with the rule count, e.g.,

[X] ||| de ||| of ||| 0.72572 0.29124 1 0 0.39357 0.17023 ||| 0-0 ||| 
2565758
[X] ||| de ||| to ||| 2.89509 2.10811 1 0 2.87285 2.08282 ||| 0-0 ||| 215020
[X] ||| de ||| in ||| 3.11663 2.17583 1 0 2.91081 2.34837 ||| 0-0 ||| 207011
...

This is then used by the filter-rules.pl script (with the flag -t 100) to prune 
remove all rules except the top 100 most frequent, for each source side. This 
has been added to the pipeline. The grammars seem to be about 5% smaller and 
should have only a positive effect on running time.

> Thrax keeps all rules
> -
>
> Key: JOSHUA-315
> URL: https://issues.apache.org/jira/browse/JOSHUA-315
> Project: Joshua
>  Issue Type: Bug
>Reporter: Matt Post
> Fix For: 6.2
>
>
> When extracting rules, Thrax keeps *all* options for each target side. For 
> large bitexts and common source sides (e.g., "de" for Spanish–English), there 
> can be tens of thousands of translations, due to errors in the alignments and 
> phenomena like garbage collection. The decoder throws out all but the top 
> num_translation_options of these (default 20), but before doing so, it has to 
> score all the target side options with all feature functions, include the 
> language model. This slows down "warming up" of the model and means that the 
> first sentences to use these items are very slow to translation.
> I have updated scripts/training/filter-rules.pl to filter out using Thrax's 
> rarity penalty field, but it would be much better if Thrax were to keep only 
> the most 100 frequent translation options for each source side.



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

[jira] [Resolved] (JOSHUA-315) Thrax keeps all rules

[Matt Post (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JOSHUA-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Post resolved JOSHUA-315.
--
Resolution: Fixed

> Thrax keeps all rules
> -
>
> Key: JOSHUA-315
> URL: https://issues.apache.org/jira/browse/JOSHUA-315
> Project: Joshua
>  Issue Type: Bug
>Reporter: Matt Post
> Fix For: 6.2
>
>
> When extracting rules, Thrax keeps *all* options for each target side. For 
> large bitexts and common source sides (e.g., "de" for Spanish–English), there 
> can be tens of thousands of translations, due to errors in the alignments and 
> phenomena like garbage collection. The decoder throws out all but the top 
> num_translation_options of these (default 20), but before doing so, it has to 
> score all the target side options with all feature functions, include the 
> language model. This slows down "warming up" of the model and means that the 
> first sentences to use these items are very slow to translation.
> I have updated scripts/training/filter-rules.pl to filter out using Thrax's 
> rarity penalty field, but it would be much better if Thrax were to keep only 
> the most 100 frequent translation options for each source side.



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

Re: [VOTE] Release Apache Joshua (Incubating) 6.1

[John Hewitt]

+1 Let's do it.

-John

On Mon, Nov 14, 2016 at 1:13 PM, kellen sunderland <
kellen.sunderl...@gmail.com> wrote:

> +1 .  Thanks to Lewis and Matt for all the recent work.
>
> On Nov 14, 2016 7:11 PM, "Matt Post"  wrote:
>
> +1
>
> Thanks for starting this off, Lewis!
>
>
> > On Nov 14, 2016, at 12:54 PM, Ramirez, Paul M (398M) <
> paul.m.rami...@jpl.nasa.gov> wrote:
> >
> > +1, let's get it released!!!
> >
> > --Paul
> >
> > ==
> > Paul Ramirez - Group Supervisor
> > Computer Science for Data Intensive Applications (398M)
> > NASA - Jet Propulsion Laboratory
> > 4800 Oak Grove Dr.
> > Pasadena, CA 91109 USA
> > Mailstop: 158-242
> > Office: 818-354-1015
> > Cell: 818-395-8194
> > ==
> >
> > On 11/14/16, 9:16 AM, "lewis john mcgibbney"  wrote:
> >
> >Hi Folks,
> >Please VOTE on the Apache Joshua 6.1 Release Candidate #1.
> >
> >We solved 44 issues: https://s.apache.org/joshua6.1
> >
> >Git source tag (167489bbd78526b9833fe7c88646bf96101d5d2b):
> >https://s.apache.org/joshua6.1tag
> >
> >Staging repo:
> >https://repository.apache.org/content/repositories/
> orgapachejoshua-1000/
> >
> >Source Release Artifacts:
> >https://dist.apache.org/repos/dist/dev/incubator/joshua/
> >
> >PGP release keys (signed using 48BAEBF6):
> >https://dist.apache.org/repos/dist/release/incubator/joshua/KEYS
> >
> >Vote will be open for 72 hours.
> >Thank you to everyone that is able to VOTE as well as everyone that
> >contributed to Apache Joshua 6.1.
> >
> >[ ] +1, let's get it released!!!
> >[ ] +/-0, fine, but consider to fix few issues before...
> >[ ] -1, nope, because... (and please explain why)
> >
> >P.S. here is my +1
> >
> >--
> >http://home.apache.org/~lewismc/
> >@hectorMcSpector
> >http://www.linkedin.com/in/lmcgibbney
> >
> >
>

Re: [VOTE] Release Apache Joshua (Incubating) 6.1

[kellen sunderland]

+1 .  Thanks to Lewis and Matt for all the recent work.

On Nov 14, 2016 7:11 PM, "Matt Post"  wrote:

+1

Thanks for starting this off, Lewis!


> On Nov 14, 2016, at 12:54 PM, Ramirez, Paul M (398M) <
paul.m.rami...@jpl.nasa.gov> wrote:
>
> +1, let's get it released!!!
>
> --Paul
>
> ==
> Paul Ramirez - Group Supervisor
> Computer Science for Data Intensive Applications (398M)
> NASA - Jet Propulsion Laboratory
> 4800 Oak Grove Dr.
> Pasadena, CA 91109 USA
> Mailstop: 158-242
> Office: 818-354-1015
> Cell: 818-395-8194
> ==
>
> On 11/14/16, 9:16 AM, "lewis john mcgibbney"  wrote:
>
>Hi Folks,
>Please VOTE on the Apache Joshua 6.1 Release Candidate #1.
>
>We solved 44 issues: https://s.apache.org/joshua6.1
>
>Git source tag (167489bbd78526b9833fe7c88646bf96101d5d2b):
>https://s.apache.org/joshua6.1tag
>
>Staging repo:
>https://repository.apache.org/content/repositories/
orgapachejoshua-1000/
>
>Source Release Artifacts:
>https://dist.apache.org/repos/dist/dev/incubator/joshua/
>
>PGP release keys (signed using 48BAEBF6):
>https://dist.apache.org/repos/dist/release/incubator/joshua/KEYS
>
>Vote will be open for 72 hours.
>Thank you to everyone that is able to VOTE as well as everyone that
>contributed to Apache Joshua 6.1.
>
>[ ] +1, let's get it released!!!
>[ ] +/-0, fine, but consider to fix few issues before...
>[ ] -1, nope, because... (and please explain why)
>
>P.S. here is my +1
>
>--
>http://home.apache.org/~lewismc/
>@hectorMcSpector
>http://www.linkedin.com/in/lmcgibbney
>
>

Re: [VOTE] Release Apache Joshua (Incubating) 6.1

[Matt Post]

+1

Thanks for starting this off, Lewis!


> On Nov 14, 2016, at 12:54 PM, Ramirez, Paul M (398M) 
>  wrote:
> 
> +1, let's get it released!!!
> 
> --Paul
> 
> ==
> Paul Ramirez - Group Supervisor
> Computer Science for Data Intensive Applications (398M)
> NASA - Jet Propulsion Laboratory
> 4800 Oak Grove Dr.
> Pasadena, CA 91109 USA
> Mailstop: 158-242
> Office: 818-354-1015
> Cell: 818-395-8194
> ==
> 
> On 11/14/16, 9:16 AM, "lewis john mcgibbney"  wrote:
> 
>Hi Folks,
>Please VOTE on the Apache Joshua 6.1 Release Candidate #1.
> 
>We solved 44 issues: https://s.apache.org/joshua6.1
> 
>Git source tag (167489bbd78526b9833fe7c88646bf96101d5d2b):
>https://s.apache.org/joshua6.1tag
> 
>Staging repo:
>https://repository.apache.org/content/repositories/orgapachejoshua-1000/
> 
>Source Release Artifacts:
>https://dist.apache.org/repos/dist/dev/incubator/joshua/
> 
>PGP release keys (signed using 48BAEBF6):
>https://dist.apache.org/repos/dist/release/incubator/joshua/KEYS
> 
>Vote will be open for 72 hours.
>Thank you to everyone that is able to VOTE as well as everyone that
>contributed to Apache Joshua 6.1.
> 
>[ ] +1, let's get it released!!!
>[ ] +/-0, fine, but consider to fix few issues before...
>[ ] -1, nope, because... (and please explain why)
> 
>P.S. here is my +1
> 
>-- 
>http://home.apache.org/~lewismc/
>@hectorMcSpector
>http://www.linkedin.com/in/lmcgibbney
> 
> 

Re: "Amazon launches voice-controlled music streaming service"

[Henri Yandell]

Not as far as I know.

On Mon, Nov 14, 2016 at 08:13 lewis john mcgibbney 
wrote:

> Hi Folks,
> Any Joshua involved deep down in here?
>
>
> "Amazon launches voice-controlled music streaming service"
>
>
>
> http://www.scotsman.com/future-scotland/tech/amazon-launches-voice-controlled-music-streaming-service-1-4286952
>

[jira] [Updated] (JOSHUA-290) Provide Joshua artifact as a bundle

[Lewis John McGibbney (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JOSHUA-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated JOSHUA-290:

Fix Version/s: 6.2

> Provide Joshua artifact as a bundle
> ---
>
> Key: JOSHUA-290
> URL: https://issues.apache.org/jira/browse/JOSHUA-290
> Project: Joshua
>  Issue Type: Task
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.2
>
>
> I think it'd be good if we could make the Joshua artifact an OSGi _bundle_.
> This would have no impact on plain java applications but would give the 
> following benefits:
> - make it possible to install it in OSGi environments
> - optionally introduce semantic versioning (in addition with the baseline 
> plugin) that would help track e.g. if changes in APIs break backward 
> compatibility 



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

[jira] [Updated] (JOSHUA-51) add jhclark/bigfatlm

[Lewis John McGibbney (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JOSHUA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated JOSHUA-51:
---
Fix Version/s: 6.1

> add jhclark/bigfatlm
> 
>
> Key: JOSHUA-51
> URL: https://issues.apache.org/jira/browse/JOSHUA-51
> Project: Joshua
>  Issue Type: Bug
>Reporter: Matt Post
>Assignee: Matt Post
> Fix For: 6.2
>
>
> It would be nice to leverage more Hadoop tools in the pipeline.



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

[jira] [Updated] (JOSHUA-314) Enable set structured-output from config file

[Lewis John McGibbney (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JOSHUA-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated JOSHUA-314:

Fix Version/s: 6.2

> Enable set structured-output from config file
> -
>
> Key: JOSHUA-314
> URL: https://issues.apache.org/jira/browse/JOSHUA-314
> Project: Joshua
>  Issue Type: Improvement
>  Components: core
>Reporter: Tommaso Teofili
> Fix For: 6.2
>
>
> Currently if one sets _use-structured-output = true_ in joshua.config that 
> results in error when parsing the config as it's not explicitly handled by 
> {{JoshuaConfiguration#readConfig}} (it can only be set programmatically), I 
> think it'd be nice to be able to configure it from config file too.



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

[jira] [Updated] (JOSHUA-51) add jhclark/bigfatlm

[Lewis John McGibbney (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JOSHUA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated JOSHUA-51:
---
Fix Version/s: (was: 6.1)
   6.2

> add jhclark/bigfatlm
> 
>
> Key: JOSHUA-51
> URL: https://issues.apache.org/jira/browse/JOSHUA-51
> Project: Joshua
>  Issue Type: Bug
>Reporter: Matt Post
>Assignee: Matt Post
> Fix For: 6.2
>
>
> It would be nice to leverage more Hadoop tools in the pipeline.



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

[jira] [Resolved] (JOSHUA-323) Joshua 6.1 Release Management

[Lewis John McGibbney (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JOSHUA-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney resolved JOSHUA-323.
-
Resolution: Fixed

> Joshua 6.1 Release Management
> -
>
> Key: JOSHUA-323
> URL: https://issues.apache.org/jira/browse/JOSHUA-323
> Project: Joshua
>  Issue Type: Task
>  Components: build, release
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Blocker
> Fix For: 6.1
>
>
> This is a governing ticket for reference more than anything else. We need to 
> add all release specific build additions to parent pom.xml which enable us to 
> roll a release candidate.
> The process is also being documented over at 
> https://cwiki.apache.org/confluence/display/JOSHUA/Joshua+Release+Management+Procedure



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

[VOTE] Release Apache Joshua (Incubating) 6.1

[lewis john mcgibbney]

Hi Folks,
Please VOTE on the Apache Joshua 6.1 Release Candidate #1.

We solved 44 issues: https://s.apache.org/joshua6.1

Git source tag (167489bbd78526b9833fe7c88646bf96101d5d2b):
https://s.apache.org/joshua6.1tag

Staging repo:
https://repository.apache.org/content/repositories/orgapachejoshua-1000/

Source Release Artifacts:
https://dist.apache.org/repos/dist/dev/incubator/joshua/

PGP release keys (signed using 48BAEBF6):
https://dist.apache.org/repos/dist/release/incubator/joshua/KEYS

Vote will be open for 72 hours.
Thank you to everyone that is able to VOTE as well as everyone that
contributed to Apache Joshua 6.1.

[ ] +1, let's get it released!!!
[ ] +/-0, fine, but consider to fix few issues before...
[ ] -1, nope, because... (and please explain why)

P.S. here is my +1

-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

"Amazon launches voice-controlled music streaming service"

[lewis john mcgibbney]

Hi Folks,
Any Joshua involved deep down in here?


"Amazon launches voice-controlled music streaming service"


http://www.scotsman.com/future-scotland/tech/amazon-launches-voice-controlled-music-streaming-service-1-4286952