- About XNAT
- News & Events
- XNAT Marketplace
- Contact Us
Washington University School of Medicine
|Time||Day 1: Administration||Day 2: DevOps||Day 3: Computing||Day 4: Programming||Day 5: Impromptu Topics|
|8:00||Check-in and Breakfast||Breakfast||Breakfast||Breakfast||Breakfast|
|9:30||Installation and Basic Use
|XNAT Under The Hood
Tim Olsen/Rick Herrick
XNAT at Scale
Rick Herrick/Tim Olsen
XNAT staff available to
|1:00||Practical Session 1: Administration||Practical Session 2: Backend Administration||Practical Session 3: Computing||Practical Session 4: Programming||No practical|
|Guest Talks||Guest Talks||Guest Talks||Adjourn|
|6:00||Suggestion: Shakespeare in the Park||
Urban Chestnut Grove Brewery & Bierhall
Suggestion: Shakespeare in the Park
(take Metrolink to Civic
Center and 9 min walk from there)
Step 1: From the airport, get onto a Metrolink Train heading eastbound.
Step 2: Getting around the Central West End.
Exit the Metrolink platform and go up the stairs on the western end of the platform. This will put you in the center of Washington University School of Medicine / Barnes-Jewish Hospital campus. Here is a Google Map that highlights Workshop locations, hotels and recommended restaurants in the area.
Step 3: Feeling adventurous?
St Louis has Uber, which makes it easy to get around and explore the city in relative safety. Here are some neighborhoods and attractions that you may be interested in:
Step 4: Going Home
Simply reverse your steps in Step 1, with one important detail: Get on a Westbound Red Line train. Way-finding on Metrolink platforms is not very good, compared to most other mass-transit systems. Be sure to be watchful for a train with red signage displaying "Lambert Airport" as its final destination.
Hard Drive: At least 40 GB of free hard drive space available, SSD preferred for performance
Processor: 2 gHz and up recommended
RAM: 8 GB and up recommended
Many of the practical sessions and hackathon sessions presume the use of Vagrant to create virtual machines that run the XNAT application. The XNAT team has created a Vagrant base box that has many of the services required to run XNAT already installed, greatly reducing the time required to build new instances. This is the xnatstack Vagrant base box. You should download and install this base box before leaving for XNAT Workshop 2016: this is a fairly large download and will be even slower if all attendees are trying to download it at the same time on the same wireless connection!.
To download the box, run the following command:
vagrant box add nrgxnat/xnatstack-ubuntu1404-docker --provider virtualbox
This will download the base box and cache it in your Vagrant data folder.
You can check for available updates to the xnatstack Vagrant base box by running the following command:
vagrant box update --box nrgxnat/xnatstack-ubuntu1404-docker
Taking care of this ahead of time will leave you more time to focus on the important parts of the sessions and practical exercises. If for some reason you don't get it downloaded ahead of the workshop, don't worry – we'll have it available on USB thumbdrives when you arrive.
You can also download the XNAT Vagrant base box by creating a new Vagrant project that references the box, then creating a VM instance from that project. Run these commands to do this:
$ vagrant init nrgxnat/xnatstack-ubuntu1404-docker $ vagrant up
The first command creates a very basic Vagrantfile. After deleting all the comments in that file, you're left with this:
Vagrant.configure(2) do |config| config.vm.box = "nrgxnat/xnatstack-ubuntu1404-docker" end
When you run the vagrant up command, this will reference the Vagrantfile and create a new virtual machine based on the XNAT base box.
If you want to further configure your virtual machine, you can have a look at the Part 1 Installing XNAT practical session documentation or use the XNAT Vagrant project to automate a great deal of the setup and configuration.
We have documented several common (and a few uncommon) problems that Windows users have run into with installing and using Vagrant. Running Vagrant from Cygwin or MobaXterm will likely help. Here are some more helpful hints: Troubleshooting XNAT Vagrant Installation for Windows Use. We highly recommend running through the Vagrant's "Getting Started" sequence before the Workshop to make sure you're able to run Vagrant on your local machine.