Coach Thrasher
Regatta Report: River City
Regatta Date: March 18, 2006
Men's Entries: V8+, V4+, N8+, N4+ A, N4+ B
Course: 2000m, straight, 4 lanes
Course: 1000m, straight, 4 lanes (novice 4s, shortened due to deteriorating conditions)
Conditions: variable winds 10-25mph, light to medium chop, from port/port-stern
Results: (official results to be posted soon)
Saturday was a "learning" day out at River City. Our varsity eight had a really bad race. On reflection, we discussed several points that we could improve upon. Briefly they are:
1) Site preparation/rigging was rushed. We need to identify a game plan for getting boats off of the trailer, and appoint a "trailer captain" to guide this process.
2) Coxswain was a sub. Our normal coxswain had previously arranged to miss this regatta. We knew this, but didn't get another coxswain involved in our race plan until about 15 minutes before launching. Ideally, we could have had the sub row with us at practice to better familiarize everyone with what the plans were. As it was, Carolina did a great job on short notice.
3) We raced other team's race, not our own. We had just changed our start sequence in practice and were nervous about executing for the first time at this event. We didn't know what to expect, but we did know we'd beaten other crews that we were racing - so we didn't expect to be behind. As it was, we were behind on the start, and tried to keep the rate up and out of control for the body of the race. We were letting other crews dictate our race strategy because we were shaken on the start.
4) Given the windy conditions, we should have used a lower rate. This condition needed to be made on the course, since the conditions weren't apparent from the land. The best rate for our crew in those conditions would have been around a 32.
5) We effectively used lessons from the V8+ to have a better race in the V4+.
The varsity 4+ race went much more smoothly. From the start, through the body of the race, and through the final sprint from the bridge, the crew reported everything went more smoothly. In particular, the start went very well. There were actually two starts: 1) a false start and alignment issues, and 2) the final start that went smoothly. These went over well despite never practicing our new start in the 4.
Our parents and boosters supplied a great selection of healthy food for lunch, along with picking a great site for race viewing along the shore. I also got to know Joan (and her son Troy) from Delta. They have a similar program to our guys - this is their second year as well, and they are developing their program. We spoke of planning a regatta on April 8 at Delta (in Stockton, CA) since the Oakland folks have double-booked their venue.
Posted at 12:21PM Mar 19, 2006 by jason in Rowing | Comments[3]
CruiseControl for Firefox
How did it take me so long to find this: CC plugin for FireFox. It's a nifty at-a-glance view of CC build status! YAY!
Posted at 06:40PM Mar 14, 2006 by jason in Software | Comments[0]
jetspeed-2 build notes
I've been trying to get Jetspeed-2 up and running for a few days now. I had it up and ready to go with the Apache site's quick-install guide, but now it's time to do some real customization. To get customized, I'm trying to build it from svn sources, here are my notes to make it happen, which were non-trivial by reading jetspeed's docs, and related svn docs for 2.0.1.
I had to be root in order to build jetspeed-2 because the maven plugin tries to write to the $MAVEN_HOME directory to install the j2 plugins. I found that even if I ran a build to install the plugin as root, then changed back to my regular account, it still tried to re-install maven plugins. You can get around this by avoiding root-only access to maven, but I like to have common tools installed and controlled by root only.
1) get the "stable" source branch:
cd ~/dev
svn co http://svn.apache.org/repos/asf/portals/jetspeed-2/branches/JETSPEED-BRANCH-2.0.1 jetspeed-2
2) get and install IzPack:
wget http://download.berlios.de/izpack/IzPack-install-3.8.1.jar
java -jar IzPack-install-3.8.1.jar
[run the installer]
cp $IZPACK_DIR/lib/standalone-compiler.jar ~/.maven/repository/izpack/jars/standalone-compiler-3.6.1.jar
3) write a build script "~/dev/jetspeed-2/jason_j2_build.sh" to control what's going on (WARNING: change exports to match your system):
#!/bin/bash
#
# setup the Jetspeed-2 environment for building, and fire away
# from http://wiki.apache.org/portals/Jetspeed2/QuickstartForTheImpatient
#
export JAVA_HOME=/usr/java/java
export JRE_HOME=$JAVA_HOME/jre
export MAVEN_HOME=/usr/java/maven-1.0.2
export CATALINA_HOME=/usr/java/tomcat
export JETSPEED2_SRC=/home/jason/dev/jetspeed-2
export ANT_HOME=/usr/java/ant
# update the path to put maven 1.0 first
export PATH=$MAVEN_HOME/bin:$PATH
export JAVA_OPTIONS="-Dorg.apache.jetspeed.server.home=$CATALINA_HOME -Dorg.apache.jetspeed.server.shared=$CATALINA_HOME/shared/lib -Dorg.apache.jetspeed.deploy
.war.dir=$CATALINA_HOME/webapps -Dorg.apache.jetspeed.services.autodeployment.user=j2deployer -Dorg.apache.jetspeed.services.autodeployment.password=j2deployer -Dorg.apache.jetspeed.catalina.version.major=5.5 -Dorg.apache.jetspeed.project.home=$JETSPEED2_SRC -Dant.home=$ANT_HOME"
# Build the Maven plugin
maven $JAVA_OPTIONS initMavenPlugin
# Clean all, build all, and create documentation (allSite is optional)
maven $JAVA_OPTIONS allClean allBuild allSite
# Set up and deploy Jetspeed and the demo portlets
maven $JAVA_OPTIONS j2:quickStart
4) Run the build script, and go eat lunch for ~30 minutes.
./jason_j2_build.sh
Posted at 02:48PM Mar 10, 2006 by jason in Software | Comments[0]