Greetings 2001, Now everyone who needs a replication assignment should have their replication assignment. A couple of notes: Everyone should have received a replication project who is either (1) writing a replication paper for the course, or (2) a distance student

the course for credit. If you expected to receive a project to

but did not receive one, send me an email. Also, if something seems fishy, like you received a different

assignment by email than in class, or you were assigned your own project

re-replicate, send me an email. If any information you need to replicate the replications is missing

the packet (the code, the writeup, etc.), contact the replication

Your assignment is to replicate the replications. Next Monday, April 7,

will bring to class (or submit to the dropbox if necessary) at least one hardcopy of a 1-2 page memo. The goal of the memo is to offer

feedback to the replication authors. Point out places where their code didn't work or where their work was unclear, or especially how they can improve the original papers. The one hard copy of this memo you bring

class will be the copy we grade. You should also give each of the replication authors a copy of the memo. You may give them either a hard copy or an electronic copy. Each person was assigned a replication project. Don't be confused if

were emailed along with another person or two- I was trying to be

in my tens of emails today. This is an individual project. That is not

say that you cannot work with others- discussing projects with others is

great way to find potential developments. But you are not required to

on this replication with your coauthors, and the memo ought to be your

work. This week we will have section as usual. We'll be focusing on some of

models presented in today's class and last week's class. To keep

on track with the lecture material, there will be a problem set assigned this Thursday. We know you have a thing or two on your plates already, though, so this problem set will be lighter than the normal problem set. Congratulations, you've already cleared a huge hurdle in the replication process. Now all you have to do is generate a publishable paper. Piece

cake. Jenn

Greetings 2001, Now everyone who needs a replication assignment should have their replication assignment. A couple of notes: Everyone should have received a replication project who is either (1) writing a replication paper for the course, or (2) a distance student taking the course for credit. If you expected to receive a project to replicate but did not receive one, send me an email. Also, if something seems fishy, like you received a different replication assignment by email than in class, or you were assigned your own project to re-replicate, send me an email. If any information you need to replicate the replications is missing from the packet (the code, the writeup, etc.), contact the replication authors. Your assignment is to replicate the replications. Next Monday, April 7, you will bring to class (or submit to the dropbox if necessary) at least one hardcopy of a 1-2 page memo. The goal of the memo is to offer constructive feedback to the replication authors. Point out places where their code didn't work or where their work was unclear, or especially how they can improve the original papers. The one hard copy of this memo you bring to class will be the copy we grade. You should also give each of the replication authors a copy of the memo. You may give them either a hard copy or an electronic copy. Each person was assigned a replication project. Don't be confused if you were emailed along with another person or two- I was trying to be efficient in my tens of emails today. This is an individual project. That is not to say that you cannot work with others- discussing projects with others is a great way to find potential developments. But you are not required to work on this replication with your coauthors, and the memo ought to be your own work. This week we will have section as usual. We'll be focusing on some of the models presented in today's class and last week's class. To keep everyone on track with the lecture material, there will be a problem set assigned this Thursday. We know you have a thing or two on your plates already, though, so this problem set will be lighter than the normal problem set. Congratulations, you've already cleared a huge hurdle in the replication process. Now all you have to do is generate a publishable paper. Piece of cake. Jenn _______________________________________________ gov2001-l mailing list gov2001-l at lists.fas.harvard.edu http://lists.fas.harvard.edu/mailman/listinfo/gov2001-l

Hi John, Yes, that's right. If you can replicate everything without problems,

say so and move on. There's no need to reproduce tables in the memo. Jenn On Mon, Apr 7, 2008 at 1:02 AM, John Sheffield <john.sheffield at gmail.com wrote: > Hi Jen[n,s]: > > Do we need to replicate the relevant tables in our memo also? At least

> my case, not much code was necessary to replicate the replications

it's > well-commented anyway). If we can replicate all figures exactly, can

just > say so and move on? > > Hating hand-formatting LaTeX tables, > John > > On Tue, Apr 1, 2008 at 12:20 AM, Jenn Larson <

> wrote: > > > Greetings 2001, > > > > Now everyone who needs a replication assignment should have their > > replication assignment. A couple of notes: > > > > Everyone should have received a replication project who is either

> > writing a replication paper for the course, or (2) a distance

taking > > the course for credit. If you expected to receive a project to

> > but did not receive one, send me an email. > > > > Also, if something seems fishy, like you received a different > > replication assignment by email than in class, or you were assigned

own > > project to re-replicate, send me an email. > > > > If any information you need to replicate the replications is missing > > from the packet (the code, the writeup, etc.), contact the

> > authors. > > > > Your assignment is to replicate the replications. Next Monday,

> > you will bring to class (or submit to the dropbox if necessary) at

one constructive > > feedback to the replication authors. Point out places where their

> > didn't work or where their work was unclear, or especially how they

> > improve the original papers. The one hard copy of this memo you

> > class will be the copy we grade. You should also give each of the > > replication authors a copy of the memo. You may give them either a

> > copy or an electronic copy. > > > > Each person was assigned a replication project. Don't be confused

> > you were emailed along with another person or two- I was trying to

> > efficient in my tens of emails today. This is an individual

That > > is not to say that you cannot work with others- discussing projects

> > others is a great way to find potential developments. But you are

> > required to work on this replication with your coauthors, and the

ought > > to be your own work. > > > > This week we will have section as usual. We'll be focusing on some

> > the models presented in today's class and last week's class. To

> > everyone on track with the lecture material, there will be a problem

> > assigned this Thursday. We know you have a thing or two on your

problem > > set. > > > > Congratulations, you've already cleared a huge hurdle in the

> > process. Now all you have to do is generate a publishable paper.

of