Closed sonyahanson closed 7 years ago
Making changes as suggested in #55 .
Add simulated data and MLE notebooks to new probe-assay
folder.
Had a quick meeting just to catch up with Greg and Mehtap today, and we decided it makes sense to call the folders in examples
:
direct-fluorescence-assay
competition-fluorescence-assay
We should try to keep this nomenclature consistent, there are some things in the autoprotocol
directory that use the term probe-assay
, which we should remember to update.
Now have a basic competition assay analysis of simulated data with MLE using the three-component-binding function: https://github.com/choderalab/assaytools/blob/data_clean/examples/competition-fluorescence-assay/MLE%20fit%20for%20three%20component%20binding%20-%20simulated%20data.ipynb
I am pretty sure the assumptions made in that three-component binding model are not going to work for us.
Can you just substitute that out with the general binding model?
If the API is too hard to use, I can expose a simpler three-component binding model for you to use as a drop-in replacement.
Sure, this notebook was somewhat of an exercise, so yeah, don't know that it's entirely suitable for actual data analysis. But yeah, Greg and I are planning working through the general binding model in a similar way, and we can compare performance.
Finished cleaning all the data and extraneous ipynbs!
There's definitely still some work to do cleaning up the ipynb's, but the main goal of this PR is just to clean up all the crap so the structure of the examples and data is roughly how we want it.
If anyone sees any specific data or ipynb's that they think should stick around that are not here, let me know. Otherwise this is good to merge.
@jchodera @MehtapIsik any thoughts?
I am very happy with direct-fluorescence-assay and competition-fluorescence-assay distinction. I think this organization of example data is much better than before.
I have three small suggestions:
Looking good!
My preference is that, instead of having a single top-level README.md
like this one to have a README.md
in each directory that explains just the current contents of that directory. That makes the github easier to navigate, I think!
Thanks Mehtap, these are great suggestions!
I've made the change suggested in 2, and made 1 and 3 issues for later. I had meant to include instructions for using quickmodel in this PR, but didn't end up having time and I like your idea of connecting it to an ipynb as a 4th segment, though perhaps it should just replace the 3rd notebook...
Merging.
Cleaning
data
andexamples
directories.