On Tuesday, I’ll talk about the Serial Harmonic Grammar paper. Please read it if you haven’t already. I’ll mostly focus on elaborating on points that are made only in passing in the paper itself. I can still make some final changes to the paper, so if you spot any infelicities, typos, mistakes, etc. please let me know!
At the end of the class, Emily asked whether we might talk on Thursday about how one goes from theory to experiment. That’s actually going to be a recurrent theme throughout the course, so instead of trying to figure out how to talk about it on Thursday, let’s instead keep it in mind as we read papers, which will give us concrete examples around which we can build our discussion. I’ve written some initial thoughts about this on the page “Theory to Experiment”.
So my suggestion for Thursday is that we do some work using OT-Help 2. This should help meet the goal of better understanding serial HG/OT, as well as moving us toward a public release of the software. If at least a couple people would commit to trying to implement something in HS, we should easily have plenty to talk about. As I mentioned in class, one possibility would be to look at the relationship between the languages generated with JJM’s files in OT and HG.
Please post a comment if you’d be willing to do tell the rest of us about some OT-Help 2.0 explorations, and let us know roughly what you’ll try!
To get started in Ot-Help 2.0, try using the files that JJM and I have created. A few quick notes (we know we need to write a manual). You can use built-in, and user-defined constraints. In my files, I use the built-in Parse constraint, which penalizes each character (letter?) not surrounded by parentheses. Markedness constraints get defined in the constraint files, faithfulness in the operation files (though they also need to be in the constraint files). Operations take a regular expression as input, and output a string (not a regex itself). See JJM’s notes on the way that these transformations can be set up.