Make both Raw and Average available to user
Needs to be available
Comments (9)
-
-
Nope not sure what this is referring to. I would maybe guess that it has to do with the Order module and allowing the user access to the data before it's averaged over neighbors. That's just a guess though, @harperic can you comment more?
-
reporter IIRC, this is in reference to the quantities produced by RDF, PMFT, etc. I believe the original proposal was to allow the user to have access to either the raw counts or even access to the counts for each frame.
It's been a while since I've thought about this particular idea/request, and I'm not sure how necessary or even how useful this would be.
-
For the PMFT the bin counter object is the raw counts, right? Not per frame, but the total.
I agree, I'm not too sure I see the utility aside from debugging purposes, and for that I would think it would make the most sense to just use very simplified systems to test with.
-
reporter There may be other reasons to provide the raw counts, I'm thinking perhaps it was related to being able to track the convergence of the calculation with its std. dev., but if that's required, doing a small set of calculations to determine how many frames you need is a better solution than providing this feature, unless the feature is already available due to the manner in which the calculation is implemented i.e. the array already exists and adding a Python wrapper is trivial.
-
OK, so that is probably something we'll need to look at on a case-by-case basis? At the moment I assume that not all accumulate methods are coded in such a way as to have the original data easily available in that form.
-
I propose we mark this issue "on hold" and revive it if there is user demand.
-
Agreed. Changing now.
-
- changed status to on hold
As of now it's unclear that there is any demand for this feature. We will revisit at a later date.
- Log in to comment
I'm not sure I know what this means. @vramasub?