Comments (10)
Hmm, it looks like the API does not disambiguate SEs from SDs. From @stripathy:
If you look at the summary spreadsheet here: http://neuroelectro.org/static/src/article_ephys_metadata_curated.csv, you'll see 6 terms per ephys property, for example for rmp: (rmp rmp_raw rmp_err rmp_n rmp_sd rmp_note). The n term is provided by the authors and the sd term is converted from the standard error (err) term provided by the authors.
In terms of the api, we only export the n and error terms (we don't disambiguate whether the error is a standard error or a SD).
from neuronunit.
Good point @JustasB - I'll add a field to the api that allows you to disambiguate whether the errors are SD or SEM.
from neuronunit.
@stripathy Let us know when the SD/SEM flag is ready -- I have everything in place on our side to look for the flag.
However works for you, but it would work for me if it was something along the lines of:
from neuronunit.
@JustasB @stripathy I implemented most of the API so I think it might be faster if I figure this one out (unless you have someone on it already, Shreejoy), but it will probably have to wait a few days.
from neuronunit.
Sounds good guys, whatever works for you
from neuronunit.
Hi @rgerkin and @JustasB - I'll take care of this tomorrow before leaving town. It's super simple on my end, I just need to add a field to the DB indicating what the error type is and then do a migration.
from neuronunit.
I just implemented this feature as requested. You'll now see a field called "error_type" on nedm data objects indicating the error type. http://dev.neuroelectro.org/api/1/nedm/?n=129
Please note that we're using a computational method to "guess" what the error type is (based on the size of the errors relative to the mean across all the data extracted for each article) vs manually curating whether errors are SDs vs SEMs. If you come across papers where the imputed error type is wrong, please let me know.
from neuronunit.
Thanks @stripathy
For the error type, when I looked at the MC data, the err or err_norm value (if existed) always corresponded to the SEM. However in the API, its not always SEM. Thoughts?
This is where I talk about it always being SEM:
neuroelectro/neuroelectro_org#290 (comment)
from neuronunit.
@JustasB Did you ever implement this?
from neuronunit.
@rgerkin The functionality to compute grand means and SDs from individual paper means and sds has been implemented in neuronunit:
neuronunit/neuronunit/neuroelectro.py
Line 271 in feb7e80
@stripathy implemented the change to return the error type:
#13 (comment)
and neuronunit code is using the error types of each paper to determine the grand mean and sd.
from neuronunit.
Related Issues (20)
- Use Allen Features to optimize HOT 11
- newer test class for passive elephant tests breaks parallelism in dask, in the case of brian2 backend. HOT 4
- Documenting all Score edge cases that break optimization gradients HOT 3
- A document Notice to debug set PARALLEL_CONFIDENT=False
- Test Suites should be dictionaries not lists. HOT 7
- Use standardized units throughout
- Sciunit judge no longer works with static Models. How can I opt of using the ProtocolToFeaturesTest? HOT 8
- Druckmann Tests are not proper tests
- Confirm that NeuronUnits jNeuromLB backend really can be regarded as a ground truth. HOT 7
- NU test.protocol should be flat or more predictable to traverse.
- Major NU interface redesigns could come with interface diagrams.
- documentation chapters of NeuronUnit should be upgraded to Unit Tests via pytest-ipynb
- 2.5 different code locations that determine sim_length need to be collapsed into one.
- Duplicated content injected current test protocol/parameter
- Installation Fails on Windows HOT 1
- create branch optimization based on dev, that I can merge pull requests into. HOT 2
- Migrate away from travis HOT 2
- Merge error in backend __init__.py HOT 2
- Missing closing ' HOT 1
- Relax constraints on install requirements HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from neuronunit.