These are chat archives for dereneaton/ipyrad

5th
May 2016
Isaac Overcast
@isaacovercast
May 05 2016 22:54
I've got a bead on the popgen summary stats, think i can code it up this weekend. Where do you think is the best place to put it? Slap it on at the end of step 7? Or have it be more of a standalone thing like svd4tet?
The argument for just tacking it on to step 7 is that if we just always do it no matter what there doesn't have to be a special paramsdict or cli flag. Also the time to calculate and the way i'm doing it is v fast, takes <5 minutes on real data.
I'm not married to either strategy, but figure i'd check if you had a preference.
Deren Eaton
@dereneaton
May 05 2016 22:56
Hmm, I'm thinking standalone, but accessible through ipyrad.analysis API.
Isaac Overcast
@isaacovercast
May 05 2016 22:57
Sounds good.
Deren Eaton
@dereneaton
May 05 2016 22:57
But that sounds awesome!
Isaac Overcast
@isaacovercast
May 05 2016 23:07
Yeah, it'll be fun when it works. My inclination is to put it in the 'analysis' dir, but looks like svd is using main. Unless you have a better idea i guess i'll make a new directory ipyrad/sumstats? Better ideas?
Deren Eaton
@dereneaton
May 05 2016 23:09
oh, well I guess each one could have it's own main
ipyrad/analysis/__mainsvd__
ipyrad/analysis/__mainsumstats__
the name main isn't really special, other than we tell setup.py to use that file to build the cli for that thing. But yeah, feel free to rearrange things into subdirectories inside analysis if that makes more sense.
maybe things don't need to be grouped into analysis, was just an early idea.
Deren Eaton
@dereneaton
May 05 2016 23:15
I'm dying trying to parallelize something in step7, whaaaaat is going on. I just cannot find the error.
Isaac Overcast
@isaacovercast
May 05 2016 23:18
dude i hate that, i sympathize.