Closed Spencerbrucehudson closed 5 years ago
Not a race I'd like to take part in, because you will certainly win. Although, I should add, natdb
is getting there...
Is there a way to write a wrapper for these clamp papers? It strikes me they're in the same format; is it possible to use some of that redundancy?
It is mostly redundant, but there's discrepancies in the number of header rows. Also, the imported data always seems to have blank rows that trail after the species names, and so I've had to adjust accordingly. I'm trying to think of ways to get around that though..
Although, more often than not, they do have the same number of header rows, so most could be wrapped as long as the other data (year,area,lat,lon, etc.) could somehow be pulled from those header rows.
Edit: I think this can be done.. Will get back to you.
Ah: don't worry about the header rows, this isn't natdb
, and all we care about is whether species are there (or not). A way around the variable length of the first column might be to loop over the column, each time adding a species to a new vector, and then break
out of the loop once you get to a blank entry. What do you think?
Sorry to have only just got to this; meetings all day :-(
Started the clamp functions. How about I race you, writing the paper vs knocking the clamp functions/wrapper out?
EDIT: Oops. Should be axelrod.1950, not 1960.