IMP-dev October 2013

imp-dev@salilab.org

7 participants
5 discussions

MD and WLC functions
by Davide Baù 14 Nov '13

14 Nov '13

Hi, I would like to start using the MD and WormLikeChain functions in IMP, but I don't know what their current state is. Are they safe to use? Thanks, Davide

2 18

2.1 release, last call
by Daniel Russel 21 Oct '13

21 Oct '13

Assuming there are no hiccups with today's doc changes tonight, I'd propose we declare the current state of IMP to be the release (see the develop branch or the release/2.1 branch). Anyone who hasn't run their code on IMP from the last week or so (it hasn't changed significantly in that period) is highly encouraged to do so to make sure some recent fixup hasn't broken anything.

5 10

2.1 release branch created
by Daniel Russel 15 Oct '13

15 Oct '13

I created the 2.1 release branch (release/2.1). It would be nice if anyone who hasn't updated in a while checks it out and makes sure there stuff works with it. To check it out do `git imp update` `git checkout -b release/2.1 origin/release/2.1` then build. An issue I just discovered is that the version number support got broken along the way, so you version number will be wrong. I'll fix that shortly.

2 2

IMP 2.1 release
by Daniel Russel 11 Oct '13

11 Oct '13

Seems like things are basically ready for the 2.1 release. Tests last night were good and the two open issues on the 2.1 milestone haven't changed recently and seem like we can let them slide (they won't, I think result in significant API or functionality changes). For reference they are: - dock with crosslinking being broken: https://github.com/salilab/imp/issues/560 - compilation warnings in ISD: https://github.com/salilab/imp/issues/539 There will be a 2.1.1 release pretty soon if necessary anyway. Since there were a couple of commits today, I'll check that nothing breaks in the tests run tonight and if not, create the release branch tomorrow.

1 0

IMP 2.1
by Daniel Russel 01 Oct '13

01 Oct '13

It is time to start on the 2.1 release. There are currently two issues open in the tracker attached to that milestone - one regarding isd (#526) - and the MC mover/optimized behavior. I'd like to resolve the latter by adding checks so errors are thrown with most movers if they try to move non-optimized attributes, which should be a relatively quick change that I can do this afternoon. Otherwise, is there anything else that someone thinks should be cleaned up before the release?

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

IMP-dev October 2013