Halo with parhelia

circular (22 degrees? anyone want to verify that, picture taken with Samsung S4 mini) halo with parhelia at 3 oclock and 9 oclock.


Jakob halvmaraton

Without much training and without any time goal I participated in the Jakob half-marathon.

Up to 10 km things went smoothly. Then the steady uphill towards 11 km felt quite tough, although I sort of kept up the pace until about 14 km. From there it was a fight with a bit of walking now and then... The steady slow-down towards the finish shows in my 5k splits: 26:23, 27:25, 28:51, and 30:16. For comparison in 2012 on this course my 5k splits were: 23:47, 24:17, 24:20, and 24:09 - very steady and not slowing towards the end.

Here's a chart with the min/km times from the half-marathons I've run.


Next year I must remember to do one or two 90-120 minute training runs per month and things will go much smoother...

Thursday 100k

First 100+ k ride this year! A bit of rain in the middle and a steady headwind as usual :)

Torino, Italia

I'm in Torino for the School on Optical Clocks, and some work at INRIM.

Piazza vittorio veneto to the left, the river Po in the middle, and the bridge vittorio Emanuele I to the right.


Olympic Arch

20150705_145255 - 20150705_145321_fused

Samsung galaxy S4 mini phone + hugin panorama creator.

Kiintorastit Solvalla

Another run on the Solvalla map with fixed controls. Last one was in April.

Problems on the second control (#50) where at first I didn't know exactly where on the dashed path I had come down from the hill, and then inside the control circle I looked for stones north up the hill when the control-stone was lower down in the forest.


NTP stratum-1 on Ubuntu 14.04LTS

Some (incomplete) notes on setting up a stratum-1 NTP server on Ubuntu 14.04LTS

To handle the upcoming leap-second we want a leapfile, from: http://www.ietf.org/timezones/data/leap-seconds.list

The path of the leapfile goes into /etc/ntp.conf
leapfile /etc/leap-seconds.list
But Ubuntu uses apparmor, so we must grant permission for the ntp service to read this file in /etc/apparmor.d/usr.sbin.ntpd by adding:
/etc/leap-seconds.list r,
To make apparmor parse and apply the new rules we do:
sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.ntpd
when the ntp service starts it is useful to look at /var/log/syslog where ntp will complain if it doesn't have permission to read the leapfile or if it is badly formatted.

Now let's edit the default options for the ntp service in /etc/default/ntp by adding:
(-N runs ntpd at highest priority, -g makes it more robust agaist large time offsets, see man ntpd)

To get time in NMEA-format and a pulse-per-second (PPS) from gpsd we add two shared-memory (type 28) refclock drivers to /etc/ntp.conf

# GPS Serial data reference
server maxpoll 3
fudge time1 -0.230 refid GPS

# GPS PPS reference
server prefer maxpoll 2
fudge refid PPS

(the time1 adjustment number needs to be calibrated somehow..).

Finally we let ntp distribute time to the outside world by adding this line to /etc/ntp.conf (this is usually at the end of the file).
restrict default noquery

Now let's set up gpsd. The service configuration file is /etc/default/gpsd, and as suggested in the file we edit it with the utility:
sudo dpkg-reconfigure gpsd
The options that worked for me are device /dev/ttyS0 and options -n (don't wait for clients to connect). After running the utility /etc/default/gpsd should look something like:


You can verify that gpsd is working with cgps, xgps, or gpsmon.

This should result in Ubuntu automagically starting gpsd and ntpd in the correct order at bootup, and ntpq -p should show something along the lines of:
Screenshot - 06262015 - 10:18:31 AM

If you want to manually restart (or just start or stop) the services, required e.g. after any changes are made to /etc/ntp.conf, it is done with
sudo service ntp restart
sudo service gpsd restart

CONT vs RCON mode on the 53230A frequency counter

This is a follow-up to my earlier notes on the 53230A noise floor.

Naively I did the initial frequency-counting tests using READ?, which is wrong both because it produces data with dead-time and because the consensus for what is meant by Allan deviation assumes pi-counting.

Driven by marketing, no doubt, the 53230A employs internal averaging (something akin to lambda-counting) both with the simple READ? command and the continuous CONT mode mentioned in the manual. Amazingly you have to use the undocumented RCON mode to get pi-counting which will produce correct Allan deviations.

Here is a plot. The opportunity for making errors (with pi- vs. lamda-counting, and gap-free data) is less in time-interval mode, and I have indicated the 12 ps RMS noise floor (1.8e-11/tau in terms of Allan deviation) with a black dashed line. In RCON mode the noise floor has the same 1/tau dependence and I get about 3e-11/tau. If however you simply use the built-in settings of the counter with READ? or CONT you get a noise floor of about 2e-12/sqrt(tau) due to the internal averaging going on behind the scenes.


For a paper that explains pi- and lambda-counting see Dawkins2007 (fulltext PDF on ReaserchGate). Enrico Rubiola also has notes on counters.

Datafiles and script for ADEV and figure: 2015-06-18_rcon_cont.zip


Big mistake on #9, where I stopped at the wrong cliff/hill, and the control was just to the right, but I did a big loop left before realizing this.

Otherwise mostly OK going in terrain that was much easier to run in compared to 2014 in Kuopio.


Itärastit Paloheinä

Last itärastit event for this spring. See you again in August.

Probably also last orienteering practice before Louna-Jukola next weekend.


#2 found the correct ditch but passed close by the flag before turning around to find it. +2 min.

#9 ran too far along the road and passed close to #4 before turning towards the control.

#15 nothing much wrong but still a bad split. straighter through the green apparently is faster.

Länsirastit Kellonummi

Long boring runs along roads followed by slow climbing up and down stony steep hills.


© 2015 anderswallin.net

Theme by Anders NorenUp ↑