“And That Concludes Our Presentation”…

Graduates

Graduates From j.o.h.n. walker’s Flickr photostream

When we ask students what drives them crazy, they sometimes respond that they wish we had given them a packet describing everything they would have to do to graduate.

There is, and we do tell them. The thing here is continuity of service. They start getting these packets from day 1, before they even sign on to the college. Some things are verbal, some things are written. All get repeated.

The problem with being a student is the continuity. Most students don’t realize that the program that they are in is fluid, so students admitted the year before and students admitted the year after may well have a different curriculum and requirements.

This shocks students. It is their education, it seems to the students that it is a giant monolithic event, one unchanged path towards a degree. Yet for faculty and administrators the curriculum and requirements are a fluid space, different for almost every year.

So back to continuity, how do we take the two perspectives and bring them into one place, where students are satisfied and faculty understand. Students should allows have access to a forward and backward look across their own curriculum and requirements, but currently that takes some work to figure out.

Yes, I can hear you thinking, as a school we already have allot of this functionality, but we don’t use it.

The Rx system we use here, or really, any portfolio system could be used this way, students get a pre-formatted space when they arrive. Pre-formatted in the sense that their handbook goes from a dead pdf online to a more interactive space that they (the student) fill with their grades and accomplishments, as it fills, they can check items off and see how close (or far) they are from reaching their goals, that year, that rotation, ultimately graduation.

Tough request, but there are places were we could do a better job. Since students get packaged by “year of entry” we could probably use the same system as is in place now, but we would improve the continuity for the student by moving it to a live space online where they could look at it when they are ready.

We tell them everything they will have to do in the beginning of their first year, but all they hear is “and that concludes our presentation”. Towards the end they ask us what is it that they have to do and are they almost done, but all we hear is our own perspective whispering, “they didn’t listen”.

That is the divide that we have to cross.

Network Backup From Time Machine

Now being one of those “jump first and realize what I did later” people, I jumped into a server upgrade confident of my ability to restore from a Time Machine Backup. Our setup here is a Drobo FS and a few headless Mac Pros. Now all of this seemed reasonable to me, and as might be expected the upgrade from the 10.7 server to 10.8 was a complete failure since I couldn’t for the life of me, drag across the wiki. So, after struggling for some time I acquiesced and decided to restore from my backup.

Right…

It turns out that restoring from a NAS like the Drobo FS is not as straight forward as hoped. I popped in the install usb that I carry around and dropped into the restore form Time Machine option and off the software went to search and search, and search.

Nothing. No networked backups appeared. So it was off to Google and this solution by Urban Toronto. Oddly or perhaps predictably, terminal saves the day… again.

So next time, just so I remember:

Create a mount point on the target disk:

 mkdir /Volumes/TimeMachine

Mount the network share to this newly created volume:

mount -t afp afp://YourDroboFSAdminUserName:YourDroboFSAdminPassword@IPAddressOfDrobo/YourDroboTimeMachineShareName /Volumes/TimeMachine

Finally mount the actual image of your Time Machine backup to make its contents readable:

hdid /Volumes/TimeMachine/yourMacsTimeMachineFile.sparsebundle

If you don’t know the name of your sparsebundle image, just cd into your /Volumes/TimeMachine directory and use ls to look it up.

Fighting Leukemia By Reprograming T Cells

Some really fascinating work is being done to save leukemia patients who have reached the end of conventional therapy without a cure. Detailed in a NEJM article here, the treatment takes the patients own T cells and reprograms them, targeting the cells to attack the patients own B cells. The reprogramming is done using an HIV derived vector that integrates its DNA payload into the genome of the hosts T cells.

The New York Times has a couple of good writes-ups on this. At the time of this post, this is the most recent.

Chemists Outrun Laws in War on Synthetic Drugs

What does similar mean?

This is where Brandon Keim starts in a post on a chemists ability to churn out legal analogues of illegal compounds.

The question is a good one for medicinal chemists, policy makers, and emergency room clinicians, but all for different reasons.

Chemists Outrun Laws in War on Synthetic Drugs | Wired Science | Wired.com.

I think this will make a good first lecture for the my toxicology students, framing the unusual mix of stakeholders when we discuss abused drugs.