Hello: chimera production version 1.6.2 (build 36855) 2012-07-06 17:55:00 UTC is unable to restore *.py files saved with chimera alpha version 1.7 (build 36726) 2012-06-21 01:06:17 UTC on another computer. Both computers running GNU-Linux Debian amd64 wheezy.. Error message "cannot open session that was saved in a newer version of Chimera; update your version" Does "alpha version" override date and stable compilations? The unable version has a more recent date. Then, I have installed the latest stable version of chimera, and the error was the same. Thanks for advice francesco pietra
Yes, when chimera 1.6 became a production release candidate, the daily builds switched to version 1.7. And especially for session files, any version of 1.7 is considered newer than any version of 1.6. Version 1.6.2 is a patched version of 1.6 and while the date is newer than your version of the daily build, the code is much older. So you need a newer daily build (or the same one) to restore that session file, luckily there is a new version every day :-). HTH, Greg On 10/10/2012 03:01 PM, Francesco Pietra wrote:
Hello:
chimera production version 1.6.2 (build 36855) 2012-07-06 17:55:00 UTC
is unable to restore *.py files saved with
chimera alpha version 1.7 (build 36726) 2012-06-21 01:06:17 UTC
on another computer. Both computers running GNU-Linux Debian amd64 wheezy..
Error message "cannot open session that was saved in a newer version of Chimera; update your version"
Does "alpha version" override date and stable compilations? The unable version has a more recent date. Then, I have installed the latest stable version of chimera, and the error was the same.
Thanks for advice
francesco pietra _______________________________________________ Chimera-users mailing list Chimera-users@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users
Hi Francesco, Although a session saved with old Chimera will generally work in new Chimera (we retain backwards compatibility), the opposite is not true: a session saved from newer Chimera generally requires that version of Chimera or newer to restore, as Greg described. This is because "Chimera from the past" does not know about more recently added features, but these features are incorporated in sessions from "new Chimera." Best, Elaine ----- Elaine C. Meng, Ph.D. UCSF Computer Graphics Lab (Chimera team) and Babbitt Lab Department of Pharmaceutical Chemistry University of California, San Francisco On Oct 10, 2012, at 3:01 PM, Francesco Pietra wrote:
Hello:
chimera production version 1.6.2 (build 36855) 2012-07-06 17:55:00 UTC
is unable to restore *.py files saved with
chimera alpha version 1.7 (build 36726) 2012-06-21 01:06:17 UTC
on another computer. Both computers running GNU-Linux Debian amd64 wheezy..
Error message "cannot open session that was saved in a newer version of Chimera; update your version"
Does "alpha version" override date and stable compilations? The unable version has a more recent date. Then, I have installed the latest stable version of chimera, and the error was the same.
Thanks for advice
francesco pietra _______________________________________________ Chimera-users mailing list Chimera-users@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users
participants (3)
-
Elaine Meng -
Francesco Pietra -
Greg Couch