Here's yet another non-linux post. I'm currently getting ready for the start of the new semester and teaching, and so haven't had much time to work on improving my computer skills.
Anyway.
I've been advertising for an international PhD student for the past 9 months and have so far only had one great applicant and three acceptable applicants. That's out of ca 200 applicants in total.
So what does 'acceptable' mean? In this case my use actually agrees with the literal meaning -- students which will stand a chance of being accepted to the PhD program. It also means students which I could imagine working with.
The formal requirements will likely differ between different institutions, and between supervisors. In addition, some supervisors may be looking for different personalities in their prospective hires, than others.
I don't think that I'm being unnecessarily harsh in evaluating applicants, as I've had colleagues review my shortlists and who have thought I've even been a bit too optimistic in my evaluations.
At any rate, if you are looking for a PhD, be aware that there are a lot of applicants out there, and only a limited amount of money and places, so you will want to spend some time on your application.
So here are a few of my thoughts:
Before reading, keep in mind that I understand that applying for a PhD, especially if you are from the developing world and applying for a PhD position in the industrialised world, can be very tough, and sometimes depressing. You don't receive a reply to most of your applications, and when you do, they responses are normally negative.
* Try to familiarise yourself with the formal requirements, and address them in the first paragraph in your email to a prospective supervisor. In the case of my uni, there are two main requirements:
-- an undergraduate degree equivalent to a first class honour degree in Australia
-- a sufficiently good score at the IELTS
That's it. However, the hubris of many universities in Australia mean that the first requirement is a significant hurdle. Typically, good grades are just the beginning. In addition to that, the applicant needs to hold a masters degree (by research) and have a couple of papers in ISI rated journals. Obviously almost none of our own undergraduate students would meet that, but there you go.
So in your first paragraph, state what unis you did your degrees at, what your cumulative GPAs (or equivalent) were, how many papers you have published and what you overall band score AND section scores on the IELTS (or TOELF) are.
At this stage, that's much more important than your background, your hobbies, or anything else. If you can't meet the minimum requirements for entry to the PhD program, everything else doesn't matter.
* Read the advertisement, and follow any instructions
I ask applicants to submit all their documents as PDFs. Yet, I get plenty of applications with .doc, .docx, jpeg etc attached. You didn't read the instructions -- will you be more careful as a PhD student? Remember that you competing against plenty of applicants that did read the instructions.
Did I ask for your IELTS results? Didn't attach or mention them in your email/CV? Not a good sign. Also, it means that you're probably not a candidate.
* Address the supervisor and the supervisor's research
I get way, way too many emails that start with 'Dear Sir', or 'Dear Professor' or even worse: 'Dear Sir/Madam'. Put my name in there. It'll show me that you spent at least a few minutes on personalising your email. If you don't make that effort, why should I make the effort of reading your email and looking at your documents?
Also, please do mention the research of the supervisor you are applying to. It doesn't need to be anything insightful or special, but just write something like: 'I find your research into catalytic activation of molecules in ionic liquids very interesting.' or 'I read your article in Green Chemistry, 2013, 10, 2345 and found it very interesting. In particular, I liked how it showed how the selectivity of blah blah blah'.
The reason is not that you are showing off your great scientific skills (you've got an undergraduate degree -- we don't expect much), but that it shows you spent a bit of effort writing your email and personalising it. Also, flatter -- in moderation -- can occasionally help (don't go overboard, so be careful -- too much makes you seem insincere).
* Don't cold-call
This should go without saying. I've had one student email me in the morning, then call me in the afternoon. That kind of behaviour is probably correct if you are applying for certain jobs in the Real World (marketing?), but not for a PhD in chemistry. It's a sure-fire way of annoying people.
* Don't send a linked-in invite
I don't have time to scroll through your profile and try to compile a CV for you. Send me your CV in pdf format instead. Also, I don't know you, and have no incentive to add you to my 'network'.
* Be careful about 'hobbies' and 'interests'.
To me as a potential supervisor they really don't matter (again, this is my personal opinion). I know that the idea is to show that you are a well-rounded individual, but knowing that you like 'travel' or that you consider 'internet browsing' a skill will not be the edge that gets you into a PhD programme.
* 'It can't help you, only harm you'.
Keep this in mind. Unless it's a piece of information required in the advertisement, or that you are absolutely certain will help your application, consider leaving it out. You may include it to highlight a particular skill or trait, but remember that a CV can be interpreted ambiguously, and your intent may not be obvious. Instead, what you feel shows how independent and committed you are, can be seen as being unfocussed, a difficult person to work with, or simply attract attention away from more important aspects of your CV.
* Attending lectures, conferences
In their CVs, some applicants include lectures by famous people that they've attended, or conferences that they've gone to.
Here's the problem for me: most first year PhD students struggle with the notion that doing the work is no longer enough. Doing the experiments, or following your supervisor's instructions, is not enough. To get a PhD you need to make that extra effort and making things work. And if it doesn't work, you put in 150% effort -- the extra 50% being extra-curricular work on finding a related project that will work. Life as a PhD student can be easy if you are lucky, but most often is not -- life is incredibly good when you project is working, but on the flip-side it can be hard, depressing and demoralising when it isn't. You supervisor can alleviate some of that, but remember that your supervisor is only there to point you in a general direction -- the PhD is all about making the transition to becoming an INDEPENDENT research.
So be careful -- if you've presented posters or given talks at conferences or at other universities, you should definitely list them, but under a suitable heading -- NOT publications. They'll detract attention from the publications, and the publications is what will get you an offer of acceptance.
* Do not make things conditional
I had an applicant who was borderline (in terms of meeting the requirements), and in those cases occasionally the supervisor putting in extra effort into cajoling the university administration MAY be enough to get a student accepted (don't count on it). If your prospective supervisor asks you to re-take IELTS, don't write something along the lines of 'I will, but only if this is the last hurdle'.
I understand it's expensive, but remember: even if you meet all the requirements I cannot guarantee that you get accepted. And I can' wait months for each student to pass through the application system -- I need to hire someone now. So be proactive.
* Face-to-face (or skype/video) interview is a good sign
If your supervisor asks for a skype interview, this is a great sign. And likely this isn't really done in order to gauge your scientific skills, but just to get a feel for your personality. Also, it's a way of making sure that your English levels are good enough that you can communicate with your supervisor. Finally, if you are borderline in terms of IELTS/TOELF, your supervisor may be able to argue that you English is good enough based on that interview. So take the opportunity.
And send an email a few hours after the interview thanking for the opportunity. 1-2 lines is enough. It will show that you're a decent human being.
* Be prompt in replying to emails
It doesn't matter what stage of the application you are at -- until the paperwork has been signed you are still on probation. If you take several days to reply to any of my emails, then you are likely to be dropped. The reason is simple: if you take a week to get things done when you are a PhD student, then you will be a disaster for me. A disaster that I'll have to live with for the next 3-4 years, and whom will be using up my research grant, and potentially ruining my career.
I understand that the reason for you being slow may be different -- maybe you are just nervous, maybe you have nothing to say, maybe you feel you are intruding. Still, be prompt.
So:
if you can show that you can read and follow instructions, and if you can make my life easy by addressing the selection criteria in a clear way, and if you seem like a person I might enjoy working with for the next 3-4 years, then you stand a fair chance of getting an offer.
If I think you'll need constant supervision, is sloppy and won't follow instructions, or that our personalities will clash, I'll probably avoid you no matter how good your grades are.
15 July 2013
12 July 2013
474. MS data, part I: Exporting data as csv from wsearch32, and generating MS assignments using Matt Monroe's molecular weight calculator
NOTE: I've heard rumours about problems with wsearch on Windows 7 Home, and on Windows 8. I've heard reports of it working on Windows 7 Professional. Curiously, it works just fine on linux under wine.
This post is written with two particular students in mind. I could put this in a pdf and email it, but why not share with the wider world since other people may encounter the same issues?
See here for part II: http://verahill.blogspot.com.au/2013/07/480-ms-data-part-ii-plotting-and.html
1. Exporting data from wsearch32
To install wsearch32 under wine, see here: http://verahill.blogspot.com.au/2013/01/321-wsearch32-in-wine.html
In order to export data from wsearch so that you can plot it in e.g. gnuplot, octave, origin or excel, do the following:
Open a spectrum (chromatogram) and pick a slice, then click on the M/I icon in the bottom right:
Pick Save As
And save as e.g. csv (comma separated file)
Done.
2. Using formula finder in Matthew Monroe's Molecular Weight Calculator
To install the molecular weight calculator in wine, see here: http://verahill.blogspot.com.au/2012/09/matt-monroes-molecular-weight.html
Open the molecular weight calculator and go to edit abbreviations.
Add an abbreviation for MeO. We'll call it Methx, and it has a charge of -1:
Methanol:
Nitrate:
Hit OK to save the changes.
Go to formula finder:
And search:
You can do fancier stuff, e.g. searching directly for the m/z and bound the search to min/max amounts of different elements:
As shown here:
This post is written with two particular students in mind. I could put this in a pdf and email it, but why not share with the wider world since other people may encounter the same issues?
See here for part II: http://verahill.blogspot.com.au/2013/07/480-ms-data-part-ii-plotting-and.html
1. Exporting data from wsearch32
To install wsearch32 under wine, see here: http://verahill.blogspot.com.au/2013/01/321-wsearch32-in-wine.html
In order to export data from wsearch so that you can plot it in e.g. gnuplot, octave, origin or excel, do the following:
Open a spectrum (chromatogram) and pick a slice, then click on the M/I icon in the bottom right:
And save as e.g. csv (comma separated file)
Done.
2. Using formula finder in Matthew Monroe's Molecular Weight Calculator
To install the molecular weight calculator in wine, see here: http://verahill.blogspot.com.au/2012/09/matt-monroes-molecular-weight.html
Open the molecular weight calculator and go to edit abbreviations.
Methanol:
Nitrate:
Hit OK to save the changes.
We'll be looking for Ga, NO3, MeOH, O, H, MeO. Then click on Formula Finder Options:
Limit the charge to 1:And search:
You can do fancier stuff, e.g. searching directly for the m/z and bound the search to min/max amounts of different elements:
As shown here:
10 July 2013
473. Programming a Metrohm Titrino -- not a how-to, just a ramble
Many, many years ago I learned basic programming using BASIC (the version that came with PC DOS 5, I think). I even wrote the odd game, but it was all pretty awful. A few years later I learned Turbo Pascal, which was a fantastic experience compared to Basic. It felt all sciency and grown up, and it was my first experience with a real IDE. I even ended up buying a TP book, and became somewhat proficient. This must've been when I was around 18-19.I then stopped programming completely.
At around 30 years of age I decided it was time to get serious about programming again -- I was doing mass spectrometry and needed a simple program that could generate a series of solutions to the identity of a mass/charge ratio given a range of elements. I probably had a quick look at C and C++, but ended up getting a Python book and have been happy Python programmer ever since.
The problem is that I've never been a /good/ python programmer -- and in all these years I've never fully understood the use for (or, in all fairness, use OF) OOP. And at the moment it seems to be holding me back -- all the examples that I find of the use the threading module as well as writing GUIs (using e.g. wxPython) involve using classes. And I just don't understand them well enough to sort out what I need done.
Anyway, long story short: I've written a basic program for communicating with a Metrohm Titrino 736 GP via RS 232. It's found here: https://sourceforge.net/projects/pytitrino/
Currently:
* the code is a mess (see above)
* it works fine for doing monotonic and dynamic end point titrations (MET and DET)
* it saves data to a file, but does so silently (i.e. when you run you won't get any feedback that things are working properly...)
* it uses the thread (not threading) module
* I've managed to pass parameters back and forth between the thread and the main loop using Queue
There are probably much better solutions. One day I hope to be able to stick a GUI on top of it, but the more I look at it I get the impression that one writes the GUI first, then the engine...not that I'd know.
Anyway. That's what I've been up to. Anyone with a bit of programming experience, whom is in possession of an old-school Titrino (i.e. using RS 232) and wants to save $1.5k in software licenses may be interested in taking the sources and turning them into something useful.
At around 30 years of age I decided it was time to get serious about programming again -- I was doing mass spectrometry and needed a simple program that could generate a series of solutions to the identity of a mass/charge ratio given a range of elements. I probably had a quick look at C and C++, but ended up getting a Python book and have been happy Python programmer ever since.
The problem is that I've never been a /good/ python programmer -- and in all these years I've never fully understood the use for (or, in all fairness, use OF) OOP. And at the moment it seems to be holding me back -- all the examples that I find of the use the threading module as well as writing GUIs (using e.g. wxPython) involve using classes. And I just don't understand them well enough to sort out what I need done.
Anyway, long story short: I've written a basic program for communicating with a Metrohm Titrino 736 GP via RS 232. It's found here: https://sourceforge.net/projects/pytitrino/
Currently:
* the code is a mess (see above)
* it works fine for doing monotonic and dynamic end point titrations (MET and DET)
* it saves data to a file, but does so silently (i.e. when you run you won't get any feedback that things are working properly...)
* it uses the thread (not threading) module
* I've managed to pass parameters back and forth between the thread and the main loop using Queue
There are probably much better solutions. One day I hope to be able to stick a GUI on top of it, but the more I look at it I get the impression that one writes the GUI first, then the engine...not that I'd know.
Anyway. That's what I've been up to. Anyone with a bit of programming experience, whom is in possession of an old-school Titrino (i.e. using RS 232) and wants to save $1.5k in software licenses may be interested in taking the sources and turning them into something useful.
Subscribe to:
Posts (Atom)