Conversation
|
@thequackdaddy thanks for this. certainly it is of interest if you want to finish it we will merge. modernizing/pruning the tests would be very helpful. |
|
@sjsrey I would be happy to continue. I'd likely need a rather thorough review of this... there's lots of potential assumptions and not extremely thorough examples... So its highly likely what I do will be somewhat incorrect. Not having a good worked example makes writing unittests challenging. When I get some time, I'll experiment some more with it shortly. If you have other resources/documentation, please let me know. |
|
Here is some more documentation: https://surveillance.cancer.gov/headbang/ |
|
@thequackdaddy this is looking good - i will get a closer review in the coming days. One thing that comes to mind is whether we can assume |
Hello,
If I understand correctly, the headbang triples spatial smoothing is not beign supported because the current one doesn't work too well in python 3. After reviewing, I think I may have stumbled across a few bugs that make getting the old unittests to pass very difficult.
I decided to re-write it. Please let me know if this is something you'd consider replacing. Right now, I've saved this in another module (it is easier that way because i work with python 3 and the
2to3process makes it hard to save a diff only for the changing part of the file. I'd incorporate this inpysal.esda.smoothing.I've followed the algorithm described in this paper.
Right now, I've only re-written the
Headbanging_Triplesalgorithm. I haven't experimented with theHeadbanging_Median_Rateclass yet. (It may be we can fully recycle that.)Please let me know if this is something of interest to this project. Happy to finish it, or close this PR if you don't want to maintain.
Right now, I'm missing docstrings (I probably could just copy from the old method... but there's a few small simplifications to the API I woudl argue for... mainly dropping the requirement for
dataandkas they are already provided by the spatial weightw.Also, the current unittests use the old nose template. There's a lot happening in the
setUpfunction that doesn't really do anything.