40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  ATF eLog  Not logged in ELOG logo
Entry  Wed Aug 18 21:14:49 2010, rana, Computing, General, The BURT situation 
    Reply  Thu Aug 19 11:17:43 2010, Frank, Computing, General, The BURT situation 
       Reply  Thu Aug 19 11:23:44 2010, Rana, Computing, General, The BURT situation 
          Reply  Thu Aug 19 12:01:13 2010, Frank, Computing, General, The BURT situation 
             Reply  Thu Aug 19 12:22:25 2010, Alastair, Computing, General, The BURT situation 
Message ID: 957     Entry time: Thu Aug 19 12:22:25 2010     In reply to: 956
Author: Alastair 
Type: Computing 
Category: General 
Subject: The BURT situation 

Quote:

Quote:

Quote:

i don't know if there is a wiki or something like that but i do exactly what Alex and Rolf told me to do:

 This is a horrible, horrible precedent to set. Please immediately make a wiki page so that EVERYONE uses the SAME procedure for rebuild each time.

                                 Not following a rigid procedure leads to a lot of wasted time.

 There is one in the ELOG, entry 124 "Realtime code generation (RCG) troubleshooting":

  http://131.215.115.52:8080/AdhikariLab/124

Thanks for posting that link Frank.  We're going to rebuild the front end soon to make changes for the gyro and we'll follow this method.  If it all looks good and works then my plan is to add an 'internals' and 'how to' section to the ATF wiki (following the same site plan as the 40m so that people know where to look for stuff) and we can start putting some useful information in here about standard things.  If there is useful information on how to do things that is already posted on the 40m wiki we can just link to that.

I would suggest we also add such useful information as 'how to add channels to the frame builder' so that everyone is doing the same thing.  Maybe that way we can converge on a more stable computing environment for everyone.

ELOG V3.1.3-