Closed rmjarvis closed 6 years ago
Given that we occasionally end up stuffing new things into the GalSimCelestialObject (for instance, the number of knots in Francois' model), we should probably add a unit test to make sure that the property getters return the same thing that is given to __init__
. I can do that.
Oh. Nevermind. This PR is from a fork. Do you mind adding such a unit test, @rmjarvis ?
I was hoping there would be some Travis run that would check that I didn't break anything with this. But it seems that the unit tests aren't being run automatically.
Is there a standard way for me to install this package and run tests (and then to add a new one and run it) that you could point me to? Or do I need to have the full stack installed and then do some complicated eups esoterica?
It is, unfortunately, the latter.
If you want to just go ahead and merge, I (as a member of the EUPSophonic community) can write the unit test in a different branch.
Or if you want, you can make a branch and merge this onto that branch instead of master. If you don't want to sully master with possibly error-prone code.
Okay. I will do that.
Added the unit test in
An idea floated on todays CI telecon to reduce the memory footprint of the GSCO instances.