Moses-support Digest, Vol 82, Issue 50

Send Moses-support mailing list submissions to
moses-support@mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu

You can reach the person managing the list at
moses-support-owner@mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."


Today's Topics:

1. XCode projects (Lane Schwartz)
2. Re: XCode projects (Hieu Hoang)
3. Known implementations of MBR system combination? (Lane Schwartz)


----------------------------------------------------------------------

Message: 1
Date: Thu, 29 Aug 2013 17:12:10 -0400
From: Lane Schwartz <dowobeha@gmail.com>
Subject: [Moses-support] XCode projects
To: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CABv3vZmXjjfnJ44uU7Pgz-Bo8xaXA9qXGX=NP0teWLzkFCYhWw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

As you may or may not have noticed from the commit logs, I have started to
clean up the XCode build projects.

Currently there are multiple XCode projects; essentially, there is one per
library and one per executable.

I would like to propose changing this to a single XCode project with
multiple targets. Within the new XCode project, there would be one target
per library and one target per binary, and if you select a binary to build,
XCode would automatically build the prerequisite libraries.

Does anyone have any objections to this change? I'm assuming based on how
outdated they were that no one has been using them lately, but if you care,
here's your chance to object before I make the change.

In addition, I am also seriously considering removing the XCode project
file from source control. Part of the reason that no one appears to be
using the XCode project is that it is unwieldy to maintain. Currently, any
time a new source file is added to moses, or an existing source file is
deleted, manual action is required to make the requisite change to the
XCode project. I think a more viable solution would be to have a script
generate an XCode project on demand; this script would scan the source code
directories and automatically create an up-to-date project.

Cheers,
Lane
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20130829/9dafd0db/attachment-0001.htm

------------------------------

Message: 2
Date: Thu, 29 Aug 2013 23:32:23 +0100
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] XCode projects
To: moses-support@mit.edu
Message-ID: <521FCBF7.2070804@gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

no objections from me

On 29/08/2013 22:12, Lane Schwartz wrote:
> As you may or may not have noticed from the commit logs, I have
> started to clean up the XCode build projects.
>
> Currently there are multiple XCode projects; essentially, there is one
> per library and one per executable.
>
> I would like to propose changing this to a single XCode project with
> multiple targets. Within the new XCode project, there would be one
> target per library and one target per binary, and if you select a
> binary to build, XCode would automatically build the prerequisite
> libraries.
>
> Does anyone have any objections to this change? I'm assuming based on
> how outdated they were that no one has been using them lately, but if
> you care, here's your chance to object before I make the change.
>
> In addition, I am also seriously considering removing the XCode
> project file from source control. Part of the reason that no one
> appears to be using the XCode project is that it is unwieldy to
> maintain. Currently, any time a new source file is added to moses, or
> an existing source file is deleted, manual action is required to make
> the requisite change to the XCode project. I think a more viable
> solution would be to have a script generate an XCode project on
> demand; this script would scan the source code directories and
> automatically create an up-to-date project.
>
> Cheers,
> Lane
>
>
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20130829/b0baceb8/attachment-0001.htm

------------------------------

Message: 3
Date: Fri, 30 Aug 2013 11:34:46 -0400
From: Lane Schwartz <dowobeha@gmail.com>
Subject: [Moses-support] Known implementations of MBR system
combination?
To: "moses-support@mit.edu" <moses-support@mit.edu>
Message-ID:
<CABv3vZkOP4Fs-xe_CFQu_LFvJc38K98qM5cQMH=mmBEG5XzE0Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I was wondering if anyone knows of any available implementations of MBR for
system combination, such as the techniques described in (Gonzalez-Rubio et
al, ACL 2011) and (Duh et al, IJCNLP 2011).

Thanks,
Lane
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20130830/2e5fb2f2/attachment-0001.htm

------------------------------

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 82, Issue 50
*********************************************

Tweet