so many lines of code to check
i have a talk coming up entitled "classical trajectory modeling of the photodissociation of the linear argon-iodine complex" based on research i did last semester, and i dusted off the program to work on the talk, but it's outputting really messed up data, and i can't figure out why. part of the problem is that there are like 2000 lines of fortran to sift through, though thankfully i have the problem nailed down to a very small section. this involves the always exciting writing of many 'write(*,*)'made it this far' statements looking for the one that doesn't print.
i'm also writing code to do a gauss-chebyshev numerical integration for my summer research. this also has a problem i can't seem to fix, but in this case it's due to my own ignorance in fortran programming. i seem to be calling my subroutine with the wrong variables....
so, after wading through all that stuff about computational chemistry, here's the 'non-nerdy' stuff. had a wonderful dinner tonight with some friends, talking about our small group and how to make it more accessible, and at the same time foster close relationships.
my stupid fantasy baseball team has decided not to hit any more. i have five 10+ game winners for starting pitchers, but my batters are in a slump, all of them... except for andruw jones.
