i would avoid using vtk...as a physics student i would assume you want to do dynamics rendering and not just static. VTK is inherently slow if you do lots of dynamics and the books for VTK are written in script(python? no wait tcl/tk). Its not hard to learn VTK C syntax through the script but its annoying and takes a long time, time away from other stuff you can do as a student.
If you just want to learn how to use opengl: the red book and blue book(the official books mentioned above) are probably your best bet. They are on the official site,i think its opengl.org or its from SUN? just search "opengl red book"
If you want hands on tutorials: Nehe Tutorials and Nate Robins(i hope that's the correct name and spelling) used to be open source i Don't know if they are now...but Nate Robins code is probably better because it follows most opengl book schemes
if you want to learn about interactive camera navigation:
www.libsdl.org OR glut(opengl's version) which are the easier GUI sdks to use with Opengl.
if you want to learn about 3D math involved in 3D engine progrmaming:
with opengl: I suggest picking up the Opengl for Game programming books, the one i learned from is from the primatech series(do they still exists) editor andre lamothe
This one has an entire physics one at the back but its in OO design
OR david eberly's "3D game engine development" also in OO design
[and the better 2 that i have been introduced]
if you want to learn just the coding for the mathematics & physics(classical?) components
Eric Lengyel: 3D Mathematic for Game programming( or something by a similar name)
has no code but its structure will lead you in the order you should code stuff and it covers so much of 3D math & physics including basic numeircal principles if you haven't already covered them as well as curves/surfaces and bounding volumes/collision stuff.
Christof Ericson: Realtime collision detection. The book I am currently working through.
Its got all the geometry stuff that the lengyel book doesn't have organized in a better order but its first few chapter orders don't compare to the lengyel book.
The great thing abotu this book its got code, gives you a great starting point for the code, has an extensive geometry section, and talks about spatial partitioning as well as robustness. Bad thing is that though most of the functions are complete..there are a lot of snippet codes and "if you want to go further look at this reference".
Lastly
[0] Chris Hecker's papers on 3D physics if you can find them (siggraph or the gaming one)
[1] THe bible for graphics Foley and Van Damm (u go to waterloo right? this book should be in the library).