40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Thu Nov 4 18:29:51 2021, Tega, Update, SUS, Setting up suspension test model 
    Reply  Fri Nov 5 12:49:32 2021, rana, Update, SUS, Setting up suspension test model 
       Reply  Mon Nov 8 17:52:22 2021, Ian MacMillan, Update, SUS, Setting up suspension test model x1sus_cp.png
Message ID: 16449     Entry time: Thu Nov 4 18:29:51 2021     Reply to this: 16451
Author: Tega 
Type: Update 
Category: SUS 
Subject: Setting up suspension test model 

[Ian,Tega]

Today we continued working on setting up the 6 degrees of freedom model for testing the suspension which we copied over from  "/cvs/cds/rtcds/userapps/release/sus/c1/models/c1sup.mdl" to c1sp2.mdl in the same folder. We then changed the host from c1lsc to c1sus2, changed cpu # from 7 to 3 bcos c1sus2 has 6 cores. Then ran the following commands to build and install the model on c1sus2:

$ ssh c1sus2

$ rtcds make c1sp2

$ rtcds install c1sp2

where we encountered the following installation error:

ERROR: This node 62 is already installed as:

hostname=c1lsc

system=c1sup

The new entry you are trying to write is as follows:

hostname=c1sus2

system=c1sp2

This script will not overwrite existing entries in testpoint.par

If this is an attempt to move an existing system from one host to another,

please remove conflicting entry from testpoint.par file

It seems that changing the model name and host did not change the node allocation, so will remove the previous entries in testpoint.par to see if that helps. After deleting the following lines

[C-node62]
hostname=c1lsc
system=c1sup

from the file "/opt/rtcds/caltech/c1/target/gds/param/testpoint.par", the installation went fine and the above entries were replaced by 

[C-node62]
hostname=c1sus2
system=c1sp2

BTW, I now believe the reason we had the node conflict earlier was bcos both models still had the same value of  dcuid=62, so I think changing this value in our model file would be a better solution. Work is ongoing.

 

ELOG V3.1.3-