text:
This document is meant to be a quick introduction to docker, and will cover the basic architecture, challenges, managing containers and images, and through to building and running a static website on docker.

[TOC]

## Slides

This document only contains the show-and-tell portion. Architectural overview slides can be found [here](https://github.com/ripta/decks.js/blob/master/intro-to-docker/index.html).

If you'd like to follow, you'll need access to a docker host.

## Installation

If you don't have anything setup on your OS X machine, expect to download about 200 MB of data, though the exact amount depends on what prerequisites you already have on your machine.

**I highly recommend the CLI way.**

Doing so requires more time to get up to speed and deals with lower level commands. While there's more to learn, I think it's more useful in the long run to know the concepts behind new technology, how to operate it, and how to fix things should they break.

The GUI way is easily, but abstracts away most concepts. If things go haywire—especially considering that docker isn't the simplest of technologies and that the GUI isn't mature (yet), they *will* go haywire—you're better off learning from the ground up.

### The CLI Way (Recommended)

On OS X, you'll need a hypervisor, e.g., VirtualBox, VMWare Fusion, or Parallels Desktop. If you don't have one already the easiest way to go is by using Homebrew.

This portion assumes you already have Homebrew installed and running.

Install the `caskroom` extension to homebrew if you haven't already, which will allow you to install Application binaries from the command line:

```
$ brew update
$ brew install caskroom/cask/brew-cask
```

Install one of VirtualBox (free and recommended by *Docker, Inc*), VMWare Fusion (not-free, but Ripta's preference), or Parallels Desktop:

```
$ brew cask install virtualbox
$ brew cask install vmware-fusion
$ brew cask install parallels-desktop
```

Get the `docker` client, `docker-machine`, and `docker-compose`:

```
$ brew install docker docker-machine docker-compose
```

We won't be using `docker-compose` today, but it can be used to define and run multiple containers as one unit.

### The Easy, GUI Way

In August 2015, Docker, Inc. announced the release of [Docker Toolbox](https://www.docker.com/toolbox), which provides a one-click install for the docker client, docker machine, docker compose, a hypervisor, and a front-end GUI.

I won't be covering the GUI way.

## Create New Machine

Now that you have a hypervisor and the docker command line tools installed, we can start our first docker host.

It doesn't matter (at least not at this point) the directory from which you issue these commands.

I'm going to first create a new docker host running on VMWare. I'll name it `intro`, but you can choose any name you'd like; a name that resembles a hostname would be a good candidate, because it will actually be used as the hostname of the docker host:

```
$ docker-machine create -d vmwarefusion intro
Creating SSH key...
Creating VM...
Starting intro...
Waiting for VM to come online...
To see how to connect Docker to this machine, run: docker-machine env intro
```

If you're running on a different hypervisor, you'll need to lookup the driver name under the `--driver` option in the output of:

```
$ docker-machine create -h
```

It should take a minute to boot up your new docker host; longer if `docker-machine` needs to download the images, which it will do automatically.

Once your docker host is running, you'll now have a set of environment variables needed to access the new docker host:

```
$ docker-machine env intro
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://172.16.241.137:2376"
export DOCKER_CERT_PATH="/Users/rpasay/.docker/machine/machines/intro"
export DOCKER_MACHINE_NAME="intro"
```

Evaluating the output of the above command will set your terminal up:

```
$ eval `docker-machine env intro`
```

After setting up the environment variables, your `docker` client will now have access to your docker host (and docker instance running on said host).

As with all git-like CLI, `docker help` should get you started. A useful command is `docker info`, which provides information about the host:

```
$ docker info
Containers: 0
Images: 0
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 0
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.0.9-boot2docker
Operating System: Boot2Docker 1.8.1 (TCL 6.3); master : 7f12e95 - Thu Aug 13 03:24:56 UTC 2015
CPUs: 1
Total Memory: 996.2 MiB
Name: intro
ID: YK3Z:WC3H:AV2M:UZQC:5GXE:V7OK:CYZW:7HOH:RRJM:SDFJ:YYJY:RIW3
Debug mode (server): true
File Descriptors: 9
Goroutines: 16
System Time: 2015-09-14T02:59:59.584647298Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
 provider=vmwarefusion
```

Of note in the output are:

* number of containers, which are separate "things" running;
* number of images, which are snapshots of things that *could* be running, stored on disk;
* storage driver, which determine *how* images are stored on disk, usually **aufs** (advanced multilayered unification filesystem); and
* the kernel version running on the docker host.

The version of docker client (running on your local machine) and server (running on the docker host) can be retrieved using:

```
$ docker version
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): darwin/amd64

Server version: 1.8.1
Server API version: 1.20
Go version (server): go1.4.2
Git commit (server): d12ea79
OS/Arch (server): linux/amd64
```

Obviously, my client version is a little outdated. Not a problem in this case, but if you can, I'd recommend running the same version.

**Aside:** You'll probably never need to do so—and in fact, doing this could mess up your setup if you don't know what you're doing—however, you can access the docker host itself using `docker-machine ssh intro`. When inside the docker host, the amount of space available to your AUFS mount, which is used for images is useful to know. There are options under `docker-machine create` to expand this size if you're building a lot of images.

## Finding Images

Official images maintained by Docker, Inc are available under the `library` username:

```
$ docker search library
```

Alternatively, open [https://hub.docker.com/r/library/](https://hub.docker.com/r/library/) in your browser. Tags show different versions of images in the repo, and also the image size.

While it may be a matter of preference on which image to use as a base, I prefer smaller, slimmer base images: you can fit more per host and it's more portable. I've found Alpine Linux to be a good balance between size and feature.

One reason for a larger image is if it contains management tools. It's up for debate, but some folks have advocated for treating images as full OSes, each with potentially its own ssh daemon, for instance.

Let's use the smaller `alpine` image for now:

```
$ docker pull -a alpine
$ docker images alpine
REPOSITORY      TAG             IMAGE ID            CREATED             VIRTUAL SIZE
alpine          2.6             6e25877bc8bc        3 months ago        4.502 MB
alpine          2.7             c22deeac7b13        3 months ago        4.711 MB
alpine          3.1             878b6301beda        3 months ago        5.041 MB
alpine          3.2             31f630c65071        3 months ago        5.254 MB
alpine          latest          31f630c65071        3 months ago        5.254 MB
alpine          edge            5e704a9ae9ac        3 months ago        5.31 MB
```

Multiple tags can point to the same image ID, e.g., 3.2 and latest above.

### Running Container

Running a container with alpine v3.2:

```
$ docker run -i -t alpine:3.2 /bin/sh
```

where `-i` keeps STDIN open even when we're not attached to the container, `-t` allocates a pseudo TTY, and `/bin/sh` being the init process to run inside the container.

Inside shell, the hostname of the container corresponds to the container ID:

```
/ # hostname
3747ada8f970
```

There aren't many processes running. In fact, `/bin/sh`, init process (PID 1), is the only thing normally running:

```
/ # ps -ef
PID   USER     TIME   COMMAND
    1 root       0:00 /bin/sh
   11 root       0:00 ps -ef
```

This is important to note, because just like a full-blown OS:

1. when the init process exits, the container stops;
2. the init process should be prepared to own any orphaned processes; and
3. the init process should be prepared to reap any adopted processes.

We can also view disk and memory usage:

```
/ # df -h
Filesystem                Size      Used Available Use% Mounted on
none                     18.2G      1.6G     15.6G   9% /
tmpfs                   498.1M         0    498.1M   0% /dev
shm                      64.0M         0     64.0M   0% /dev/shm
tmpfs                   498.1M         0    498.1M   0% /sys/fs/cgroup
/dev/sda1                18.2G      1.6G     15.6G   9% /etc/resolv.conf
/dev/sda1                18.2G      1.6G     15.6G   9% /etc/hostname
/dev/sda1                18.2G      1.6G     15.6G   9% /etc/hosts
tmpfs                   498.1M         0    498.1M   0% /proc/kcore
tmpfs                   498.1M         0    498.1M   0% /proc/timer_stats

/ # free -m
             total         used         free       shared      buffers
Mem:           996          379          617          112           13
-/+ buffers:                366          630
Swap:         1108            0         1108
```

Because we have not restricted resources on the container, it has access to all the host's resources.

You can also view routing information:

```
/ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 02:42:ac:11:00:01 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:acff:fe11:1/64 scope link
       valid_lft forever preferred_lft forever
```

Try making a curl request to `ifconfig.co`, which returns your public IP address:

```
/ # curl ifconfig.co
/bin/sh: curl: not found
```

Thankfully, Alpine Linux comes with a lightweight package manager: apk.

```
/ # apk update
/ # apk add curl
```

After much output, you'll hopefully have `curl` available to you.

```
/ # curl ifconfig.co
12.174.123.130
```

Awesome. Let's exit the container (`exit` works, as does `C-D`).

Let's start a new container using the same image:

```
$ docker run -i -t alpine:3.2 /bin/sh
/ # curl ifconfig.co
/bin/sh: curl: not found
```

Note, however, that curl is no longer available to us. It's important to note that when a container is run from an image:

1. Changes inside the container is invisible to any other container running the same image.
2. Changes to the image is not automatically kept.

**Observations:**

1. Once created, images are read-only. When a container is started using an image, a writable file system is created on top of the read-only image (thus, references to filesystem layers when doing a `docker pull` and the use of AUFS as a backing store to docker).
2. A command, `docker commit`, exists to create a new image based on changes introduced by a container. See its help page for information.

## Listing Containers

If you issued `docker ps` while a container is running, you'll see an entry for every running container in its output. However, `docker ps` only lists running containers.

When I exit the running container, it can still be queried with `-a`:

```
$ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                          PORTS               NAMES
3747ada8f970        alpine:3.2          "/bin/sh"           23 minutes ago      Exited (1) About a minute ago                       sick_einstein
```

Image and container IDs go hand-in-hand and are both 64-character identifiers, but refer to different objects.

## Restarting Containers

You can restart a stopped container, after which it will show as running again:

```
$ docker restart 3747ada8f970
3747ada8f970

$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
3747ada8f970        alpine:3.2          "/bin/sh"           34 minutes ago      Up 2 seconds                            sick_einstein
```

However, it runs the container in detached mode, meaning that no TTY is allocated against it. You could manually attach to a running container using:

```
$ docker attach 3747ada8f970
/ # %
```

Keep in mind that when you attach to a container, you are now interacting with its init process. Depending on the process, interrupting it (`C-C`) could kill the process and stop the container.

When you exit the container, it once again becomes stopped. Stopped containers always appear in `docker ps -a` and are not automatically removed. You can remove it manually using `docker rm`:

```
$ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                     PORTS               NAMES
3747ada8f970        alpine:3.2          "/bin/sh"           35 minutes ago      Exited (0) 3 seconds ago                       sick_einstein

$ docker rm 3747ada8f970
```

## Detached Containers

Because containers exit when the init process exits, the init process would need to be foregrounded. Take for example a forever process that loops and prints "Hello World!" once a second:

```
$ docker run alpine:3.2 /bin/sh -c 'while true; do echo "Hello World!"; sleep 1; done'
```

However, doing so keeps a terminal occupied. We've seen how to restart a container in detached mode, but when running a new container, the answer would be to explicitly detach the container with `-d`:

```
$ docker run -d alpine:3.2 /bin/sh -c 'while true; do echo "Hello World!"; sleep 1; done'
032b0875083eadcc20c21987ffbb04ca4c6b0f7dd89d1740ea5e4be0ea9ea583

$ docker ps
CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS               NAMES
032b0875083e        alpine:3.2          "/bin/sh -c 'while t   2 minutes ago       Up 3 seconds                            reverent_engelbart
```

Viewing logs, both STDERR and STDOUT, which are still separate streams:

```
$ docker logs 032b0875083e
$ docker logs -f 032b0875083e
$ docker logs -f -t 032b0875083e
```

Viewing all running processes:

```
$ docker top 032b0875083e
UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD
root                1906                1530                0                   05:09               ?                   00:00:00            /bin/sh -c while true; do echo "Hello World!"; sleep 1; done
root                2009                1906                0                   05:10               ?                   00:00:00            sleep 1
```

Stopping a container (`docker stop ID`) sends a SIGTERM, while (`docker kill ID`) sends a SIGKILL. It's up to the init process on how it handles these signals; hopefully predictably.

## Removing Containers

Docker doesn't provide one command to remove all containers, but this should get you going:

`docker ps -a -q | xargs docker rm`

**Notes:**

1. This command will attempt to remove *all* containers, regardless of whether they're running or stopped. Thankfully, docker will prevent you from deleting running containers; you'll just get a lot of warning messages.
2. The `-q` option will print out only the container ID column, without a column header. It's very useful for shell magickery, and many commands support this option.

## Sample Application

You can get the project from [https://github.com/ripta/dockerfell](https://github.com/ripta/dockerfell):

```
$ cd ~/Projects
$ git clone git@github.com:ripta/dockerfell.git
```

The repository contains several docker projects. The one you want is `nginx-static-test`:

```
$ cd dockerfell/nginx-static-test
```

You may wish to edit the `Dockerfile` to have your name and email address.

Once ready, build the image, giving it the tag `$DOCKER_HUB_USER/nginx-static-test:1.0`, where `$DOCKER_HUB_USER` is your docker hub username if you have one.

If you don't plan on pushing the image to docker hub later—and you don't have to—you can give it a local tag, e.g., `nginx-static-test:1.0`.

```
$ docker build -t $DOCKER_HUB_USER/nginx-static-test:1.0 .
Sending build context to Docker daemon 224.3 kB
Sending build context to Docker daemon
Step 0 : FROM alpine:3.2
 ---> 31f630c65071
Step 1 : MAINTAINER Ripta Pasay <ripta+docker@pasay.name>
 ---> Running in 4d28a4beff1f
 ---> 17b2ddda00c7
Removing intermediate container 4d28a4beff1f
Step 2 : ENV META_IMAGE_VERSION 1.0
 ---> Running in 10322b11c0a6
 ---> bc6ca695a5c7
Removing intermediate container 10322b11c0a6
Step 3 : RUN apk update
 ---> Running in eea0d955c8f2
fetch http://dl-4.alpinelinux.org/alpine/v3.2/main/x86_64/APKINDEX.tar.gz
v3.2.3-35-g583a384 [http://dl-4.alpinelinux.org/alpine/v3.2/main]
OK: 5295 distinct packages available
 ---> 517497e53894
Removing intermediate container eea0d955c8f2
Step 4 : RUN apk add nginx
 ---> Running in 1ed0c47d698a
(1/2) Installing pcre (8.37-r1)
(2/2) Installing nginx (1.8.0-r1)
Executing nginx-1.8.0-r1.pre-install
Executing busybox-1.23.2-r0.trigger
OK: 7 MiB in 17 packages
 ---> 10c88301b95d
Removing intermediate container 1ed0c47d698a
Step 5 : COPY . /usr/share/nginx/html/
 ---> 1bb05fedcd31
Removing intermediate container 01c1298bb966
Step 6 : RUN echo "Generated at $(date)" > /usr/share/nginx/html/VERSION
 ---> Running in 88287bcff994
 ---> 606891c0f07a
Removing intermediate container 88287bcff994
Step 7 : EXPOSE 80
 ---> Running in 64f4670e03c4
 ---> e1df01d77395
Removing intermediate container 64f4670e03c4
Successfully built e1df01d77395
```

You should have a new image, tagged with your tag, although the image ID will likely be different as you build at different times:

```
$ docker images
REPOSITORY                TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
ripta/nginx-static-test   1.0                 e1df01d77395        2 days ago          7.639 MB
```

Now try running nginx:

```
$ docker run -d -p 80 $DOCKER_HUB_USER/nginx-static-test:1.0 nginx
eedf6027be4bf66a20317265154ae857f4cae74ebab3d9ae151d61c20065d555
```

Even though you get a container ID, if you check `docker ps`, you'll notice that the container is not running.

Something is wrong, because the container has exited. What went wrong?

Let's spawn a shell against the image, and run nginx manually:

```
$ docker run -i -t $DOCKER_HUB_USER/nginx-static-test:1.0 /bin/sh
/ # which nginx
/usr/sbin/nginx
```

You'll notice that because the image already has nginx on it, we don't need to reinstall it.

```
/ # nginx
/ #
```

Looks like nginx got backgrounded. Uh-oh.

More importantly, if you're familiar with how processes are daemonized, you'll know that applications will frequently [fork or double-fork](http://stackoverflow.com/a/16317668), with the intention that the child process is orphaned, then adopted by the init process.

If you recall, the process we start is actually the init process. When the init process exits, *regardless of whether there are other processes running inside the container* or not, the container also exits, thus terminating all processes in the container.

So, you'll note that nothing has been started, because nginx is automatically backgrounded. If you refer to the nginx docs, you'll note the [`-g` flag](http://wiki.nginx.org/CommandLine), which allows you to [disable daemonization](http://nginx.org/en/docs/ngx_core_module.html#daemon).

Let's try that again:

```
$ docker run -d -p 80 ripta/nginx-static-test:1.0 nginx -g 'daemon off;'
e4359bc5905ee4432e38a109770efb44497aa6caf13c67d50ab90054ff781664

$ docker ps
```

You'll see docker's host port in the output of `docker ps` above. So how do we connect to it?

Normally, you would most likely know the IP address of the docker host. In our case, however, `docker-machine` provides a simple way to query the IP address of the docker host:

```
$ docker-machine ip intro
172.16.241.128
```

and if you have the container ID of the nginx container, you can retrieve the host's port that is mapped to the container port 80:

```
$ docker port e4359bc5905e 80/tcp
0.0.0.0:32769
```

To connect to the web server, use curl or open the URL in a browser, subtituting for the IP and ports above:

```
$ curl -i http://172.16.241.128:32769/
$ curl -i http://172.16.241.128:32769/VERSION
```

## Cleaning Up

You can stop your docker host using `docker-machine stop intro`, which will also stop all containers running in it.

Docker does not keep track of the state of the containers during shut down, and so it will *not* automatically restart containers when you start the docker host back up again using `docker-machine start intro`.

redpajama_set_name: RedPajamaGithub


This is a dainty 14k gold-filled initial necklace with choice of birthstone. The necklace comes with a small circular initial disc, a teardrop shaped birthstone and roundel birthstone. We have listed additional popular gemstone options too.
Model shown wearing July's birthstone ruby.
Measurements: 16" or 18". If you would like a shorter length than 16", please write in the notes section at checkout. If you would like a length longer than 18", please purchase here.
Please Note please type which initial you would like stamped on the disc in the 'Additional Notes' section at checkout.


text:
Die Liste der Filmfestivals in Afrika ist eine alphabetisch sortierte Übersicht über Filmfestivals in afrikanischen Ländern mit Angabe des Genres und des Austragungsortes.

Siehe auch
 Afrikanisches Kino
 Afrika-Filmfestival (in Belgien)

Afrika
!

en:List of film festivals#Africa

redpajama_set_name: RedPajamaWikipedia


What a perfect way to treat your Mum on Mother's Day!
Call the team on 01473 831263 or email team@amoe.co.uk to book your table!
Get in touch with the team on 01473 831263 or email team@amoe.co.uk to book your tickets!


text:
FBI to "give" 127 million dollars to the families of the parkland "school massacre victims", because the FBI failed
November 24, 2021 12:35 pm by IWB
The families of most of those killed and wounded in the 2018 Florida high school massacre announced Monday have reached a multi-million dollar settlement with the federal government over the FBI's failure to stop the gunman even though it had received information he intended to attack.
Attorneys for 16 of the 17 killed at Marjory Stoneman Douglas High School in Parkland and some of those wounded said they have reached a monetary settlement with the government over the FBI's failure to investigate a tip it received about a month before the massacre. The 17th family chose not to sue.
See also PFIZER EXECUTIVE GENOCIDE confession video has now +40 million views. Project Veritas CENSORED by Youtube. Shame on you, YT!
The attorneys said the settlement's details are confidential, but a person familiar with the deal said the government will pay the families $127.5 million overall
www.yahoo.com/news/florida-school-massacre-families-settle-221843556.html
See also Joe Biden tells families struggling to afford gas to buy a new car, and families struggling to afford food to buy a new refrigerator.
Tags dollars, families, massacre, million, parkland, school, victims Post navigation
Germany Rejects Merkel's Request for Lockdown
When Risk and Opportunity Become Personal

redpajama_set_name: RedPajamaCommonCrawl


text:
ManOnIce
Climate, Glaciology, Mountaineering, Photography
Seasons of Ice: Part 1 Spring
November 6, 2016 Noel Fitzpatrick 2 Comments
As Irish skiers go, I'm pretty average, which is to say, I'm a bad skier. I can survival ski down most things, but the grace and elegance that the residents of my current home display on the slopes still eludes me. The benefits of learning to ski before developing risk awareness is all too apparent.
This was on mind when talking over the phone with Ben Pelto (University of Northern British Columbia). Those of you who have read other posts on this blog will know that Ben and I regularly work together during our summer fieldwork campaigns on the glaciers of BC (see On Conrad Glacier: Part 1 and Part 2). It was January, and we were discussing plans for a spring trip to the mountains, specifically Conrad Glacier, to observe how the winter had treated the glacier, and to scout out locations for the coming summer's deployment of my weather stations. We were also planning to perform scans of the glacier using a ground penetrating radar (GPR), which would provide us with information on how thick the ice is, and the general shape of the underlying bed. This would all require some serious skiing.
Three months later, I am on a familiar road. With skis and camping gear in the back, I'm winding my way along the 750 odd kilometers from Vancouver to Golden, in eastern BC. Tonight, I'm meeting Ben and his sister, Jill, before an early morning helicopter flight to the ice.
Stopping off at Roger's Pass, en route to Golden.
Morning of departure at the Alpine Heli base, with Jill and Ben.
Happy for our mechanical problems to happen on the ground.
After a brief delay to fix a clogged spark plug, we were in the skies above the Purcell Mountains, in good flying weather. It was my first time taking this journey in what were essentially winter conditions, and I was glued to the window as we maneuvered between the snow-covered peaks. We landed on the west flank of Conrad Glacier at 2,300m. Our campsite overlooked the jagged crevasses of the icefall that lay above our summer field sites. We dug out level platforms in the snow for our tents, and built up walls on the upper side to keep out the cold, downhill 'katabatic' winds that can develop on glaciers at night. In the front vestibules, we dug out lower platforms for storing gear, and putting on our boots in the mornings. Finally, we dug out a table and benches, and pitched a tarp over it to serve as our kitchen.
Our mess tent. The option to get out of the elements for awhile to cook and eat can make all the difference.
One of the main goals for this trip was to get an idea of how much snow the glacier had received over the winter, and how much water this snow will produce if it melts in the summer. To this end, we needed to take regular measurements across the glacier of the depth of this season's snow, and its density. After setting camp on the first day, we skied down to the terminus of the glacier, and took a series of these measurements as we moved back up the slope. The weather was mild, and we were surprised to find a well developed melt water stream this early in the season, carving a channel into the surface snow. In the weeks preceding our trip, we had been keeping an eye on data from snow sensors located on mountains in this region. The early onset of spring was resulting in some significant snow melt, and the question on our minds was whether 2016 would prove to be as detrimental to the glaciers in this region as the record losses of 2015.
Late in the afternoon, with the weather beginning to turn, we pushed back to the shelter of our camp. After a warm meal, we watched the skies clear and felt the temperatures drop as the indigo twilight turned into a star filled mountain night.
Ben and Jill, ascending past an icefall on the glacier.
Ben, probing the snow depth to determine how much the glacier had received over the winter.
A well developed melt stream (supraglacial channel) was a surprise find this early in the year.
Returning to camp just as the weather began to close in.
Nights fall on our Conrad spring camp.
Day two saw the beginning of our radar campaign. Our objective was to ascend to the upper plateau of Conrad, taking measurements along the way. The GPR system consists of a transmitter, and a receiver, each mounted on skis, with antenna extending out in between. The transmitter sends out a pulse of energy that passes down through the ice, and reflects off the bedrock underneath. The reflected energy is detected by the receiver, and the time taken by the pulse to travel to the bed and back tells us how thick the ice is. That's the theory. The practical involves hauling this system over large swaths of the glacier, up steep slopes and icefalls, and around crevasses, trying to keep the system in line as much as possible. The relatively mild temperatures and strong sunshine made the hauling difficult, with the sleds prone to digging into the soft snow and tipping over. Despite this, we managed to cover significant ground with the radar, completing day trips of over 20km in some cases. Descending with the GPR was always an interesting experience, generally completed at the end of the day when we were returning to camp with already tired legs. We needed to act as brakes to stop the system from torpedoing down the mountain, requiring us to snowplow in our skis for kilometers downhill at a time, quad muscles screaming.
Ascending Conrad towards the upper icefall, with the GPR in tow.
Myself and Ben hauling the GPR across the stunning upper plateau of Conrad (Pic: Jill Pelto).
Shared slopes. We came across these wolverine tracks in the snow at 2,900m.
Cloud streams across the faces of the surrounding peaks.
Probing the snow depth as we moved up the glacier (Pic: Ben Pelto).
Completing a GPR survey on the glacier close to camp.
Our days on the glacier continued with combined snow depth/density measurements and GPR surveys. Working on the upper plateau of Conrad, the expanse of mountainous terrain around us was astounding. On every degree of the compass, snow covered peaks jostled for space on the horizon, like some jagged, storm blown ocean. A thought that keeps returning to me when working in these places, is what a privilege it is to be afforded such isolation and space in what is an increasingly crowded world. No traffic, sirens, voices, bleeping phones, or engines (apart from the occasional helicopter). To have access to the culture and community that living in a society provides is a great thing, but I am grateful for these opportunities to exist in solitude with nothing but survival and science to drive us on.
On one of our last days on the upper section of the glacier, we continued to record snow depth values to well over 3,000m elevation, and decided to push on to climb the summit of Mount Conrad; the peak which had loomed over us as we worked. We ascended on skies to within 50m or so of the 3,290 summit, before shedding our gear and scrambling the rock and snow of the final section. We climbed in beautiful weather (as had been the case for most of the trip; very unusual for Conrad), and our view from the summit was unimpeded in all directions. Turning from the summit, my thoughts were now fully occupied by the ski descent necessary to get off the mountain. The conversation I had had with Ben in January regarding my ski experience was echoing in my head as I clipped into my skis, and double checked my bindings. This was steep for me, but hesitating or leaning back would be the wrong option. I watched Ben and Jill drop in, took a solid breath, and followed.
Ben, checking some gear, on the ascent of Mount Conrad.
On the summit, looking south into Bugaboo Provincial Park; a climbing mecca I had visited a year previously.
My view from the top, prior to our ski descent.
On a very fun section of the descent back to camp. The beautifully symmetrical ski tracks are not mine (Pic: Ben Pelto).
Below the tumbled walls of one of the icefalls we passed through on the return to camp.
Light from a low sun highlights the textures of the glacier.
Back at camp after another rewarding day.
Ski boots that aren't your own can be unforgiving on long touring days, but it was little to complain about.
Looking north down the valley as the day ends.
Our spring visit to Conrad had been very successful, with a wealth of snow and ice thickness data recorded over much of the glacier. Throughout our travels , I had been scouting for potential sites for installing the weather stations in the summer; just two short months away. One would be deployed in a similar location to last year; lower on the glacier in the ablation zone (the area on a glacier where more ice/snow is lost than gained from year to year). The other would be a more ambitious venture. The upper plateau at 3,000m would provide a unique and intriguing location to gain information on the glacier's weather and melt relationships. It would also present a much harsher environment to operate in. Would we get a decent enough weather window to allow us to install the equipment (several days work), and if so, could the system withstand a season in tough and, as of yet, untested conditions? We would find out soon enough.
The moon sets behind Conrad as another day begins.
'What are men to rocks and mountains'? Ascending a western branch of the glacier.
BCBritish ColumbiaCanadaClimateclimatechangeClimbingGlaciersGlaciologyIceMountaineeringMountainsNaturePhDPhotographyResearchRockiesScenicScienceSkiingsnowUBCUniversity of British Columbia
Climate, Glaciology
On Conrad Glacier: Part 1
September 14, 2015 Noel Fitzpatrick 8 Comments
High on a mountain glacier, sheltering from a thunderstorm. With hail and wind buffeting the blue plastic tarp I'm clutching on to, and lightning cracking above, I realise that the boxes I'm sitting on contain several large high capacity batteries. My science teachers would be proud.
Four months earlier, I had returned to Vancouver from Svalbard, and an arctic winter that I will never forget. Touching down in YVR airport though, my mind was already on the list of ideas and tasks that would need to be tackled before fieldwork in July. My field campaign on Nordic Glacier last summer (see Notes from Nordic and Return to the Field) had been successful, but this season would present a whole host of new challenges. New glacier, new sensors, new objectives.
The overall goal of my project remains the same; to measure the weather conditions over a glacier surface, and to better understand how these conditions affect melt rates. One of the main differences for this year was that two stations would be installed on the glacier rather than one. The idea behind this is to see how weather and energy patterns vary across different points on the surface of the glacier, and how this in turn affects melting. This would mean a doubling of the number of sensors that would need to be prepared and tested.
Test set up of the two stations for the 2015 field campaign, on the grounds of the University of British Columbia (UBC).
Feeling like a roadie: some of the gear that makes up one station.
One of the (mostly) complete stations, in testing at UBC.
One of the more challenging aspects of last year's campaign was ensuring the station remained powered throughout the summer. The nature of mountain weather means that persistent cloud can prevent a solar power system from providing enough energy to the sensors. In addition to doubling the number of stations this year, each station was fitted with a new, power hungry system for measuring turbulent air flow (an important mechanism for transferring heat between the atmosphere and glacier). The upshot is that a total of 12 large boat batteries and 4 solar panels are required this time in the hope of keeping everything beeping and recording over the season.
Each station was fitted with two 140W solar panels.
Modifying the Pelican cases. Each of these cases will house 3 large batteries for powering the stations.
Packing up in the lab, on the night before departure.
This year's destination is Conrad Glacier, in the Purcell Mountains of British Columbia. I had visited Conrad at the end of last season to scout it out as a potential research site. Aside from its scientific merits, it is a beautiful part of the world; flanked by snow covered peaks, with forested valleys below and miles without engines. Named after Conrad Kain, a pioneering Austrian mountaineer who unlocked several first ascents in this area, the glacier is one of many in this region at risk of total disappearance. A recent study has forecast a 70% loss of BC's glaciers this century, with almost total deglaciation in this region. Apart from global consequences to sea level rise, the loss of a glacier is the loss of a large water reservoir, putting pressure on ecosystems and communities (who use the water for drinking, irrigation, and hydro-power) during dry periods like we've had here this summer.
Being just a short journey south from last year's glacier (Nordic), we would again base ourselves in the town of Golden prior to our flight into the mountains. After spending a day on the always spectacular drive from Vancouver to Golden, Valentina and I met up with Ben, a glaciologist from the University of Northern British Columbia (UNBC) who would be joining us. Over some excellent burgers, we also had the chance to catch up with Tannis and Steve, friends of ours who run a ski lodge in the area, and have been consistently helpful. The plan for the next day was to drive to a staging area in the foothills to the south of Golden, and get all our gear into the mountains in as few chopper loads as possible (with thanks as always to Steve for his expertise on this).
A van-load of science: hitting the road for Golden, BC.
At the staging site, waiting for the helicopter to take us to the glacier, with Steve, Ben, and Valentina.
Summer snow storm, clearing over Conrad Glacier
Directing in the first sling load for station 1 (photo credit: Ben Pelto)
Three helicopter flights (and some delays) later, all crew and equipment were accounted for on Conrad. Our campsite was just off the ice itself, on a rocky outcrop overlooking the glacier. The first evening was a battle against the weather to get tents set up in between heavy showers and gusty winds. Dinner was a simple affair, with everyone retiring to their sleeping bags early; sleep coming to the sound of fluttering tent fabric.
After breakfast the next morning, we set about finding the best route from camp on to the glacier; navigating the broken and crevassed ice along the glacier margin. Two locations had been selected for station 1 and 2 not far from camp. Each station would take about two days to install, with some additional time to prepare and secure everything for a season in the mountains.
Camp, overlooking the glacier on the western nunatak (rock outcrop).
Setting a safety rope for one of the sketchier sections of our route (photo credit: Ben Pelto).
Ben and Valentina drilling holes
The bones of a station.
Working my way through the sensors and wiring (photo credit: Ben Pelto).
The weather had a constant presence throughout the week, with wind, thunder and snow storms slowing the work somewhat, and making cooking a frigid task at the end of the day. Despite what felt like a cold spell to us, it was clear as soon as we saw the glacier that it was experiencing a warm season. In combination with low snowfall during the winter, warm temperatures had resulted in significant melt across the surface by the time we had arrived. Although close to what would normally be the beginning of the melt season, this year's snow had already completely melted up to the high regions of the glacier.
Ben, getting a drink from one of the many melt water streams on the glacier
Wiring the radiometer, which measures the incoming radiation energy from the sun and sky, and the outgoing radiation from the glacier surface.
Setting up the power system for one of the stations.
The brains of the operation. Wiring up the datalogger, which is programmed to store all the data from the station, and to tell the sensors when to take measurements.
Sheltering from another hail storm
With the stations coming together, Ben and I ventured higher up the glacier, and spent an afternoon installing ablation stakes. These stakes, installed along the length of the glacier, provided a record of how many meters of ice are lost or gained at the surface each year, and give an indication of the health or mass balance of the glacier (see Svalbard Part 2: Balancing Act). During the week on Conrad, Ben was also involved in carrying out a kinematic survey; using detailed GPS measurements to create a map of the glacier.
Ben, navigating a crevasse field.
Due to weather delays, the final tasks for installing the stations were completed in the last few hours of the trip. With the helicopter due to pick us up that afternoon, I got moving early on the last day, and headed on to the ice before dawn to shore up the last few pieces of equipment from the elements, and to make sure all the systems were behaving. In the end, two full weather stations were installed, along with a time lapse camera to monitor conditions over the season.
A completed station (solar panels out of shot). This was the lower of the two stations, at around 2,130 meters elevation.
Time lapse camera, for observing the weather conditions on the glacier, and for keeping track of changes to the surface and the stations themselves.
Loading the helicopter for the journey back to civilisation, and a warm shower.
It remains to be seen how the the glacier will respond to this year's melt season, and on a personal level, how all the equipment will perform. A good or bad field campaign will have a major impact on the timeline for my studies and on the goals I hope to achieve. As our chopper lifted off from our disassembled camp and sped down the valley, I took one last glimpse at the stations and the glacier itself, before my eyes turned to home and my mind to the plan for the next trip.
The sun dipping below the peaks on the western margin of Conrad Glacier.
A Note of Thanks: Just prior to leaving for field work, I received word that I was being awarded the Chih-Chuang and Yien-Ying Wang Hsieh Memorial Scholarship for research in Atmospheric Science. A sincere thank you to the Hsieh family. I was honoured to received it.
UP NEXT: The return to Conrad, and what we found.
BCCameraCanadaClimateclimatechangeConradcryosphereGlaciersGlaciologyGoldenIceMountaineeringMountainsNaturePhotographyResearchSciencesnowUBC
Climate, Glaciology, Mountaineering, Photography, Travel
Svalbard Part 6: Stories in the Ice
Gallery July 22, 2015 Noel Fitzpatrick 6 Comments
"There is no such thing as 'just' ice." Not to a glaciologist anyway.
Professor Doug Benn is recounting to us his reply to a reviewer who questioned his use of the term 'refrozen water ice'. While this may sound superfluous, the many variations in density, temperature, content, layering, and colour of glacier ice can tell us a lot about its history, and potentially, about it's future.
Prepping the Ground penetrating radar (GPR) on Longyearbreen. GPR is used in glaciology to look at the thickness and structure of a glacier. The GPR is towed across the surface, emitting pulses of energy which pass through the ice. These pulses bounce of the rock underneath the glacier, and are reflected back to the GPR, like an echo when you shout in a valley. The time it takes for this echo to travel back to the GPR tells us how far it has travelled, and hence, how thick the ice is. GPR can also be used to see if there are regions in the glacier that are 'warm' i.e. at its melting point, by reflecting off liquid water. The presence of these warm sections in a glacier can tell us about the glacier's present and past; how it moves, how it used to move, and how its behaviour has changed with time.
Examining the internal layering and structure of the ice on Larsbreen.
The network of tunnels visible here are formed by the movement of air bubbles in between ice crystals as freezing takes place.
A ship frozen in the sea ice, on the way to Tunabreen
Arriving at the calving front of Tunabreen. Calving is the processes by which chunks of ice break off at the end or 'terminus' of a glacier, forming icebergs. We were there during winter, when the sea was frozen. The sea ice acts as a temporary barrier to the glacier, slowing its forward movement, and preventing calving.
Tunabreen is a surge type glacier, meaning that its rate of flow or speed is not constant. Instead, the glacier may move very slowly or remain still for several years, before going through a period of faster flow, known as a surge.
A glacier prayer
Departing Tunabreen
Surge front of Paulabreen
The dark banding visible at the front of Paulabreen is evidence of its surging past. When the glacier was flowing more rapidly, large crevasses (cracks) opened up at the surface and spread downwards. Debris and dust fell into these cracks, and when the crevasses closed again as the glacier flow changed, dark vertical bands of debris mark their former location.
Better to light a candle: an arctic storm led to a power cut on the night before the final exam, leading to some creative lighting.
Morning view after an overnight snow storm
One last venture into the mountains before leaving the Arctic.
Summit ridge of Trollsteinen
Parting gift from Svalbard: dancing aurora on the flight south to Oslo
Glaciology PhDs: amazing experiences, zero glamour. Overnighting at Oslo Airport.
Flying over the enormous glaciers on the west coast of Greenland on my way back to Vancouver, and getting re-inspired for the next adventure.
ArcticClimateGlaciersGlaciologyIceNaturePhotographyPolarResearchsnowSvalbardUNISUniversity Centre in Svalbard
Climate, Glaciology, Photography, Travel
Svalbard Part 5: The beauty of the North
April 27, 2015 Noel Fitzpatrick 6 Comments
Some shots from a landscape that I hope we can continue to be inspired by. Click on the images to see them in high resolution. They still won't do the place justice, but it's a start.
Triple point
Frozen air
Polar bear tracks
ActicAuroraClimateGlaciersGlaciologyIceMountainsPhotographysnowSvalbard
Climate, Climbing, Glaciology, Mountaineering, Photography
Svalbard Part 4: To the icy core
April 3, 2015 Noel Fitzpatrick 10 Comments
A glacier is more than an ice cube. Rather than being solid, uniform blocks, glaciers can have incredible variations throughout in terms of structure, temperature, and movement. The surface and the base of a glacier can communicate with each other, and the language of this communication is water.
When ice and snow on the surface of a glacier melts, it can produce a lot of water. Streams of this meltwater flow over the surface of a glacier during the warmer months of the year. These streams can cut or 'erode' into the glacier, creating paths or channels which the water flows through. Over time, these channels can cut deeper and deeper into the glacier, their roofs closing over to create tunnels through the ice which can bring the meltwater from the surface all the way down to the bottom of the glacier. This is important because increasing the amount of water underneath a glacier can encourage it to slide faster.
During the cold winter months, melt channels are generally dry. We had explored one of these channels previously on Scott Turnerbreen (see Svalbard Part 2: Balancing Act), and decided that some more time under the ice was needed. There had been reports of an excellent ice cave on Larsbreen, a glacier within an hour's hike of Longyearbyen. So one Tuesday evening, with duties at UNIS finished for the day, Tom, Ellie, Jelte, and myself met on the outskirts of the village, and began the trek to the glacier. Our plan was to explore the cave for a few hours, and then being a bunch of idiots, to stay overnight inside the ice.
(A note on the images: the caves in the glacier were entirely dark, with our headlamps being the only source of light. Therefore, for me, much of the photography was experimental; playing around with shutter speeds, iso settings, and flashes, while avoiding damaging my camera too much when climbing and crawling. As always, click on images to see them in full resolution)
Nighttime in the mountains above Longyearbyen.
At the cave entrance, on Larsbreen.
The walls of the channel were lined with a huge variety of beautiful and delicate ice structures.
Glaciologist: defrosting.
By the light of the moon, we found the entrance to the cave; first squeezing into a tunnel down through the overlying snow to get into the glacier itself. The passage through the ice twisted, widened, and narrowed, like a desert rock canyon; in sections coated in fragile crystal structures, then changing to smooth, swirled patterned walls like polished marble. We followed the channel as far as we could go, descending through a series of levels and passages until we were forced to stop at a major drop; the location of what would have been a waterfall during the melt season. We picked a spot where we could roll out our bags for a few hours, and returned to the surface for some frigid air before sleep. On the way to the surface, I had a 'how did I get here' moment; crawling out of a glacier through a snow tunnel in the middle of the night, with a rifle on my back to watch out for polar bears, and being greeted by the northern lights.
Our home for the night: a cosy ice chamber inside the glacier.
Student accommodation in the Arctic can be grim
My choice of sleeping spot, or as it became know as, the 'MRI machine'.
Our night in the glacier was a memorable experience, but it felt like the caves had a lot more to show us had we been willing to push a little further. A few days later, we returned to Larsbreen. Armed with ice climbing gear, Tom, Andi, and myself would attempt to work our way down some of the larger drops that had stalled us on the previous visit, and see how deep we could get.
Descent was carried out through the use of ladders, fixed ropes, and rappels for the longer drops.
Climbing my way up through an ice chimney.
Tom, about to drop over the edge of the first rappel section, which was extremely narrow.
Close to the base of the glacier, looking upwards through the section we had just rappelled down. The dark bands in the ice are layers of debris and sediment (rock and soil) that has been picked up by the glacier as it moved along the valley floor.
Getting narrow…
Wide. We reached the base of the glacier to find a cathedral of ice.
Crawling through an R channel (a tunnel cut into the bottom of the ice by a stream running along the bed), with the entire glacier above our heads.
(photo: Andi Alex)
End of the line. The channel eventually became too narrow for us to proceed further.
Belaying Tom up the last pitch of ice climbing (photo: Andi Alex).
Back on the surface, and being watched by a distant reindeer (photo: Andi Alex).
We found the bed of the glacier, and it was an awe inspiring experience to have this entire mass of ice lying above us. My thanks to my like-minded companions on both trips for their company; the highlight of being in such incredible places is to share it with great people.
ArcticcavesClimateClimbingFeaturedGlaciersGlaciologyIceIce ClimbingLongyearbyenPhotographysnowSvalbardUNISUniversity Centre in Svalbard
Mountaineering, Photography, Travel
Svalbard Part 3: In search of Sun
March 6, 2015 Noel Fitzpatrick 8 Comments
The Sun has been absent since I've arrived here in Longyearbyen. The islands are deep inside the Arctic Circle; the line of latitude north of which it is possible to have 24 hour nights in winter. But Spring is fast approaching.
When a ray of sunlight was spotted hitting the mountain tops on the other side of the fjord, it was decided that a group of us would aim to get as much elevation as possible over the weekend, and try to catch some elusive light. Temperatures would remain well below -20°C over the two days, so warm clothes and moving fast would be essential.
Saturday morning saw us hiking up to Sverdruphamaren; an elevated plateau to the west of Longyearbyen. There is a real sense of wilderness here, and the view is an expanse of white peaks, sea ice, and reindeer. The sun however, remained just below the higher mountains to the south.
Setting out from Longyearbyen on Saturday morning
Ice mascara
The Svalbard Cold Feet Dance
Some opted just to get their feet off the ground altogether.
Chasing the sun across Svalbard's wilderness
Returning back across the plateau after a cold but beautiful day
On Sunday morning, we aimed higher, and set out for Trollsteinen; the peak behind which the Sun had hidden from us the previous day. With temperatures at sea level forecast to be around -30°C, we knew we were in for a cold summit. Our route would bring us south of Longyearbyen, up the glacier of Larsbreen, before ascending onto the main ridge of the mountain. The winds were calm, and the skies were perfectly clear, promising excellent views, and potentially some vitamin D.
Heading south, with Longyearbyen in the distance
Lone hiker on Larsbreen
Beginning to ascend towards the ridge
The Sun! The end of polar night, as viewed from the main ridge of Trollsteinen
The Sun is literally days away from reappearing here in the valley, and the community of Longyearbyen will mark its return this weekend with a festival in its honour. It's certainly something worth celebrating, but I'll still be happy to experience a few more Svalbard nights.
The Aurora over Longyearbyen
ArcticAuroraIceLongyearbyenMountainsNorthernLightsPhotographyPolarReindeersnowSunSvalbardUNISUniversity Centre in Svalbard
Glaciology, Photography, Travel
Svalbard Part 1: Arrival in the Arctic
February 18, 2015 Noel Fitzpatrick 18 Comments
It's a matter of latitude. 78° 13′ N; approximately twelve degrees, or 1,334 kilometers north of the Arctic circle. This is the realm of twenty four hour nights and days, of the Aurora Borealis, of polar bears, of windswept landscapes of snow, sea ice, mountains, and glaciers. It's a part of the world I've wanted to experience since I was a kid, and it's the place I'm going to for the next six weeks.
My destination is Svalbard; an archipelago of islands in the Arctic Ocean. I'm taking part in a glaciology program run by the University Centre in Svalbard (UNIS), which is located in the regional capital of Longyearbyen. Sixty percent of Svalbard's surface is covered by glaciers, making it an ideal location to study their processes.
The first leg of my journey takes me from Vancouver to Oslo, where I have an overnight stay before my flight to Longyearbyen. The stopover gives me a chance to join up with a friend who is also taking part in the glaciology program. I met the aptly named Aurora last summer in Alaska (see North to Alaska), and catching up over some much need food that night, we're both equally excited about the trip ahead. The next morning, we soak up the last sunrise we'll see for a few weeks, and board our flight to the Arctic.
Touchdown at Longyearbyen Airport, Svalbard.
Arriving in Longyearbyen just after 1pm, the usual bustle for hand luggage when the plane stops takes on a more practical air. Down jackets, balaclavas, and mittens are being pulled on before the exit door is opened. Stepping out into the blue semi-darkness, we are greeted by a biting wind that draws streams of fine snow across the tarmac. It's already below -20°C, and I couldn't be happier.
The following are just some initial shots from my first few days here, including some from the training we underwent. As always, images can be clicked on to view in full size. More updates coming soon.
Protect our glaciers. Rifle handling is an important component of the safety training at UNIS, but is very rarely drawn upon. Temperatures on this evening were around -25°C, adding the additional challenges to target practice of bulky gloves and shivering.
Flare testing
Snowmobile training
Dog team
Reindeer calf
Mountains and sea ice
A wild day
Shelter in a storm
ArcticGlaciersGlaciologyLongyearbyenPhotographySvalbardUNISUniversity Centre in Svalbard
Gallery November 16, 2014 Noel Fitzpatrick 10 Comments
Some shots from a recent drive along the Icefields Parkway, a 230km stretch of road through the center of the Canadian Rockies.
Waterfowl Lake
Peyto Lake
Columbia Icefields
CanadaPeytoPhotographyRockies
Climate, Glaciology, Photography
Return to the Field
October 13, 2014 Noel Fitzpatrick 7 Comments
Waiting at the gate at Anchorage Airport, my phone beeps to life. I had spent the last two weeks in Alaska, without phone or internet coverage, and was looking forward to having a little time off back in Vancouver before the end of the summer. My phone disagrees.
A few short days later, I'm sitting behind the wheel of a pick up truck on the road to Golden, and Nordic glacier (see Notes from Nordic). 740km of driving solo in one afternoon was certainly a first for me. This isn't surprising when you consider that I come from a country that can be crossed three and a half times in that distance. It is quite a road though; the landscape constantly evolving between mountains, forests, and arid plains. Back at the airport, I had received a backlog of emails advising me that a research team from the University of Northern British Columbia (UNBC) were planning to travel to Nordic earlier than expected. Before leaving for Alaska, the plan had been to return to the glacier in mid September in order to dismantle and collect my equipment. Now, if I wanted to get back to my station this season, I needed to be on the helicopter flight tomorrow morning.
I made it into Golden after dark, with the silent flashes of distant thunderstorms hinting at what the weather would have in store for us. Once again, I was being hosted by Tannis and Steve (of Sorcerer Lodge), and was grateful for a place to sleep that night. A short drive to the helicopter early the next morning, and we were on our way back into the mountains. We were a group of five; Rob Vogt and Ben Pelto from UNBC, Bob Sawyer, Steve, and myself.
Click on images to enlarge. Due to a technical issue, the images in the first half of this article (from Nordic) were not taken with my usual camera, and are of a lower quality.
Autumn had arrived in the mountains, and we experienced some significant snow showers.
The last I had seen of my station had been in early July as we were flying out after installing the equipment. Thoughts of failed power systems, wiring mistakes, and crevasses opening underneath had been frequently on my mind in the intervening period. They were certainly on my mind that morning as Steve and I hiked up to the glacier. Ascending a ridge of ice, I could see emerging above me the rotating propeller of the wind sensor on the top of the station. So, it was still standing at least. As we approached closer, I could hear the low hum of one of the sensors, meaning power was still being supplied. So far so good. A quick check of the data logger (device for storing the measurements from the sensors) showed no obvious gaps in the data. More serious investigation would be left for the lab back in Vancouver, but I was delighted with that much.
When designing each aspect of the station (see The Project), the fact that the glacier surface would be constantly melting and changing was always kept in mind. Seeing the change in reality, however, after such a short period of time was still a shock. Equipment that I had installed while crouched on my knees was now towering above me, stranded high on 4 meter poles that had been fully submerged in the ice 48 days previously.
An example of the changes observed on the surface. The above image shows the camera mount on the day it was installed (July 11th). The mounting poles were drilled 4 meters into the ice. The image below shows the camera mount on returning to the glacier on August 28th. (This image is taken from a different angle and from further away).
It took a day and a half to dismantle the station, and to pack everything up for transport out by helicopter. It would have taken significantly longer without Steve's assistance throughout. With the last minute nature of this trip, I had thought that I would be tackling the station on my own, and I would probably be still up there trying to extract frozen pipes had that been the case.
Preparing the sling load for transporting the equipment out by helicopter.
I had been really curious (and nervous) to see how the camera had performed over the summer (see A Camera for all Seasons). For one reason, it would be a really useful source of information when it came to examining the data. Also, as I had built it, I would have no one to blame but myself if it hadn't worked. Opening the case back in the lodge that night, the camera passed the first test; it switched on. Quickly checking through the pictures, the most recent image had been taken just a few minutes earlier as I was taking off my boots. Overall, the camera performed well, with just one day where it failed to shoot (looking into that). I've stitched the images together into the short timelapse video below, to give an idea of the changes taking place.
The camera box, just prior to me opening it to see if it had worked.
(Best viewed in full screen and HD)
On the third day, I joined Rob, Bob, and Ben (seriously), and assisted with their work on the glacier. In order to monitor the loss or gain of ice over the glacier surface (known as it's mass balance), a common method is to drill a series of stakes along the central line of the glacier (usually every 100 meters of elevation). These 'ablation' stakes are inserted deep into the snow or ice, with just their tops emerging. The stakes are visited at the same time the following year, and the change in the level of the glacier surface relative to the stake is measured. We spent most of the day installing stakes, and also a sensor in one of the streams emerging from the base of the glacier, to monitor temperature changes of the melt water.
Rob, using an ice auger to drill a hole for an ablation stake. Depending on elevation and the expected amount of melt, holes were drilled between 3 and 7 meters deep.
A temperature sensor was installed in this melt water stream, emerging from the base of the glacier.
All about the angles. This huge crevasse and snow bridge were only visible when we came around the far side. During the winter, it is concealed by snow.
I had agreed to stay on after the work on Nordic, and to assist Ben and Bob with an ablation stake campaign on Conrad Glacier. I was also interested in assessing Conrad (also in the Selkirk mountains) as a potential location for installing a station next summer. Between flying down from Nordic and setting out for Conrad, we had a couple of enforced rest days. Low cloud meant that visibility was too poor for the helicopter, so we hung out in Golden, and Steve took us around some of the local mountain bike trails.
Rain delayed. Waiting at the airport for a break in the weather. Cloud in the valleys was preventing us from taking a helicopter to Conrad glacier.
A window of clear skies two days later gave us a few hours to fly to Conrad, and set up camp. The following are some images from our time there, and of the work we were involved in.
Conrad glacier, as seen from our camp. Although heavily crevassed along its margins, once this section was navigated, the main truck was relatively solid.
Preparing dinner as the sun sets.
Home in the mountains.
Morning reflection.
Ben, preparing the GPS locator, which would facilitate the airborne LiDAR scanner in producing a digital map of the glacier.
Gaining access onto the glacier.
Navigating bands of lateral crevasses.
Drilling boreholes into the ice, with depths of up to 6 meters, for installation of ablation stakes. On Conrad, we installed stakes every 100 meters or so of elevation.
Ice falls of a tributary glacier.
The skull of a mountain goat at the base of Conrad glacier.
Returning back after a day on the ice, we found one of the tents flipped by the wind, and only moments away from being blown off the cliff on to the glacier below.
Come to carry us home. Bob signaling the location of the landing spot to the approaching pilot.
Boots off the ground
I really enjoyed my time on Conrad. With my own project wrapped up on Nordic, I was better able to connect with the landscapes around me. This was wilderness; rock, ice, water, and weather, with little to distract from it. With night temperatures below zero, and winds that spoke of snow, it was clear that the summer was ending, and it was a beautiful location to bid it farewell for this year. The last day was an epic. We rose at 6 to piercing blue skies, and spent the morning installing the remaining stakes higher up on the glacier. We returned to break up camp, and were picked up by helicopter at 3. It was 5:30 before I was pulling out of Golden, with the drive back to Vancouver ahead of me. Arriving at the University shortly after 3am, I unloaded the equipment as quickly as possible, and was thankful that my running in and out of the building with expensive equipment did not alert the suspicions of security.
Night shift. The truck, finally unloaded, after an epic day.
The main purpose of the field work was to obtain data. So in some ways, the work is really only beginning, and will continue throughout the winter, in the office and the lab. This summer's campaign was just the first of several before the research questions of my PhD can, hopefully, be answered. However, a PhD can be filled with lots of missteps and wrong turns, so it's important to recognise and appreciate when things go well. A solid first step. One down.
CanadaClimateFeaturedGlaciersGlaciologyIcePhotography
Gallery August 25, 2014 Noel Fitzpatrick 10 Comments
At the beginning of August, I was fortunate enough to take part in the International Glaciology Summer School, in beautiful Alaska. The school is run every two years, directed by Regine Hock of the University of Alaska Fairbanks, and brings together students and instructors from all over the world. Based in the Wrangell mountains, in the old mining village of McCarthy, the school provides an opportunity to learn from experts in a range of fields within glaciology, and perhaps more importantly, provides a platform to engage with and get to know others embarking on research in the science. The 10 days of the course were some of the most enjoyable of my academic career, and I left inspired by the enthusiasm and curiosity of my peers.
Below are images from some of the activities that took place outside of the classroom (click on images to enlarge).
Hitting the road from Fairbanks to McCarthy, and aiming for the mountains.
The drive to McCarthy took 11 hours, but it was broken up with regular stops.
The Trans-Alaska pipeline crosses the entire state, north to south, from Prudhoe Bay to Valdez, stretching over 1,200km.
Not a popular decision. In reality, the salmon at this point have traveled so far inland from the sea (to reach spawning grounds) that they have lost much of their mass, and are not suitable for consumption.
Hanging out under bridges.
Home for the next 10 days
McCarthy's old hardware store, now operated as the Wrangle Mountain Center, was our base for the summer school.
Tools of the trade. An unconventional poster session.
Friday night softball in McCarthy.
Passing Kennicott mill, where ore from the surrounding copper mines was processed in the early 1900s.
Mike in action. The expanse of what looks like gravel in the background is actually the lower reaches of the Kennicott glacier; the ridges are composed predominately of ice, coated with a thin layer of debris. The material comes from the lateral moraines of numerous tributary glaciers that have merged with the main trunk of the Kennicott, higher up the valley.
Footprint of a moulin. Debris carried downwards by water is deposited at the bottom of the moulin. When the overlying snow and ice melts (and the moulin collapses), the ice covered by this material melts slower than the surrounding exposed ice, resulting in these ridges.
Glaciologists in their natural environment.
Holding court
Descending into a temporarily empty lake basin. This lake, along the margin of the Root glacier, can fill or drain in a day; the water flowing through subglacial channels.
What lies beneath a glacier?
The blue room. I spent longer crouched in a subglacial river than is probably recommended, but it was a hard place to leave.
Having seen all there is to see on the surface of a glacier, Colin decides to check out a moulin (not really; don't do this).
Outlets were a commodity when power was available.
A group of us took advantage of the landing strip in McCarthy, and arranged a flight over the surrounding glaciers and mountains.
The debris covered terminus of the Kennicott glacier. The village of Kennicott can be seen along the right margin.
Further up the Kennicott, medial moraines are visible as dark bands on the surface, and are formed by the merging of several tributary glaciers (and their lateral moraines).
Medial moraines and incredibly blue melt water pools.
Glacial ogives.
Rock glacier.
Trail run up to the old Bonanza copper mine, in the mountains above McCarthy (phone pictures).
A very fuzzy picture of a black bear encountered during the run.
Fire and ice.
Obligatory moose, with calf (I was driving at the time).
AlaskaClimateFeaturedGlaciersGlaciologyMcCarthyPhotography
On Conrad Glacier: Part 2, and life since
Lengthening shadows on Lake Garibaldi
Noel Fitzpatrick on The Parkway
Maureen Maughan on The Parkway
Noel Fitzpatrick on Seasons of Ice: Part 1 Spring
eamonfitzpatrick on Seasons of Ice: Part 1 Spring
Seasons of Ice: Part… on On Conrad Glacier: Part 2, and…
Glaciology
Glaciology, Climate, Travel, Mountaineering, Photography
Follow ManOnIce on WordPress.com
© Noel Fitzpatrick and ManOnIce.com, 2014. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given with appropriate and specific direction to the original content.


text:
NCL calls on insurers to cover air medical services during COVID-19 crisis
May 5, 2020 /in Consumer policy, Consumer Protection, Featured Home - Consumer Protection, Featured Home - Your Health, Health, Health policy, Healthcare coverage, Transportation Issue Statements, Press Releases /by Melody Merin
Contact: National Consumers League – Carol McKay, carolm@nclnet.org, (412) 945-3242 or Taun Sterling, tauns@nclnet.org, (202) 207-2832
Washington, DC –The National Consumers League (NCL) last week sent a letter to the CEOs of Cigna, Aetna, and UnitedHealth Group, urging them to enter into productive negotiations with air medical service providers to ensure coverage of emergency air medical transportation. The ask comes as the COVID-19 pandemic spreads across the country, making air medical services even more essential, particularly in rural America.
In its letter, NCL notes that it is increasingly concerned about emergency air medical access during this crisis, and that it believes this life-saving care should be covered by every insurance plan. NCL asks that insurers review the robustness of their coverage policies and immediately to enter into network negotiations with air medical providers so that this critical service is covered, and patients are never left with a bill they cannot pay.
Text of the letter, signed by NCL Executive Director Sally Green is below:
Dear Mr. Wichmann, Mr. Cordani, and Ms. Lynch:
The National Consumers League has long advocated for health care as a right and argued for fair treatment for all stakeholders across the health care spectrum – patients, physicians, hospitals, health plans, and health care providers. Our mission is particularly acute during the global COVID-19 pandemic, when medical professionals are on the frontlines fighting for our health and safety, stricken patients need life-saving care, and nearly everyone is focused on their health and that of their loved ones.
In this vein, we are increasingly concerned about access to emergency medical care, especially in rural America, as the virus indiscriminately makes its way across the country. When minutes count, Americans who fall victim to COVID-19 must be assured that they can get to the nearest, most appropriate medical facility as quickly as possible. As COVID-19 strains hospital capacity and critical medical equipment like ventilators become attenuated, emergency air medical transports between facilities are often the only way for patients to get the care they need.
According to the Centers for Disease Control and Prevention (CDC), 85 million Americans can only reach a Level 1 or Level 2 trauma center within one hour if they are flown by an air medical helicopter. The effects of this access problem are staggering, and even more pronounced as we wrestle with the COVID-19 crisis. For many Americans, air medical ambulances are a vital link to timely, life-saving care.
We believe that such life-saving care should be covered by insurance. Patients pay their monthly premiums – and copays and deductibles – so they are not bankrupted should the worst befall them or their loved ones. Unfortunately, there have been far too many stories of people who were transported by air ambulance because it was ordered by a first responder or doctor, only to be told later by their insurance company that they would have to shoulder the bulk of the cost. This should not be the case anytime, but especially now as our nation wrestles with a pandemic.
This explains why we at the National Consumers League are writing to you for your input and thoughts. We believe that emergency air medical transportation should be included in every health coverage plan. We think that insurance companies and air medical providers must work together to bring these services in-network, so patients are not left footing a bill they can never hope to pay. Adequate network agreements are imperative so that patients are not told – after the fact – that they were transported by an air ambulance that was not in-network. When an emergency happens, or worse yet, a pandemic strikes, patients are not choosing whether to take an air ambulance, let alone choosing a particular provider. Similarly, coverage denials based on "medical necessity" should be the exception, not the rule, in light of the fact that patients are not a part of the decision-making process.
We ask that your companies immediately take a comprehensive look at your coverage policies for air medical services and the robustness of your provider networks. We urge you and the air ambulance community to enter into network negotiations, take patients out of the middle, find a middle ground on reimbursement that fairly compensates both sides, and ensure rural communities have access to air ambulance transports. Refusing to fairly negotiate is simply not an option in light of the current crisis. Entering into productive negotiations immediately will ensure that patients across the country have access to the medical care they need and that they are simultaneously protected from balance bills.
Thank you for your attention to our concerns.
Sally Greenberg
About the National Consumers League
The National Consumers League, founded in 1899, is America's pioneering consumer organization. Our mission is to protect and promote social and economic justice for consumers and workers in the United States and abroad. For more information, visit www.nclnet.org.
https://nclnet.org/wp-content/uploads/2020/08/NCL-logo.png 0 0 Melody Merin https://nclnet.org/wp-content/uploads/2020/08/NCL-logo.png Melody Merin2020-05-05 15:58:002021-02-23 10:47:07NCL calls on insurers to cover air medical services during COVID-19 crisis
Safe takeout options under coronavirus
COVID-19 shows us the extraordinary importance of vaccines
Nation's pioneering consumer-worker organization demands massive COVID-19 testing production, universal testing
Protecting consumers from COVID-19 Scams: A virtual panel event with Pennsylvania Attorney General Josh Shapiro and fraud experts
Watchdog org predicting 'tsunami' of coronavirus-related scams to come
COVID-19, what could it cost you?
A few out-of-the-box consumer tips for staying safe from coronavirus
Universal testing: What is the hold-up?
NCL: Annual in-office eye exams help diagnose potential problems More tips for staying healthy during the COVID-19 outbreak and beyond


Cartoon flowers coloring pages - is not only coloring pages with flowers from cartoons. Here we collected different pictures. Some of them are really from cartoons but some is just cartoon style coloring pages. It's just a subcategory of Flowers coloring pages. Enjoy.


Excessive sweating usually occurs in people who are otherwise healthy. The problem commonly starts during childhood or adolescence and is a life-long condition. Heat, nervousness and anxiety can trigger or aggravate sweating and it can also appear without any trigger or reason.
Should Excessive Sweating be treated?
Excessive sweating causes awkward social situations as one may be dripping with sweat and have difficulty holding a pen or even gripping a steering wheel. Sweating also stains clothes and ruins dresses. Sufferers in extreme cases may even avoid shaking hands to avoid embarrassing situations. Treating hyperhidrosis normalizes the patient's quality of life and minimizes many of this social awkwardness.
Commonly available treatments include over-the-counter antiperspirants (commercial or medical), oral medications, tap water iontophoresis, Botox injection and surgery.
Iontophoresis uses tap water to conduct a mild electrical current through the skin's surface. It's not entirely understood how or why iontophoresis works but it works for a fair number of patients. When it works, one has to continue with the treatment 2-3 times weekly to maintain its effectiveness.
Are there any oral treatments for Hyperhidrosis?
The most commonly used oral medications is a type of medication that works by blocking nerve signalling. Although the majority of patients will respond to it, there are minor tolerable side effects that may develop, which include dry mouth, blurred vision, urinary retention and constipation. Hence, the patient needs to be aware and notified.
How does Botulinum Toxin injection help to stop sweating?
Botulinum toxin stops the sweat production by blocking the nervous system from reaching the sweat glands. A very effective midterm solution to sufferers, Botulinum toxin treatment for excessive sweating is an outpatient treatment that can be completed in less than an hour. This treatment can be done on palms, underarm, forehead, cheeks, nose or any part of the body. Each treatment can provide relief for about 6-10 months and it is carried out painlessly by Dr Wong under numbing cream or local anaesthesia. For some patients, the improvement can even last longer than a year.
A special type of surgery can be carried out that will provide long term solution to the problem of excessive sweating, only in armpits and hands. It involves cutting or clipping a specific nerve near the neck area that controls the sweating. However, a side effect is that other parts of the body may sweat in excess and this is known as compensatory sweating.
Body odour is determined largely by secretion from the apocrine gland in the skin. Odour also arises from dried sweat on clothes or may originate from metabolic disorders, ingestion of foods or drugs. There are marked individual and racial variations in body odour and excessive sweating or poor hygiene often aggravates it. Medical and dermatological conditions associated with excessive sweating or overgrowth of bacteria (eg, obesity, diabetes mellitus, fungal infections) may be contributory causes of body odour as well.
Good hygiene and use of commercial antiperspirants may help. Botulinum toxin is also able to provide relief from this embarrassing condition because it stops excessive sweating, reduces the moisture, bacteria activity and hence, the bad odour.
Dr Wong Soon Tee is a MOH accredited Dermatologist for more than 20 years. Consult Dr Wong for effective non-surgical treatments of your sweaty palms and underarms now. Call Assurance Skin Clinic at +65 6694 1121 for an appointment.


text:
{% extends 'layout/base.html' %}
{% load crispy_forms_tags thumbnail staticfiles %}

{% block main_content %}

Actualizar información del producto

        <form style="display:none;" action="{% url 'store:upload-product-image' product.slug %}" method="post" enctype="multipart/form-data">
            {% csrf_token %}
            <input id="id_logo" type="file" name="image" />
        </form>

            Change

{% crispy form %}

{# <form method="post" action="{% url 'store:product-update' product.store.slug product.slug %}" enctype="multipart/form-data"> #}
    {# {% csrf_token %} #}
{# {{ form.name }} #}
{# {{ form.description }} #}
{# {{ form.quantity }} #}
{# {{ form.category }} #}
{# {{ form.price }} #}
{# {{ form.tags }} #}
{# <input type="submit" name="submit" value="Update product" class="btn btn-primary" id="submit-id-submit"> #}
{# </form> #}
{% endblock main_content %}

{% block js %}

{% endblock js %}


text:
Snibe Shines at Medica 2019
Medica, known as the world's largest trade fair for medical technology, was held in Dusseldorf, Germany, from November 18th to 21st.
Every year, more than 5.000 exhibitors present their latest products and ideas at Medica. With the 108sqm spectacular exhibition stand (Hall 1 D39), Snibe also brought the latest innovations to the exhibition, which once again attracted the attention of many visitors.
The most eye-catching products of the exhibition were undoubtedly one of the world's fastest CLIA system, MAGLUMI X8, and SATLAS-TCA, a lab automation solution launched in a grand collaboration between Snibe and Thermo Fisher, which combines high throughput, flexibility, and scalability, highlighting Snibe's large scale and strong strength.
During the exhibition, remarkable reagent menus and typical products including MAGLUMI 800 and MAGLUMI 2000 from chemiluminescence immunoassay system, Biossays 240 Plus from biochemistry system, also attracted lots of professional audiences, showed their keen interest in the powerful clinical test platform of Snibe and came to learn details.
As a leading brand of Chemiluminescence Immunoassay solution from China, Snibe has been focusing on CLIA solution for 24 years and has exported its products to more than 145 countries with 12,000 units installed. Warmly welcome to join Snibe, developing together and realizing win-win strategy together!
See you in Medica 2020!
Previous :Snibe Shows Great Charms at 71th AACC
Next :Snibe Showcases Total Lab Automation at MEDLAB 2020