| DATE | TOPSPIN UPDATE |
|---|
| 3 Feb 05 | StatusReport-500900.msg: DV status report feb 3/ 05 |
| 11/1/04 | The next insturment that we have scheduled to receive Topspin 1.2 is the 500. At the end of cycle 13, in early Dec. we will install Topspin and resume our testing of remote spectrometer operations. |
| 9/17/04 | * TOPSPIN testing/installation on the 700 continues. We have completed upgrade from the beta-version of TOPSPIN to the full release version. There was a problem associated with one installation described in LinuxVirus?. |
| | * TOPSPIN 1.2 release letter and manuals can be found at http://www.nysbc.net/NMR/NMR_instrument_page.htm. You may want to take a look, the user interface is very different than that of xwinnmr, however very easy to use. |
| | * We will continue to operate the 700 (and presumably in the future 900#1) with TOPSPIN, but have no definite date for starting the conversions of other systems. |
| | * Remote spectrometer operation using TOPSPIN continues. Watch this space for progress updates. |
| 12/14//04 | The 500 has been removed from schedule during Cycle 14. Over the next few weeks we will upgrade the Linux opreating system and harddrive and isntall TOPSPIN 1.2. Once this is accomplished the 500 will be used to continue our efforts to provide remote spectrometer operation. Any available time will be offered to the waitlist. |
| 50203.01 | The upgrade for the 500 is close to completion. Since this was an upgrade rather than a straight install, a few more steps were necessary. The conf and exp directories were taken from Xwinnmr and upgraded by topspin. DV
There are a more things to be done during an upgrade, however, there should not be a significant impact to the time taken to upgrade as opposed to a new install. This is the first upgrade that has been performed at NYSBC, and there were some extra modifications that were made manually. Once the 500 upgrade is complete, we will have a good idea of the steps to be followed, and have a process that will work well with the other systems. DV | Is this going to be generally OK for other systems? DC |
| 50203.02 | As of now, though all users have been added, only a single user's (nysbc) configuration has been modified to run topspin. Kaushik is planning to run an experiment with the new settings, and if all goes well, we will be able to modify the configuration for the remaining users. DV | Need KaushikDutta's evaluation DC |
| 50203.03 | Xwinnmr data is stored locally on the 500, so that the users may get their parameter files without any trouble. DV | There probably need to be notes of when XWINNMR params cant be used for TOPSPIN (esp for shaped pulses and gradients, I expect ) DC |
| 50203.04 | Xwinnmr data will not be included in the delete cycle until we are notified to do so. This applies to the data server as well as the 500. DV | The delete cycle can run on the 500 as previously if there are space limitations. DC |
| 50203.05 | Backup scripts have been modified to take into account the new directory structure. A script has also been created for converting the existing users to Topspin. DV
Topspin and Xwinnmr require different versions of Linux. Xwinnmr cannot be installed on the 500, so the execution option is lost. Topspin is backward compatible with data collected using Xwinnmr, so the user will still be able to read the data in Topspin. DV | By "converting" does that mean it's one directional and the xwinnmr executionoption is lost ? DC |
| 50203.06 | Modifying each user takes over 1 minute, there are currently 96 users not including nmrsu and nysbc. DV | We need to update the user list and be sure that the deaffiliated are moved out DC |
| 50203.07 | On the 900, we have modified the host id as per NYSBC conventions. This needed modification of the Bruker license file, and reinstallation of the new license. The home directory for nmrsu has been changed to /opt/topspin/data/nmrsu/home, so that any files stored within the home directory will be backed up. DV
We are quite comfortable with this process, and are currently working on the documentation. There would be some advantage in changing the host id as soon as we assign an IP address to the 900#2, but it may make the engineer running the install nervous, as they will be deviating from their normal install routine. DV | Keep the notes for the 900#2 as the same issue will arise DC |
| 50203.08 | There are no users created on the 900 as yet, since we need to create a template using the nmrsu files. The script to add users on the 900 is also ready. The process of adding new users takes longer and we estimate the process to take between 3 to 5 minutes for each user. DV | We will add 900 users slowly. See list at NinehundredGroup? DC |
