DO NOT MAKE ANY METHODS STATIC!
DO NOT WORRY ABOUT THE CONSTRUCTOR RIGHT NOW!
Justin, nothing you said seems relevant to Beth's problem to me; the program should work fine as-is, with no constructor. Let's just worry about one thing at a time.
Now, as to your question:
you should be able to remove the getRadius() method entirely without having any effect on this program, since no code here calls that method. It doesn't matter what a method does if it never gets called!
When you say "new Circle()" you create a new Circle object. Imagine that an object is like a kitchen drawer with dividers in it. In one section, you put forks, in another,
spoons, etc. For a Circle object, there's a divider where you can put a value called "radius". That divider corresponds to the "radius" instance variable.
The setRadius(x) method says "here's a value 'x', put it in the divider for storing the radius, please."
The getRadius() method asks for the value stored in the radius divider. It could be used like
double radius = aCircle.getRadius();
Is this helping at all?