Skip to main content

Resources for begining recurve archery

I took up archery with instruction books, rather than an instructor. Time will tell if that was smart. I read a lot of stuff from websites and some from books. In the UMD library I could not find an archery book more recent than some time in the 1970s ! I guess UMD is not big into archery!

I read the following books:

"Shooting the Bow", Larry C. Whiffen, The Bruce Publishing Co, Milwaukee 1946.
This is an instructional book with charming mid-20th century black and white pictures written in a charming and humorous mid-20th century style. It has hand illustrations for stance, grip etc. It has a one page chapter about correcting errors.

"Archery", Lorraine Pszczola, W.B. Saunders Co, 1976
This is meant as an instructional booklet for college/school archery programmes. Filled with illustrations about stance, and grip etc.

"Archery for beginners", John C. Williams, Contemporary Books, 1976
This was the one I referred to the most. The archers in bellbottoms are a hoot. It also uses the words "sexy" and "groove". A true 70s book. It has some good advice about correcting errors.

My favorite book of these three is Williams' book because the advice on stance, grip and release are very well described and illustrated with photographs. Williams also explains the mechanics behind it all, which makes his writing more aesthetically pleasing foe me.

It helped me to read several books because there were differences in the material and advice, and I picked out those things that struck me as useful, or that helped me. There was contradictory advice about stance and grip, which illustrated to me that there is not ONE way to shoot an arrow!

Mostly it was the illustration and pictures that helped me from the books. A lot of text about archery is available on the web. Unfortunately a lot of the websites don't have pictures, so that's where you have to refer to the books.

Some websites that I find useful are:


Oh, and here are some things I found useful.

Comments

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...

Remove field code from Word document

e.g. before submitting a MS, or hand manipulating some formatting because Word does things (like cross-references) so half-assed [from here ] Select all the text (CTRL-A) Press Ctrl+Shift+F9 Editing to remove anonymous comments that only contain thanks. I really appreciate the thanks, but it makes it harder to find comments that carry pertinent information. I'm also going to try and paste informative comments in the body of the post to make them easier to find.

h5py and multiprocessing

The HDF5 format has been working awesome for me, but I ran into danger when I started to mix it with multiprocessing. It was the worst kind of danger: the intermittent error. Here are the dangers/issues in order of escalation (TL;DR is use a generator to feed data from your file into the child processes as they spawn. It's the easiest way. Read on for harder ways.) An h5py file handle can't be pickled and therefore can't be passed as an argument using pool.map() If you set the handle as a global and access it from the child processes you run the risk of racing which leads to corrupted reads. My personal runin was that my code sometimes ran fine but sometimes would complain that there are NaNs or Infinity in the data. This wasted some time tracking down. Other people have had this kind of problem [ 1 ]. Same problem if you pass the filename and have the different processes open individual instances of the file separately. The hard way to solve this problem is to sw...