Document all possible evalFuncs

[ewu63]

Description

We should document all the possible values to evalFuncs. This is currently stored in self.basicCostFunctions.

Potential solution

Maybe reuse the options table/list to document this? This feels like a rather general thing for solvers, e.g. what they can compute.

[gawng]

@ArshSaja do you have a branch with this started? If you have a branch I can work off of, I won't start a new one. Please let me know either way, thanks.

[ArshSaja]

@gang525 Now we can split the evalfunc option to finish the explanation. After cd0 @gang525 will take care of it

[ewu63]

@ArshSaja @gang525 what's the status on this?

[gawng]

Yea, the status is ive been thinking about this but i just havent done it yet but i know this is time sensitive to before people leave like Eirikur, anil, you, yingqian etc who can review it. I have an abstract due mid october and trying to finalize my trip to australia but i can work on this after.