Visiting relatives in Texas, just like last spring. Very distant relatives. And this happened:
Here’s the culprit, with his sidekicks Monorail Badger, Trashbag Tortoise, and Kas-Tor, Last Beaver of Krypton. A disreputable bunch.
The victim. Some call him the Winter Cervical. He was fast, strong–and he had a metal arm…ature.
Meanwhile, in the back:
March 24, 2014
Here’s a working version of that link.
- Falkingham (2012) on photogrammetry for free
- Mallison photogrammetry tutorial 1
- Mallison photogrammetry tutorial 2
- Mallison photogrammetry tutorial 3
- Mallison photogrammetry tutorial 4
- Powell, Jaime E. 2003. Revision of South American Titanosaurid dinosaurs: palaeobiological, palaeobiogeographical and phylogenetic aspects. Records of the Queen Victoria Museum 111: 1-94.
March 21, 2014
When Fiona checked her email this morning, she found this note from our next-door neighbour Jenny:
I seem to remember Mike wanting a mole – I do hope so because I’ve left you a body on your patio in a cereal box!
Cheers Jen x
What a delightful surprise! And here it is:
And a close-up of that awesome digging hand:
I don’t have time to deal with it properly right now, so it’s gone into a plastic box with some small holes in the lid, where I will trust invertebrates to do my work for me — as they did to great effect with the juvenile baby rabbit whose skeleton I must show you some time.
The end-game here is of course to obtain a complete skeleton; but if not that, then at least the upper-arm bones. I’m on record as saying that next to sauropod vertebrae, mole humeri are the bones that move me most; and elsewhere I nominated mole humeri in response to John Hutchinson’s question, “what are the strangest animal bones (in form & function etc) that have ever been discovered?”
March 20, 2014
In discussion of Samuel Gershman’s rather good piece The Exploitative Economics Of Academic Publishing, I got into this discusson on Twitter with David Mainwaring (who is usually one of the more interesting legacy-publisher representatives on these issues) and Daniel Allingon (who I don’t know at all).
I’ll need to give a bit of background before I reach the key part of that discussion, so here goes. I said that one of David’s comments was a patronising evasion, and that I expected better of him, and also that it was an explicit refusal to engage. David’s response was interesting:
First, to clear up the first half, I wasn’t at all saying that David hasn’t engaged in OA, but that in this instance he’d rejected engagement — and that his previous record of engaging with the issues was why I’d said “I expect better from you” at the outset.
Now with all that he-said-she-said out of the way, here’s the point I want to make.
David’s tweet quoted above makes a very common but insidious assumption: that a “nuanced” argument is intrinsically preferable to a simple one. And we absolutely mustn’t accept that.
We see this idea again and again: open-access advocates are criticised for not being nuanced, with the implication that this equates with not being right. But the right position is not always nuanced. Recruiting Godwin to the cause of a reductio ad absurdum, we can see this by asking the question “was Hitler right to commit genocide?” If you say “no”, then I will agree with you; I won’t criticise your position for lacking nuance. In this argument, nuance is superfluous.
[Tedious but probably necessary disclaimer: no, I am not saying that paywall-encumbered publishing is morally equivalent to genocide. I am saying that the example of genocide shows that nuanced positions are not always correct, and that therefore it's wrong to assume a priori that a nuanced position regarding paywalls is correct. Maybe a nuanced position is correct: but that is something to be demonstrated, not assumed.]
So when David says “What I do hold to is that a rounded view, nuance, w/ever you call it, is important”, I have to disagree. What matters is to be right, not nuanced. Again, sometimes the right position is nuanced, but there’s no reason to assume that from the get-go.
Here’s why this is dangerous: a nuanced, balanced, rounded position sounds so grown up. And by contrast, a straightforward, black-and-white one sounds so adolescent. You know, a straightforward, black-and-white position like “genocide is bad”. The idea of nuance plays on our desire to be respected. It sounds so flattering.
We mustn’t fall for this. Our job is to figure out what’s true, not what sounds grown-up.
March 11, 2014
I hate to keep flogging a dead horse, but since this issue won’t go away I guess I can’t, either.
1. Two years ago, I wrote about how you have to pay to download Elsevier’s “open access” articles. I showed how their open-access articles claimed “all rights reserved”, and how when you use the site’s facilities to ask about giving one electronic copy to a student, the price is £10.88. As I summarised at the time: “Free” means “we take the author’s copyright, all rights are reserved, but you can buy downloads at a 45% discount from what they would otherwise cost.” No-one from Elsevier commented.
2. Eight months ago, Peter Murray-Rust explained that Elsevier charges to read #openaccess articles. He showed how all three of the randomly selected open-access articles he looked at had download fees of $31.50. No-one from Elsevier commented (although see below).
3. A couple of days ago, Peter revisited this issue, and found that Elsevier are still charging THOUSANDS of pounds for CC-BY articles. IMMORAL, UNETHICAL , maybe even ILLEGAL.This time he picked another Elsevier OA article at random, and was quoted £8000 for permission to print 100 copies. The one he looked at says “Open Access” in gold at the top and “All rights reserved” at the bottom. Its “Get rights and content” link takes me to RightsLink, where I was quoted £1.66 to supply a single electronic copy to a student on a course at the University of Bristol:
(Why was I quoted a wildly different price from Peter? I don’t know. Could be to do with the different university, or because he proposed printing copies instead of using an electronic one.)
On Peter’s last article, an Elsevier representative commented:
Alicia Wise says:
March 10, 2014 at 4:20 pm
As noted in the comment thread to your blog back in August we are improving the clarity of our OA license labelling (eg on ScienceDirect) and metadata feeds (eg to Rightslink). This is work in progress and should be completed by summer. I am working with the internal team to get a more clear understanding of the detailed plan and key milestones, and will tweet about these in due course.
With kind wishes,
Dr Alicia Wise
Director of Access and Policy
(Oddly, I don’t see the referenced comment in the August blog-entry, but perhaps it was on a different article.)
Now here is my problem with this.
First of all, either this is deliberate fraud on Elsevier’s part — charging for the use of something that is free to use — or it’s a bug. Following Hanlon’s razor, I prefer the latter explanation. But assuming it’s a bug, why has it taken two years to address? And why is it still not fixed?
Elsevier, remember, are a company with an annual revenue exceeding £2bn. That’s £2,000,000,000. (Rather pathetically, their site’s link to the most recent annual report is broken, but that’s a different bug for a different day.) Is it unreasonable to expect that two years should be long enough for them to fix a trivial bug?
All that’s necessary is to change the “All rights reserved” message and the “Get rights and content” link to say “This is an open-access article, and is free to re-use”. We know that the necessary metadata is there because of the “Open Access” caption at the top of the article. So speaking from my perspective as a professional software developer of more than thirty years’ standing, this seems like a ten-line fix that should take maybe a man-hour; at most a man-day. A man-day of programmer time would cost Elsevier maybe £500 — that is, 0.000025% of the revenue they’ve taken since this bug was reported two years ago. Is it really too much to ask?
(One can hardly help comparing this performance with that of PeerJ, who have maybe a ten-thousandth of Elsevier’s income and resources. When I reported three bugs to them in a course of a couple of days, they fixed them all with an average report-to-fix time of less than 21 hours.)
Now here’s where it turns sinister.
The PeerJ bugs I mentioned above cost them — not money, directly, but a certain amount of reputation. By fixing them quickly, they fixed that reputation damage (and indeed gained reputation by responding so quickly). By contrast, the Elsevier bug we’re discussing here doesn’t cost them anything. It makes them money, by misleading people into paying for permissions that they already have. In short, not fixing this bug is making money for Elsevier. It’s hard not to wonder: would it have remained unfixed for two years if it was costing them money?
But instead of a rush to fix the bug, we have this kind of thing:
I find that very hard to accept. However complex your publishing platform is, however many different modules interoperate, however much legacy code there is — it’s not that hard to take the conditional that emits “Open Access” in gold at the top of the article, and make the same test in the other relevant places.
As John Mark Ockerbloom observes:
Come on, Elsevier. You’re better than this. Step up. Get this done.
Ten days layer, Elsevier have finally responded. To give credit where it’s due, it’s actually pretty good: it notes how many customers made payments they needn’t have made (about 50), how much they paid in total (about $4000) and says that they are actively refunding these payments.
It would be have been nice, mind you, had this statement contained an actual apology: the words “sorry”, “regret” and “apologise” are all notably absent.
And I remain baffled that the answer to “So when will this all be reliable?” is “by the summer of 2014″. As noted above, the pages in question already have the information that the articles are open access, as noted in the gold “Open Access” text at top right of the pages. Why it’s going to take several more months to use that information elsewhere in the same pages is a mystery to me.
As noted by Alicia in a comment below, Elsevier employee Chris Shillum has posted a long comment on Elsevier’s response, explaining in more detail what the technical issues are. Unfortunately there seems to be no way to link directly to the comment, but it’s the fifth one.
March 9, 2014
Although it would be nice to think that our site views have octupled in the last day because of Mike’s fine and funny posts about what search terms bring people to SV-POW!, the real reason is that we were blessed by incoming links from both pages of this Cracked.com article.
Now, as any person who has ever accomplished anything whatsoever knows, it is super-important to avoid Cracked.com or you’ll still be up 23 hours from now reading, “6 Mind-Blowing Ways that Comedy Writers are Secretly Destroying Your Productivity”. (I’m kidding, that article doesn’t really exist–but if it did, I’m sure it would consist entirely of descriptions and links to six other Cracked articles). But that’s only true because most of the articles there hit the sweet spot at the intersection of funny, surprisingly informative, mercifully short, and well-written. Crack.com would be a more honest URL, but I assume it was taken.
Anyway, I’d like to return the favor, so here’s a list of the 6 SV-POW! Posts Most Likely to Blow the Minds of Cracked.com Readers. If I missed some goodies or recommended some stinkers, let me know–the comment thread is open.
Who doesn’t want to read about the bizarre real-world mystery surrounding what might have been the world’s largest dinosaur? If you’re not sold, consider that the picture above shows a single vertebra that was–or at least might have been–seven and a half feet tall.
The mercifully short version of this much longer post, in which I consider the consequences of the world’s largest animals having the world’s longest cells.
Weapons-grade anatomical pedantry.
Yes, there is a ship in Star Wars: The Clone Wars that is basically a flying dinosaur vertebra. It took us about five weeks to unravel that story–the post linked above has links to the rest of the saga.
Our original linkbait post. Don’t miss the shorter follow-up with more critters.
A deliberately goofy post in which I wax poetic about the largest predatory dinosaur claws ever discovered.
So, that was a big pile of superlatives and Star Wars. If you’re hungry for more substantial fare, you might start with our Tutorials page or our Things to Make and Do series on dissecting and skeletonizing modern animals. We also blog a lot about the evils of obstructive publishers and the need for open access to the scientific literature–you can find those posts on our Shiny Digital Future page.
A parting shot in my desperate quest for attention: this Star Wars ship flying around in the background in Firefly and Serenity is at least partly my fault–full story here. Oh, and my co-blogger Mike Taylor has written an insightful and affordable book about Doctor Who; read about it here.
Wedel, M.J., and Taylor, M.P. 2013. Neural spine bifurcation in sauropod dinosaurs of the Morrison Formation: ontogenetic and phylogenetic implications. Palarch’s Journal of Vertebrate Palaeontology 10(1): 1-34. ISSN 1567-2158.
February 19, 2014
Previous posts in this series are here.
February 11, 2014
Somewhat lamely, this is the only slide I had in about lighting. I left it up while I talked about the most important points, which are:
- Don’t use a flash unless you absolutely have to.
- If you can swing it, the common convention is to have specimens illuminated from the upper left.*
- If you have the time, it’s not a bad idea to bracket your Goldilocks shot with brighter and darker photos, by fiddling with your camera settings.
* I happily violate this convetion if illumination from another angle shows the specimen to better advantage–and if I have any control over illumination. Working with big bones in some collections, you basically have overhead florescent lights and that’s it. The NHM shot above may look not-so-hot, but there we at least had a desk lamp we could move around. In a lot of places I’ve worked, I didn’t have even that.
The other posts in this series are here.