-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DensityAnalysis Normalization #108
Comments
I doubt that packaging the histogram from PMDA into Lines 314 to 317 in 1e99541
As an alternative density calculator you can use VMD's VolMap. |
Are you sure that Line 303 in 1e99541
run(start, stop, step) parameters?
There's some "we're trying to be smart"-code in |
Can you please also look into why DensityAnalysis failed after merging into master? See https://travis-ci.org/MDAnalysis/pmda/jobs/592141990
|
It failed because the number of frames is grabbed from the length of the trajectory in I'm currently working on a solution to this since the number of frames is never saved in the run method or dask helper. I looked at the RMSF function for inspiration since it has to divide by a similar value in |
Ok, my fault – I looked at the wrong travis run. Thanks for the explanation. |
* Fix #108 * Corrected start/stop/step issue in DensityAnalysis and RMSF * Changes: - Added self.n_frames to parallel.py - Updated DensityAnalysis conclude() to read self.n_frames instead of trajectory length - Updated RMSF to read self.n_frames in _conclude() - Added test_n_frames() to both DensityAnalysis and RMSF tests - Added test_accuracy() to test_rmsf.py to verify subselecting trajectories doesn't affect accuracy - Added new datafiles to test_density.py to use for testing timestep sub-selections - Consolidated two tests in test_density.py into one test that verifies both the array values and the sum of their values * Fixed commented out metadata in conclude() * PEP8 fix
The current density function may have an issue with normalization. Since DensityAnalysis uses the MDAnalysis density function, it is currently unclear whether MDAnalysis.density.density_from_universe() is incorrect or the implementation of density_from_universe() into pmda is incorrect. We need to compare the results from a run of MDAnalysis.analysis.density.density_from_universe() to pmda.density.DensityAnalysis for other trajectories to see if they agree, as well as find a 3rd party method of calculating densities to compare values with.
The text was updated successfully, but these errors were encountered: