IMP  2.3.1
The Integrative Modeling Platform
changelog.md
1 PMI changelog {#pmi_changelog}
2 =============
3 
4 *News May 14 2014*
5 
6 From Ben Webb:
7 
8 PMI was added as an IMP submodule. But what might not be obvious is that a submodule is tied to a specific revision (or git hash) so doesn't automatically update whenever PMI is updated. So far I've been updating PMI in IMP on a rather ad hoc basis (essentially whenever I make changes to PMI itself), but you might want to do this too when you add new features.
9 
10 It's pretty easy: if you maintain PMI outside of IMP somewhere, just go into your IMP checkout, cd modules/pmi, then `git checkout <githash>` where <githash> is the version of PMI you want to live in IMP. Then you can go back up into IMP proper and git commit/git push that change. Or you can do what I do and work on the copy of PMI that's in IMP directly rather than checking it out separately. To do that, go into modules/pmi in your IMP checkout and run `git checkout develop` to get on the PMI develop branch. Then you can run all the normal git commands (e.g. git pull) in there. (Although note that you can't push by default; that's easy to fix though by running `git remote set-url --push origin git@github.com:salilab/pmi.git`.) When you're done with your git push, you can cd up into IMP proper and commit the change in PMI githash there (without having to remember what it is).
11 
12 *News April 24 2014*
13 
14 The main branch is now `develop` (not `master`) and the module is included
15 in IMP by default.
16 
17 *News February 28 2014*
18 
19 The [clustering analysis](http://nbviewer.ipython.org/github/salilab/pmi/blob/master/examples/analysis/clustering_analysis.ipynb?create=1) calculates the localization densities
20 
21 *News February 25 2014*
22 
23 First working version of the [clustering analysis](http://nbviewer.ipython.org/github/salilab/pmi/blob/master/examples/analysis/clustering_analysis.ipynb?create=1). For the moment each cluster directory will only contain pdbs and rmfs
24 of the structures, but soon I'll add statistics, features and localization densities.
25 
26 To have full speed install the mpi4py python library
27 
28 
29 *News February 10 2014*
30 
31 Checkout the macros in macros.py
32 
33 *News February 6 2014*
34 
35 Added a FAQ section in the wiki. There will be ipython notebook tutorials soon.
36 Best IMP version so far: `ee1763c6859a29ab37415c8454d16549268d9668`
37 Previous versions had a bug in the RigidClosePairsFinder [bug](https://github.com/salilab/pmi/issues/19)
38 
39 
40 *News February 4 2014:*
41 
42 Best IMP version so far: `b700fff93ca45ba1551c8aa9d697c805fcb126dc`
43 Previous versions might be considerably slow due to a [bug](https://github.com/salilab/imp/issues/724)
44 
45 *News January 30 2014:*
46 
47 Now the developed git branch is master and not resolution-zero.
48 
49 If you want to use pmi, after you've freshly cloned it,
50 you don't have to checkout resolution-zero anymore:
51 it is the default branch that you get when you clone it.
52 
53 The resolution-zero branch does not exist anymore,
54 it was copied into resolution-zero-old.
55 
56 To see what branch you're in, run (into the pmi source code directory):
57 
58  git branch
59 
60 If you want to update the code and you still are in resolution-zero branch,
61 just run :
62 
63  git checkout master
64  git pull
65 
66 Note that the interface is also changing,
67 so you'll probably get deprecated warnings in your standard output more and more.
68 `grep deprecated` to get the deprecation warnings, which might be lost in the middle of many other messages. Change your python script according to what the warnings say.
69 The old version of pmi (mainly used by Peter and SJ) is
70 still available under the tag "v0.1". To get it:
71 
72 `git checkout tags/v0.1`