As the title suggests, there are moments in your programming life when you'll need to be overly complex. Yes, with more time and skill you could likely find a more elegant solution - something you could be proud to stand up and say "Yes! I wrote that!". But often you'll find an inelegant fix will work just fine all the same. Sure, it's not pretty looking and you wont want to go around showing it off to your more tech savy friends but hey, you wont get any judgement from me! Plus it's likely that only in these moments of patching solutions together that you're really justified in using crass, explicit phrases to comment your code.
Given the plethora of hours I've been recently devoting to picking refraction data I thought why not make a video of it?? And so that's exactly what I did! This video will give you a taste for what the last several weeks of my life have been filled with, granted with a slightly different soundtrack (cough, so-much-netflix, cough). Plus if you ever find yourself needing a solid program for picking refraction arrivals you should give OpendTect (a primarily reflection platform) a try! Enjoy :)
Recently my life has been consumed with picking data! Picking, and picking, and piiicking, and piiiiiiiiicking ... But hey, that's ok! I'm 18 OBS down, 15 OBS to go, and ~ 45 onshore stations to pick! Wait, that's a lot more than I thought ... Ah, oh well I'm sure time will fly! To stave off madness I have been taking breaks brainstorming ways of effectively displaying my picking escapades. These include plots of my progress (to prove to my advisor I've been working ... cough, I mean to practice visualizing data)
Onto the big reveal … Let’s cut SEGY data from continuous data! For a brief introduction into why one might do this go back and read my last post.
Most major plate boundaries (with a few notable exceptions, can you think of which they are?) sit either completely offshore (i.e. mid-ocean ridges) or at the junction between an ocean and a continental land mass (i.e. subduction zones). Thus to study the forces that control plate tectonics we commonly have to jump in and "get our feet wet" - i.e. go into the oceans. As seismologists we routinely get our feet wet by deploying ocean-bottom seismometers (OBS) to record ground motions both from near and far earthquakes as well as man-made sources.
Hahaha, ok I'm already cracking myself up with this title because, really, who likes debugging and debugging in fortran nonetheless? The title is definitely a misnomer but it's a reality that as a graduate student in earth science (and likely other fields) at some point in time you're going to have to debug something written in Fortran.
My life continues to be consumed by the awesome world of active-source seismology. Specifically, picking, picking, picking, and more picking ... I have now realized that no matter what field of science you're in at some point in your career you're going to end up picking something. Maybe you're picking spectral peaks to identify organic molecules in soil samples, or different types of pollen scraped off of bees (I've done this), irregular heartbeats in a mouse's cardiogram, boulders in satellite images of the Moon (I've done this too), or just regular ol' seismic arrivals to locate earthquakes, no matter what field you're in you'll likely end up picking something!